Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opting out, and the Hitchhiker's Guide to the Galaxy #841

Closed
timixretroplays opened this issue Feb 13, 2024 · 5 comments
Closed

Opting out, and the Hitchhiker's Guide to the Galaxy #841

timixretroplays opened this issue Feb 13, 2024 · 5 comments

Comments

@timixretroplays
Copy link

The Hitchhiker's Guide to the Galaxy begins with an absurd story: A man's house is knocked down by the council to make room to build a road. He is lambasted by the council for being ignorant and difficult, and is told the plans to build this road have been made public, and available to read for a while, and that it is his fault that he's made no act at all to move his possessions out of the way, settle accounts, or even raise objections. It's revealed that the plans were in a locked filing cabinet, in a dark basement, in an unmarked part of a building, so that practically nobody would ever have discovered anything was going to happen to their houses before it happened.

Mastodon's monthly user base, as of October 2023, was 1.8 million (source). What you have proposed is to knock down all 1.8 million houses in order to build your road, which is revolting. You could consult with home owners about your proposal. You could work with them to find a solution to your road that doesn't involve knocking their houses down. Invariably, some will agree to have their houses knocked down so you can build your road. Those are the people you're building this road for - they want the road built so they can use it, and they are entirely free to do so if they so choose. You should seek these people out, gather their support, and crucially, only knock down the houses of people who have expressed to you that they want you to do so.

What percentage of people are telling you "yes, knock my house down" vs "no, don't knock my house down"? How would that percentage map to that figure of 1.8 million Mastodon users? From what I've read so far, I assume you're seeing far more of the latter, and so extrapolating out, the vast majority of people would tell you not to knock their houses down, if only they knew they needed to do so. Knowing this, with the switch yet to be flipped, you should simple back down and walk away, because the alternative is completely unconscionable. Altering course to an opt-in situation is the only ethical way forward for this project.

And if you've read through this, thinking "but I'm not doing anything as drastic as knocking down anybody's houses!", you have not only misread the room, you have missed the point entirely.

You do not have permission to bridge content I post on the Fediverse across to Bluesky, for any of my accounts, and it is your responsibility, not mine, to ensure this is honoured.

@scheeseman486
Copy link

scheeseman486 commented Feb 14, 2024

Equating the creation of an API bridge between to social media protocols and eminent domain is a bit silly. Whose "house" is getting knocked down? Everyone's servers are able to continue existing and if there is a metaphorical highway it isn't this piece of software but the internet as a whole. Your premise is faulty, the comparisons you make are nonsense and nothing you said makes a coherent point about how an API bridge is somehow a threat.

It's not like it's impossible for a server using ActivityPub to be run by a literal nazi. If you want to be a part of a larger, open network then you'll have to moderate reactively. If you want a private social network of trusted servers then you're probably better off whitelisting, effectively silo off. The protocol makes no difference.

@timixretroplays
Copy link
Author

It doesn't make sense because I'm talking about data ownership and control, not moderation, the protocol, safety, or nazis?. To be clear, I don't have a technical issue with the bridge existing, but I and plenty of others are on Mastodon specifically to avoid contributing to or otherwise interacting with the big social sites like Facebook or Bluesky, and any project that will just attempt to connect 1.8 million people to them with an opt-out mechanism that almost none of them will ever see is going to be met with revulsion. This is a social issue, not a tech one.

@timixretroplays
Copy link
Author

No, yes, data ownership and control, yes, yes, and "probably not" is making an assumption about me as a person and not discussing the issue at hand. I think we're done here.

@snarfed, if I've interpreted correctly that you're switching to an opt-in strategy instead, feel free to close this issue. Sorry about the pile-on going on, I hope you get the opportunity to take some time out for yourself after this mess.

@Sketch6307
Copy link

It doesn't make sense because I'm talking about data ownership and control

You do have data ownership and control. That is provided, and can only possibly be provided, by the instance you use (i.e. by your visibility settings). If you make your content public, then yes, anyone can read it. And yes, that includes people (and platforms) you don't agree with.

That's the entire point of federation: multiple interoperable platforms that may not agree with each other.

If you want to live in a bubble you can absolutely do that, but the responsibility is not on those around you to build that bubble for you. You're expecting the opposite of eminent domain: turning a public space into a private one dedicated to the benefit of certain people.

@snarfed
Copy link
Owner

snarfed commented Feb 15, 2024

@timixretroplays You never go wrong by quoting Douglas Adams on the internet. 😁 Hitchhiker's Guide to the Galaxy is a great book, and this a great parable, and obviously relevant. Thanks for the thoughtful, creative response. I've opted out your account; you can also block bsky.brid.gy on your end if you want.

@snarfed snarfed closed this as not planned Won't fix, can't repro, duplicate, stale Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants