- has many actors / participants (1:1, 1:n, n:m)
- an actor / participant can be human or system
- can be text based
- can have audio or video feeds for one or more actors
- can have attachments
- policy driven limits
- message retention
- attachment size
- number of participants
- conversations can be peer to peer
- all communications are encrypted
- frictionless onboarding, no registration to start
- each client / device is automatically registered
- account links one or more clients / devices
- subscription based or usage based
- a person owns an account
- an orgrnization owns an account
- Registeres with platform at first start / connection
- Can be linked to an account or used without one
- Registration also generates cryptographic keys
- A client not linked to an account keeps all config locally
- contacts can only be other client ids
- contact list clients can only direct message other clients
- A client without an account cannot use APIs, must be human
- Message rate limits strict to prevent abuse
- Ability to utilize proxies to bypass censorship
- Tor clients allowed
- account level preferences
- can block conversations requests from unverified clients
- client level preferences
- can rotate cryptographic keys periodically
- can only function through tor
- conversation level preferences
- two way contact pairing
- when adding an entry to your contact list, messaging only becomes possible once the request is accepted or you are manually added to the other parties contact list
- offsetting co2 impact of communications for paid accounts
- platform resiliency, not dependant on a single cloud provider, built to remain up if AWS / GCP / Azure are down.
- offer to use local storage for conversation attachment retention
- distributed sotrage with erasure codes, for objects between clients
-
1:1 disappearing conversations, relayed by message queue or some type of message relay, server only relays messages does not keep them in memory more than 1-2 minutes maximum, less reliable delivery but greater privacy, small messages only, client configured to clear local message history based on conversation lifespac setting, all comms are encrypted with client keys, not accessible from multiple clients for same account
-
1:1 direct messages with history enabled, encrypted with account keys, viewable from any account client / device, push notifications, re-synchronization,
-
...
Show how much your personally identifiable information is worth to marketers. Market price per email, per month etc. What they do whith that data. How we are transparent, because charge you what it costs to run the platform and offer options to be socially responsible.