You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hosted-service policy for an independent iOS/macOS encrypted messaging client
#1825
We are preparing Smile Code, an independent iOS/macOS companion app, for an App Store release. Before enabling Happy's public hosted service in a distributed third-party client, we would like to confirm the hosted-service usage policy separately from the MIT software license.
Our planned production scope is text conversations and control messages only. Desktop video/previews will remain LAN-only and will not use your public service.
May an independent third-party app use the public Happy backend for end-to-end encrypted text conversations and control messages? Does this include commercially distributed apps, or is prior permission or a separate agreement required?
What limits apply (accounts/connections, messages, payload size, bandwidth, rate limits, or fair use), and where is the authoritative policy documented?
Which production endpoint and authentication/client compatibility requirements should a permitted third-party client follow? Is self-hosting the expected approach instead?
We are not asking for an uptime or unlimited-bandwidth guarantee. We will keep this public-service integration out of the production release until its permitted scope is clear. A link to the applicable terms or the appropriate maintainer contact would be appreciated. Thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi Happy maintainers,
We are preparing Smile Code, an independent iOS/macOS companion app, for an App Store release. Before enabling Happy's public hosted service in a distributed third-party client, we would like to confirm the hosted-service usage policy separately from the MIT software license.
Our planned production scope is text conversations and control messages only. Desktop video/previews will remain LAN-only and will not use your public service.
We are not asking for an uptime or unlimited-bandwidth guarantee. We will keep this public-service integration out of the production release until its permitted scope is clear. A link to the applicable terms or the appropriate maintainer contact would be appreciated. Thank you!
All reactions