this post was submitted on 23 Jun 2023
714 points (100.0% liked)
Technology
37720 readers
337 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A good response. Civlised and to-the-point.
I disagree.
I hope there'll be people discussing sensibly.
For example the question how the rest of the fediverse would like Meta to act, when / if they have the by far largest instance on Fediverse with Threads.
Should they Rate-Limit queries from their users to other Instances, as to not overload them? This would protect other instances, but make the federated experience worse, driving more people to threads.
Would the Fediverse rather that Meta mirrors images etc on their servers too, or pull those from the original server?
Maybe they have UX ideas that would be useful to have somewhat uniform (like the subreddit/community/magazine stuff here), and would like input on them.
Of course just blocking them is an option for the fediverse, but doing that blindly seems like a missed opportunity for both sides.
More freely available content would be great, wouldn't it?
Maybe they have Ideas on the protocol, that they want to talk with admins about as a first step to gain more perspective. And certainly they are likely to be data-hungry greedy shit, but there is a chance that they are actually good ideas - there are actual people working at meta after all.
There's tons of ways in which this could be useful, and I don't really understand the completely blocking approach I see a lot of.
They want to use ActivityPub, that's awesome, finally something new and big that uses an open freaking standard on the web. What are the downsides? If it sucks for communities they can easily block Meta.
Yes, Meta is not a Company working for the betterment of the world, certainly.
But maybe, just maybe, goals align here, and Meta can make money and improve the Fediverse and the Internet with it. And certainly, maybe they want to "take over" ActivityPub, and that would indeed be bad. And even then, wouldn't knowing because they told you be much better than knowing because they're meta?
So, if they want to change the Protocol, be very, very wary of their proposals. But even there there they could just want reasonable improvements because they suddenly deal with 100x of the next biggest instances.
tl;dr: when you tell people what you'd like them to do, it increases the chances of them doing that.
Yeah large EEE on ActivityPub feels like almost a given if they start to use it.
But should you block people from embracing a good thing, just because you're scared they'll try to extend and extinguish?
no one is preventing people who have facebook or instagram accounts from joining the fediverse by blocking meta. what they are doing, is preemptively taking action to ensure an immoral company doesn't do exactly what it has shown itself to be in it's nature to do.