It should come as no surprise that the lemmy.ml [http://lemmy.ml] admin team
took about 2 minutes to decide to pre-emptively block threats / Meta. Their
transparent and opportunistic scheme to commodify the fediverse and it’s users
will not be allowed to proceed. We strongly encourage other instance
administrators to do the same, given the grave threat they pose to the
fediverse.
the standard is made by the World Wide Web Consortium, which I trust to not let facebook take control of their standard. They also manage standards like HTML, CSS and SVG
No, they re-publish the work of WHATWG in standards form, the vendors literally made a pact not to deal with them. Then sometime in the last decade they standardized EME, even after the technology activists told them fucking not to. Defective By Design said this shit for years, decades, and W3C ignored everyone. I have more reason not to trust Berners-Lee at this point than put any stock in his leadership skills.
I agree in theory, but in practice, when Google dropped RSS and XMPP support it took most of my friends with it, which is what started this mess in the first place. I’m actually not a fan of mastodon; feels too ambitious to start a new protocol without a killer app. RSS and XMPP are extensible protocols and I really just want modern support for those.
ActivityPub wasn’t built with the purpose of having a “killer app” in mind. That’s centralization logic. The point is for all apps to be able to talk to each other regardless of where on the network and maintaining the ability to do so seamelessly without the user having to think too much about it.
Mastodon should be able to talk to Lemmy. Lemmy should be able to talk to Pixelfed. Et cetera. I don’t believe XMPP had the same purpose, matter of fact I remember it just being a subpar IM protocol iirc, and I don’t see social media going by the wayside the way IM clients of the past did.
If one instance gets too big they could just ignore the standard and start adding random tweaks to it. And all the others would eventually have to adapt to that or risk becoming irrelevant by being incompatible with the big instance.
Federation allows for choice. Indeed, many AP implementations already add to the base AP stuff. Peertube already does this itself.
For this to really be a problem, the server software would need to be maintained by the same person running the instance, and they have to have the manpower already to either a) Build an implementation or b) Run a fork of existing software. Both take effort and quite frankly is juice that isn’t worth the squeeze to risk cutting yourself off from the network like that.
When they do go that route, I propose the community fork the standard and continue work that way. We already do this with code.
the standard is made by the World Wide Web Consortium, which I trust to not let facebook take control of their standard. They also manage standards like HTML, CSS and SVG
No, they re-publish the work of WHATWG in standards form, the vendors literally made a pact not to deal with them. Then sometime in the last decade they standardized EME, even after the technology activists told them fucking not to. Defective By Design said this shit for years, decades, and W3C ignored everyone. I have more reason not to trust Berners-Lee at this point than put any stock in his leadership skills.
I agree in theory, but in practice, when Google dropped RSS and XMPP support it took most of my friends with it, which is what started this mess in the first place. I’m actually not a fan of mastodon; feels too ambitious to start a new protocol without a killer app. RSS and XMPP are extensible protocols and I really just want modern support for those.
ActivityPub wasn’t built with the purpose of having a “killer app” in mind. That’s centralization logic. The point is for all apps to be able to talk to each other regardless of where on the network and maintaining the ability to do so seamelessly without the user having to think too much about it.
Mastodon should be able to talk to Lemmy. Lemmy should be able to talk to Pixelfed. Et cetera. I don’t believe XMPP had the same purpose, matter of fact I remember it just being a subpar IM protocol iirc, and I don’t see social media going by the wayside the way IM clients of the past did.
If one instance gets too big they could just ignore the standard and start adding random tweaks to it. And all the others would eventually have to adapt to that or risk becoming irrelevant by being incompatible with the big instance.
Federation allows for choice. Indeed, many AP implementations already add to the base AP stuff. Peertube already does this itself.
For this to really be a problem, the server software would need to be maintained by the same person running the instance, and they have to have the manpower already to either a) Build an implementation or b) Run a fork of existing software. Both take effort and quite frankly is juice that isn’t worth the squeeze to risk cutting yourself off from the network like that.