892
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 23 Jun 2023
892 points (100.0% liked)
Technology
37574 readers
781 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
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.
I can imagine all sorts of technical points like how the firehose will be load-balanced so as to not overwhelm any instance, or what metadata they should include in their feeds. Meta also has a lot of AI and moderation expertise that could be of benefit to the Fediverse once it grows into an attractive enough target for the troll farms and spambots.
Quite frankly, the sooner that festering cesspool that is Twitter is killed off, the better off the planet will be. If it takes Meta to wean the talking heads like Oprah from Twitter, so be it. It would be better if Oprah set up her own instance, but that's unlikely to happen, media businesses still haven't understood they need to take control over their distribution rather than the easy way of going through big social networks that will stab them in the back when expedient like Facebook deprioritizing media outlets from users' feeds.