China:
mlg
joined 2 years ago
They care more about protecting their IP and public image, not end privacy of users.
They make a big fuss anytime a public request comes up like the FBI a few years ago, but they have zero issue funneling everything into the NSA just like every other Silicon Valley shmuck.
A morbillion javascript frontends, data hoarding middle ends, and another morbillion tracker tags all so you can display 5 sentences of text and a default picture which causes the website to take 5000 years to completely render as you watch Wappalyzer light up like a christmas tree on fire. Use static HTML and CSS ffs, it's there for a reason.
Modern HTTP is such a horrendous steaming pile of crap that I could honestly spend an entire day talking about the horrible ways we accomplish WWW, with about a solid 70% of it being directly attributed to pos Google.
Whenever the new standard hits the almost impossible golden triangle of "cheap, reliable, and fast".
It's gotta be cheaper than the alternatives, better and more reliable than the alternatives, and faster/easier to adopt than the alternatives.
Early computers for example had various ways to chug math, such as mechanical setups, relays, vacuum tube's, etc.
When Bell invented their MOSFET transistor and figured out how to scale production, all those previous methods became obsolete for computers because transistors were now cheaper, more reliable, and faster to adopt than their predecessors.
Tbf though transistors are more of a hardware thing. A better example of a standard would be RIP being superceded by BGP on the internet.
Federation.
There's a reason why worldnews@lemmy.world and worldnews@lemmy.ml are not federated with eachother, yet lots of users are subscribed to both.
For lemmy, it's again a federation thing. You just don't see many multiple defederated examples due to the small user count.
It's not the most optimal solution, but it's still miles better than dealing with single instance or single community issues.