It should be pretty obvious that a decentralized network that many use specifically to not be connected to centralized networks houses mostly people who do not wish to have their posts bridged to B...
Unless there’s some actual technical reason why this a bad idea, I don’t buy the “ethical” hand-wringing here. It sounds like just another case of not liking specific social media companies and wanting the defaults to conform to those personal dislikes.
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.
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.
I think the people mad about these massive networks joining the Fediverse want to shield their little social networks from the big bad internet. They don’t want the Fediverse or any part of it to succeed and become mainstream, because that brings in the toxic waste of opinions and trolls that the wider social media is known for, and their tiny servers don’t have the moderation capacity to deal with that.
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.
Unless there’s some actual technical reason why this a bad idea, I don’t buy the “ethical” hand-wringing here. It sounds like just another case of not liking specific social media companies and wanting the defaults to conform to those personal dislikes.
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.
deleted by creator
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.
deleted by creator
deleted by creator
Thank you for this!