In Strawberry (the hybrid pubsub protocol I'm building), we don't just not criticize the fact that public data is public - we fully embrace it.
Sure, there are going to be mechanisms in place for data deletion of course, but it's impossible to guarantee that *every* copy of *every* post is gone - especially considering how Strawberry is designed.
That's not to say that there wouldn't be ways to guarantee deletion of a post at all though.
For example, you can create an encrypted network channel, use it temporarily, burn the keys, and ask the network to delete everything on that channel. And in some cases this might be the best way to use Strawberry for your use case.
@hexaheximal :blobcatgoogly: what are the differences between your idea and activity pub? i dont see much more features which could be implemented into a protocol for a federated service...
@hexaheximal You either need a server which acts as inbox / outbox (basically emails or fedi) or a core server which can be the entrypoint for a fully decentralized service (like torrent tracker, and im sure i also saw message protocols which do that) or you build a protocol which passes messages directly (like briar)
@Jain Most notably, it does not know nor care what you use to transport data. You can use QR codes with embedded MessagePack data as a Strawberry transport and it will work fine.
But it's also not necessarily federated. By default, it's fully decentralized (and no, there is no stupid blockchain stuff involved), but you can make it federated by setting up and/or signing up to a Strawberry post office server, which will then assign you a mailbox address, which acts like a normal profile handle as you would expect on the fediverse.
A post office server can also act as a bridge, not only to ActivityPub, but to other protocols as well. And it will create handle aliases as well so you see a Strawberry representation of the bridged profile instead of the internal user ID.