That's because you don't know what the solution is. But I know.
Have to go build it. Later 😘
I'm torn between applauding your optimism and giving in to age and experience of "having seen all this before". Especially adding some **P to extend a core protocol more and more seems a reliable road to certain chaos. Like XMPP did before - and ultimately we ended up with a wagonload of competing, at times even conflicting XEPs, and most devs even in 2020s were left with choosing "bare" XMPP when they were aiming for compatibility (which in turns meant using unencrypted plain text in XML, without even support for any kind of media files to be transferred). 😔
(Ah, and ... yes, that could be done with Nostr. But it might be possible to do that with ActivityPub, too, before, or with atproto which has some interesting ideas. Or with the Diaspora federation protocol even though this is slightly a beast of its own. Or with Zot which is one of the most sophisticated protocols I've seen to date in this field but totally underdocumented. The protocol hardly is the problem in these cases. Usually, people are. Interesting reading recommendation, unless already known: https://overengineer.dev/blog/2019/01/13/activitypub-final-thoughts-one-year-later.html -- that's one of the Diaspora* maintainers writing about the standardisation process and shortcomings of ActivityPub. Very very disillusioning in any possible way. 😔)
Discussion
No replies yet.