this post was submitted on 13 Feb 2024
120 points (91.7% liked)
Fediverse
28294 readers
698 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 !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's exactly this. Bluesky has its problems but there is a massive overreaction from the fediverse crowd that it makes it hard for me to sympathise with them even if I agree on the principle.
EDIT: JSYK, the Bridgy Fed developer is working towards making the bridge opt-in! https://tech.lgbt/@ShadowJonathan/111925391727699558
That kinda sucks. We need more openly accessible information without everyone erecting their little walled gardens. :'(
I think the fediverse, and that includes Lemmy, have this warped idea of what Bluesky is and what ActivityPub/the fediverse actually is. They think ActivityPub is the de-facto protocol for microblogging, when it has glaring issues that Bluesky wanted to solve with Atproto (the queer.af debacle is a great example of this, imagine if you've got an account on queer.af and you want to move your data to a new instance). If you're a Linux guy, you might have seen parallels between ActivityPub/Mastodon vs. Atproto/Bluesky and X11 vs. Wayland.
And I mean, I don't necessarily disagree - but I find it wild that the very same group would then not also want their social network to be inaccessible from the outside, so that it cannot simply be scraped like this bridge does.
But it's also a bit weird insofar that if AP ever gets big, that's a problem we'll have to do deal with sooner rather than later anyways. Or at least have a plan how to handle it that goes beyond DEFEDERATE EVERYTHING™️. We need to accept that either there's a certain baseline obscurity always baked in that also means at any point it could be that the world at large swings to using a different federation protocol and then we're the weird pariah on a weird non-standard protocol. Or it gets mainstream acceptance and then Threads will be just one problem in an ocean of corporate federation.
Personally, I just go 🤷 in regards to the actual data-federation, and rather focus on moderation/administration tooling and automation. It's a problem that eventually needs solving anyways, so might as well get in front of it and have a solution for when or if large corporate instances and their masses of users end up dumping data into AP.
Thank you for this!