AFAICT, mastodon's decisions, which are arguably problematic (on which see: https://lemmy.ml/post/14973403) are literally trickling down to other platforms and infecting how they federate with each other as they dance around mastodon's quirks in different ways.
It seems like masto is ruining "the standard" with its gravity.
None of that matters if Mastodon doesnt implement these suggestions or standards. And from past experience its extremely unlikely that they will. Thats why I think its best to ignore what Mastodon does, its not our concern how they decide to render things.
That's kind of what I meant too, if there's a standardised and correct way to implement things, that's how projects should implement it instead of trying to do it the "Mastodon" way
"We Need To Rewild The Internet"
An absolutely excellent read (and great analogy) by @mariafarrell and @robin Probably the best piece I've read all year.
I often struggle to think of a term for "appearing messy from a distance is often, on a human scale, healthy actually." Comparing the social web to an ecosystem is exactly it.
I poked around in the (slightly verbose) documentation and stumbled onto this:
Servers should not re-use URIs, regardless of the mechanism by which resources are created. Certain specific cases exist where URIs may be reinstated when it identifies the same resource,
So I wonder if it has the same inbuilt limitation that IPFS has, which means you cannot just update the data you are sharing, without also having to create a whole new link (I know IPFS are trying to work around that, but have seen no decentralised solution yet).
I'll poke around some more!
Thanks for the link, I hadn't heard of them before.
Now this is interesting, I know about Tor ofc, with all problems surrounding it (exit nodes etc) but I guess an onion website could be made well protected and shared & updated. You have to host it yourself though I guess.
Freenet, gotta dig down and see how it works under the surface, it looks very promising but it's kind of complex and I haven't yet figured out if it is all benevolent sharing for example and what happend if some random node sharing your stuff goes offline.
Very interesting!
I think (I'll dig more to see if it stands) my advantage would be the redundancy (so the data always stays up and is hard to take down), the no need of benevolent nodes, and potentially the ease if use.
The problem is that Misskey code is bad. This is the main reason the forks exist at all.
Iceshrimp is rewriting from scratch in C# and it's my main hope for the *keys.
As more and more instances are providing multiple services under the same management, we need a term to talk about this type of arrangement. A Fediverse Galaxy is a collection of federated software that is provided by the same admin or collective.