233
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2023
233 points (99.6% liked)
Programming.dev Meta
2365 readers
6 users here now
Welcome to the Programming.Dev meta community!
This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.
Links
Credits
founded 2 years ago
MODERATORS
TLDR; YES.
They are just trying to pull an EEE(Embrace, Extend, Extinguish) on fediverse. Federating with Thr*ads is just putting a shotgun at the mount. Just see how Google killed XMPP
If they start to pull some EEE bullshit I'm sure 90% of the Fediverse will just nope the fuck out. I'd say give them a chance, but don't let them start to control the Fediverse protocols.
Once they start damage is already done, I'd say treat them like they're as radioactive as they are
XMPP is alive and well, you can use it, many do.
When Google and Facebook embraced it back then, the community was small and fresh, so their adoption of XMPP was quite the boost.
When Google quit and took its users there was a significant user base that disappeared.
The fediverse exists for almost a decade and it has a stronger user base. Meta can try to extend ActivityPub and we can only hope the devs don't cater to their needs above anyone else's (maybe we can learn from Mastodon's influence). When Meta tries to extinguish it'll only take their users with it.
They can already fetch all the public data they want without federating.
I dislike preemptiveness but everyone would have to be on their toes to react to any ill intent (like trying to change ActivityPub although that's not really a well-defined protocol to begin with).
I'm still on the fence but leaning towards block.