this post was submitted on 07 Jul 2023
3567 points (98.6% liked)

Fediverse

27910 readers
1 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

Lemmy.ml has now blocked Threads.net

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 16 points 1 year ago* (last edited 1 year ago) (9 children)

Yes. Threads wants to use the ActivityPub Protokoll. We can interact with Kbin and Mastodon users thanks to this Protocol. The fear is that they use their huge user base to change the protocol to their liking (basically take control over the ActivityPub) and everyone who wants to stay federated with them and their users has to adapt those changes until the day they will simply cut everyone off.

[–] [email protected] 4 points 1 year ago (8 children)

When they do go that route, I propose the community fork the standard and continue work that way. We already do this with code.

[–] [email protected] 6 points 1 year ago (1 children)

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

[–] [email protected] 3 points 1 year ago

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.

load more comments (6 replies)
load more comments (6 replies)