Conceptual Issue: How to have a public feed, @komrades, which is safe, encrypted, and not overrun with BS? about comrad HOT 1 OPEN

MZ, Sep 19: "For now, I decided to go for more centralized solution. (It's interesting by the way how design questions in this "socialist network" recreate political-philosophical debates within socialism: the role of a centralized state, e.g. vs more anarchist strains of socialism emphasizing decentralized governance.)

"Posting" basically means sending a DM to a special account, @.komrades who 'registers' as if a user on the same machine that the Operator runs oon. Like all DMs, when you DM @.komrades, the post is stored as you encrypted it end-to-end from you to that user. (But unlike other DMs, the message won't be deleted from the server as soon as you logs in to download it, but will stay up there for N days (set by you the poster?).) Then, if anyone sends a request to the Operator for the latest posts, then Operator boots up the account @.komrades (whose private key it has on the same machine), de-crypts the latest DMs @.komrades, then re-encrypts them from @.komrades -> the account requesting the posts, before sending them back over the wire to that account, where they're also stored as encrypted, until they're loaded and read on the client, in which case they're just decrypted on the fly.

So now we have two tiers: 1) DMing user to user, which stays private between those users, and where messages are removed from ASAP; 2) posts to world, which normally are read by anyone, although we can still play with setting certain restrictions (like blocking a specific user, e.g.). But we're still missing the middle tier: group chats, which I think actually could implement something more peer-to-peer, where if I post to a group, it travels through the social network of the network."

Any more thoughts on this?

from comrad.