Yo browsers already know & implement Signed Http Exchanges[1]. Just follow the spec we have. Once twitter or bluesky or whomever signs a message, it becomes in effect a cryptographically self identifying content addressable blob we can relay around as we please, is cryptographically signed.<p>Such a damned pity that so much zealous & righteous energy jn distributed & p2p is shunted into rejectionist, reactionary re-treading, that it rejects what is & expansion & enhancement & wanders off alone (into the far blue sky) to go try it's own hand at communing with god & finding a whole new approach. This is bluesky confirming that they too either dont see or dont care to work with the best most advanced prospects we have, that they d rather go back to 0 again. Disappointing, unsurprising, totslly in the mold of every hot taking reactionary would be do-it-all-over-again revolutionary, like like urbit.<p>I will try to see if there's anything here really novel & ennabling, but holy cow, http already does 92% of what's on the tin here, & we could turn it on for everything in months, with little challenge, if we cared to try.<p>[1] <a href="https://web.dev/signed-exchanges/" rel="nofollow">https://web.dev/signed-exchanges/</a>