this post was submitted on 19 Jun 2023
227 points (100.0% liked)
Technology
37705 readers
91 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Wouldn't the "extend" part be problematic for them since it's W3C that define the protocol? If meta tries to change it it'd break compatibility with the rest of the federation. Not that it is that well defined right now, from what I've read even mastodon, kbin and lemmy all use AP in different ways, with upvotes/downvotes and post types being interpreted and used in different ways from the technical standpoint and then jury-rigged in frontend to look decent.
The fact that W3C defines the protocol doesn't stop large companies from doing whatever they want. Have a look at Google: their web browser has become so widely adopted that Google effectively controls what is considered part of the spec, not W3C.
If Meta's platform grows to become the biggest fediverse project, they will control the spec and others will either have to follow, or risk dropping out. This is just like how Firefox is forced to follow Google to ensure all websites work properly on Firefox, even if these sites don't comply with the spec.
Honestly, they should. Drop out of the spec if Facebook gains control over it, I mean. Fuck em, I don't care if I can't federate with Instagram, in fact I prefer it that way.