status-legacy

ven lots) in a reasonably private context, then the chances of it being spammed or randomly joined are quite low. Note that public chats, while "public", are still E2EE, using a chat's name as the basis for a symmetric key. 1-to-1 and private group chats are highly secure; the latter have a max size, and depending on their size and your device, sending messages can be a little slow. Creating a robust alternative to the existing public chats facility has involved a lot of work: the forthcoming Communities feature provides a discord-like facility whereby founders/admins of communities can take advantage of various mechanisms for moderation and governing membership. The Communities feature can already be enabled in advanced preferences of both mobile and desktop apps, but note it's a WIP. The moderation mechanisms for Communities don't undermine the no-censorship principle of Status because: (1) Any user can create a community. (2) A community's rules are managed by those with a stake in the community: there's no override by Status-the-org nor anyone else. (3) The underlying nodes of the network form a decentralized p2p network, i.e. there's no central actor/authority that controls the flow of messages. Re: (3), running a Status node should be simple and incentivized. The "incentivized" aspect is a challenging problem and not solved yet. Long story short, engineering an incentivized decentralized messaging network (it's not a blockchain!) is harder than incentivizing a blockchain network. That being said, the "simple" aspect isn't too difficult to solve, sneak peek: https://github.com/status-im/status-node Finally, with pertinent laws and regulations in flux across the globe, there could come a day when binaries aren't readily available (from app stores, GitHub, etc.), but thankfully there's always `git clone` and `make`. Disclosure: I'm a core contributor at Status.