[1] https://fosstodon.org/@kev/110592625692688836
edit: More info here: https://wedistribute.org/2023/06/fedipact-blocking-meta/
If this rumor is real and Threads takes off, you can still stay in whichever instance that you like, but now be able to get updates from the artist, the experts, educators, politicians, the influencers that would not have joined the Fediverse otherwise. And more importantly, more people now can get updates from you. Reach might not be something you personally appreciate but it's very important for content creators.
Now, I personally I think it's trying to swim up the waterfall & ultimately worse for everyone, but: Mastadon specifically has had a strong history of being anti-search, anti-scraping. You aren't supposed to be surveiling folks at industrial scale on the fediverse.
There's widespread skepticism about Meta respecting rules of the road. Having a huge giant shark join the pool of lots of little fish seems like a scary proposition. How we can still protect & have sovereignty over our different fedi-sites is a real question when there's a company with so much technical, economic, and popular leverages.
I'm honestly pretty skeptical about the fediverse aspect of Threads. It suggests that if I open a new fediverse instance and follow their accounts, I can suck in their timeline and do with it whatever I want. In particular, to bypass ads.
Hence, I could make a "best of Threads" fediverse instance without ads. Or maybe put my own ads on it.
Or, I could build my own client on top of the Threads instance.
None of this sounds very Meta to me.
It's the opposite of naive: it's extremely well thought out and heavily deliberated. Making so many things "public" by default is an invite to people. It's an intentional welcome mat in old school "Internet 1.0" sort of way. But just because you want to welcome people doesn't mean you have to welcome robots (crawlers, etc). Many instances do that deliberately in a very old school "Internet 1.0" way by saying so in their ROBOTS.TXT file (in addition to other places).
In the old web, crawlers were expected to read ROBOTS.TXT and no matter how "public" they thought the website was they found, ROBOTS.TXT was supposed to be the final word.
Anyone scraping or making searchable "at will" random chunks of the Fediverse is easily violating some number of ROBOTS.TXT files. That is an ancient technical convention that isn't new or naive. The internet knew even then that bad actors would ignore ROBOTS.TXT files. The old internet learned to name and shame the bad actors, and in some cases would back that up by force with firewall blocks and in some cases lawsuits. Mastodon does that too. That's why a lot of Mastodon instances are preemptively blocking Threads, because they don't trust Meta to follow good behaviors such as checking ROBOTS.TXT, because Meta hasn't shown a history of being a good actor there and because Thread's privacy policies seem to imply that they don't care to be a good actor for their own users (to the point of not supporting EU users at all because GDPR is "too hard"), so it makes it much harder to assume they will be good actors with respect to all of the conventions around Mastodon data including the classic ROBOTS.TXT.
The Mastodon culture of "public for people, but not for ROBOTS, or only select ROBOTS" is an ancient internet tradition. It's hard to call that naive, when it has decades of history and internet social norms (including good outcomes) behind it. What's naive is thinking that because some major corporations stopped respecting good social norms in the name of increased ad revenue that those norms no longer apply and "anything technically possible is allowable". Read the ROBOTS.TXT in the room and stop being motivated by technology for technology's sake without respecting ethics. Be a good actor in any ecosystem.
But it's still wishful thinking. We live in the age where AI is so bold as to scrape the crap out of even the largest of other big tech companies without blinking. Without permission, attribution, compensation. So surely a little Mastodon scrape isn't a problem.
There's no need to talk about how unethical it is, we agree. Problem is that it's hard if not impossible to stop. That what I mean by naive.
I don't think it is is exactly "wishful thinking" to believe that the way we get back to promoting ethics in software is expecting people to behave ethically. We sure are doomed to be disappointed when people turn out to fail us, but that's all the more reason to fight for it, to remind people what ethics are and why a polite society needs them. All of those disappointments are teaching opportunities, if people are open to listening.
(Will Meta learn anything at all from all the Mastodon instances that have pre-emptively blocked them on ethics concerns? Who knows? Mastodon can teach, but it can't force the student to learn. Is it worth Mastodon trying and fighting to teach Meta, no matter what happens? I'd say yes. Ethics are as much a social construct. How we talk about them, how we try to teach them, that says a lot about who we are and what our ethics are.)
I'd rather have even the attempt at ethics than despair that "ethics are technically impossible to enforce". We know ethics can't be programmed, that's why we have to enforce them socially.
Regardless, I'm predicting that if not for a cultural clash, many instances may de-federate due to the compute cost.
Then those content creators can set up their own (or pay someone else to do so) Fediverse instances. The Fediverse is decentralized on purpose to avoid the kinds of lock-in that FB/IG/etc. require.
I want no part of that, which is why I don't use such centralized services. As such, why should I allow those same centralized services run by greedy scumbags anywhere near my instance(s) or even my consciousness?
Can you provide me with a cogent argument as to why, after making the effort to get away from those toxic ad-riddled environments, I should welcome those same folks into my world? I imagine that could be an interesting discussion.
That’s a pretty doubtful condition, especially if Threads becomes too successful for the Fediverse.
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
> Fediverse users are already planning to boycott any instance
Though if this is true, yeah, I dislike that too. It should be individual admins’ choices.
I wager most Fediverse users aren't worried about this (at least speaking for myself). The status quo is 2 or 3 big private companies and a few thousand federated alternatives. If Meta betrays the community, things will go back to square one and core functionality of their app will start to falter. They need the community more than the community needs them.
I'm not worried about it really because I think the ethic of fediverse as such that they will be quickly de-federated. But it won't be fun along the way.
Defederated or not, Meta will have pretty much zero bearing on the instances outside their bubble.
You have to be kidding me. The entire fediverse is little over 1M MAU, almost all of them not monetizable. So...tiny and useless. Threads can launch whilst being fully defederated and instantly become the fediverse.
The ActivityPub ecosystem stands to lose nothing either way. Meta is walking a fine line with the remainder of the community that trusts them, but stands to integrate into a pretty nice system if they pull things off.
1. Meta conditionally federates with Mastodon instances that sign the deal (allow ads to be pushed, data to be collected, etc)
2. Small/vocal instances reject the deal and defederate.
3. Some large instances do take the deal.
4. Small/vocal instances defederate from the large ones.
5. Large Mastodon instances become pointless as they're isolated from the rest of Mastodon and have no real value over simply using Threads.
6. Large Mastodon instances implode, and the Mastodon fediverse becomes even smaller than it already is.
Nobody outside of the HN crowd gives half a fluff about distributed social. They'll use the one that lets them interact with people they know. If that means they can talk cross-instance, sweet, they will. If they can't, Mastodon and ActivityPub in general continues to be a pain that the majority wont bother with.
If that's Mastodon's goal, fair enough. I think it's a bad goal.
But indeed, if the goal is to self sabotage and remain an irrelevant corner of misfits, all good.
Yes instances occasionally have issues... But I've experienced less outages than on twitter.
Yes there are unsavory types on some servers, but in my experience most are pretty good at defed-ing from them if needed, and you can block/mute individuals.
First, the technical/usability part...
Picking an instance is a major hurdle. There's no usable feed from the get-go. Following people, especially from other instances, is not intuitive. There's no functional search, no quotes.
Mods are volunteers and can wipe you out at a whim, or just decide to quit the instance. They'll also regularly defederate with other instances, which means they break your followers and whom you follow. There's a perpetual worry of losing everything. In any case, media attached to your content is regularly wiped out, to save costs.
You'll have a feed and see like/boost/whichever icons showing zero. Then you open the individual post and it has non-zero values. Which still is wrong. The original post might have 100 likes but your version shows 15. Not only will it lag, it may never sync as this entirely depends on users on your instance following particular users on other instances.
Worse, the same is true for replies. You will not see most other users replies as those replies are only federated if that user is followed by anyone from your instance. Hence you'll get an original thread with tons of similar replies because users are not seeing the other replies.
I could go on, but almost nothing about it works correctly in the way conventional social media does. It is sorely lacking in basic features and features that are there work poorly.
Second, the cultural part...
Mastodon is basically a community of leftist tech folks, lgbtq, and general misfits. Nothing wrong with that, everybody deserves their place. The problem is that they developed a culture of anti-everything and extreme safetysm.
The bar for hate speech is so low as to exclude most people. They're against any type of commercialization, institutes, influencers. They're against any type of growth or improvement and consider the broken parts of Mastodon features, not shortcomings.
I don't mean to escalate this into a culture war discussion, I'm saying that this attitude is what sabotages Mastodon as a whole from improving and growing, and possibly becoming a much larger and more serious alternative network.
The culture is so cynical and counter productive that even those in the ideological bubble can't take it anymore, this constant in-fighting.
None of this means the entire Mastodon experience is useless. I have used it and it somewhat works. But the more you understand about how it works, the more you realize it can't possibly be a replacement for conventional networks.
It's worth noting that the only time I've payed any attention to twitter is in the last several months, so it's weighted to be worse than it was prior to recent happenings.
The server where I have an account has had downtime twice in the past 200 something days, and had search go down once in that time frame. Occasionally I'll see an update from another server saying "<search|image hosting|replies> are temporarily down", but life goes on fine and they rejoin when they can.
Believe it or not, most Mastodon / Fediverse admins & users aren't interested in taking over the world and having a huge reach. They just want a nice community.
I do not plan to follow people who are excessively toxic or negative. If Threads launches, and 100% of its users are toxic, I will not follow anyone on Threads. But that seems unlikely to me.
Edit: I suppose it's true that people I don't follow can still reply to my posts. Idk, I suppose it's possible that federating with Threads would make my replies super toxic. But, like, let's see how the community develops first.
I have zero issue with Meta using ActivityPub, cause whatever they try, it makes them at least somewhat permeable in theory. I do have zero intention of interacting with them on any level though.