The most reasonable solution I’ve seen so far, from the pixelfed and pixelfed.social creator
Not the solution I was hoping for but it's an extremely reasonable compromise. I've never heard of selective authorized fetch. Pretty sure he just invented it.
FOSS ingenuity at work. All it needs is adaptation and adoption.
Authorised fetch has been a thing on Mastodon and I believe Akkoma too. I don't know if Pleroma, Soapbox or Misskey have it though.
Authorized Fetch has been a thing for a bit on Mastodon at least - but as far as I can see it's a global toggle rather than saying "If you present as a domain on the blocklist then you must be authorized to fetch this resource" (the selective authorized fetch I assume they're talking about).
Never used Akkoma though, so I can't speak for it.
Yeah the selective part I think is new. I believe Akkoma's authorised fetch is similar to Mastodon, though I've also heard it came at the cost of breaking MRFs (essentially policies to handle incoming messages, that can be custom-written if needed)
Unless I'm wrong, the unique thing here is that auth fetch is always off for the server. It's on only at the user level and it's only on at that level if a user has an active domain block.
That could actually solve a lot of problems for people. Admins are reluctant to enable it server-wide because it causes a bunch of problems. The biggest being that it breaks federation with servers running older software (Mastodon v <3.0 I think) and with other services (Pleroma, maybe others). It also uses more server resources. But there are always people who think it's worth it.
For the lazy:
After some careful consideration, I have decided to block threads.net on pixelfed.social and .art by default
However, users will have the ability to unblock the domain
Soon we will be selectively enforcing authorized fetch for accounts with domain blocks so as to provide the best of both worlds.
(I'm also shipping a command for :pixelfed: admins to easily add user domain blocks for all local users)
I'm eager to hear your feedback!
That's a good solution. Keeps the all feed clear of threads content while allowing users to opt in
Did Dan ever get the messaging service Sup going? Tried to look it up, but his name being Dansup is throwing a wrench in my Googlefu.
@supapp@pixelfed.social
Releasing in beta soon!
Also searching for #sup in Mastodon has been a good way to find information about developments. Not so necessary now that there's an official account I guess. :)
Yeah. And now that we have account migration we can switch more easily.
Unless you want content and more people to interact with.
Like, people keep saying "oh yeah you can jump instances" as if that wasn't possible on Reddit. You could go to different subs or make your own. But what good were most of them? As long as there's a "default", a main "hub", people will go there, and that's where everything will be happening. The alternatives and smaller instances will be starved out.
Centralization is not about the software, it's about the people. Users centralize where others are. So when the big hubs are allowing threads to poison the well, it's poisoning the thing most people want to drink from, and the thing new visitors will be most likely to drink from.
Threads represents something that a lot of people came to the fetiverse to escape. If threads wants to join, fine, but I believe it is in the best interest of all of us if there is a large alternative "cluster" that is separate from it rather than being tied up with it.
A separate galaxy in the fediverse, that says in big red neon lights, "Get your corporate bullshit away from us. This is our space, for people, not for you to make money." And if we let them in immediately, it becomes increasingly difficult for that galaxy to retain that identity.
And I'll just gently point out that once Threads joins, separating from it will not be easy because you will have Threads users here actively pushing back on the separation.
I see you really care about the fate of "the others". I don't know. Maybe that's the right reaction but if the people who came here bacause of threads or from threads will disappear again I think I won't bother much. I liked it here with even less people around so I don't really care how many thousand users we have. Fact is the decentralized internet and ActivityPub are the future and there will always be a way.
Finally someone gets it!
I'm out of the loop
Last thing I vaguely remember about a defederation incident was honeybear or something like that upsetting everyone
Essentially, Facebook's Twitter competitor Threads is gearing up to join the fediverse by integrating ActivityPub into their platform. Don't take my word too much on this but I believe this is due to the European Commission's Digital Markets Act which requires interoperability (similar to how iOS now requires sideloading in the EU). This is essentially their cheap way of complying.
The fediverse has a strong hatred of Facebook, for various reasons (from petty things like "embrace, extend, extinguish" to much more serious things like Facebook's compliance in the Myanmar genocide) and a "pact" was enacted of fediverse instances that are simply outright blocking Threads. Part of it is the fear that Facebook will federate its moderation problem and cause a headache (which, in my opinion, would be better dealt with by limiting Threads to followers only - Mastodon and Pleroma allow this).
Opponents of the Fedipact are optimistic this will help a more mainstream audience warm up to the fediverse. The fediverse has a reputation of being unwieldy and complicated to newcomers, and having a major platform like Threads integrating ActivityPub might help bring them in and see what it's like. Toxicity is cited as a reason for defederating Threads, but IMO I see more toxicity towards newcomers and outsiders coming from the people already on the fediverse, so I've been quite apathetic to the Threads thing.
Yeah I'm in a wait and see with my instance. People act like it's one and done. When they start they'll be just another server to me. If they start becoming hostile and everything coming from them it's terrible then I'll defederate. Same as any other server.
People are worried about data being misused but, I'm sorry, that's what happens when we publish to an open protocol. Anyone can use it however they want, and yeah, they're are scum usage for it
Agreed. I think Lemmy is more public than Mastodon and co. which do have some privacy settings for posts and account follows, but ActivityPub is inherently a public protocol. Appreciate everything you've done for Poptalk btw!
Hexbear.
I feel like honeybear suits them better. They seem sweet like honey in how they support minorities and protected classes, but then they support viciously genocidal dictatorships like Russia and China
The controversy you are referring to is regarding specifically .world defederating Hexbear "preemptively" before the latter could federate with anyone, out of fear that the "annoying tankies" may overrun everyone else. Since Hexbear is a relatively small platform run by volunteers like .world is, and the basis on which the defederation was justified was shaky at best, a lot of users raised an eyebrow. There was a similar move by .world later on where they defederated from Lemmygrad, another "tankie" instance, due to alleged hate speech of which the admins failed to provide a single example, and it was clear as day that .world admins just wanted some excuse to defederate away "the evil communists".
In this case, the situation is different, because it involves a lot more than just .world. A large, for-profit instance Threads, run by Meta, is opening up to ActivityPub, and people are afraid of the reasonable possibility that Meta is attempting to either destroy or absorb the Fediverse as a whole. Besides the shitty corporate attempts in the past, Threads is also overrun by a lot of algorithm induced hate speech and far-right extremism, and there is a legitimate concern that this will spread to instances that federate with Threads.
Hexbear (and others like Lemmygrad) are different in that they are still part of the Fediverse, they are run by volunteers like most instances, and remain federated with other large instances such as lemm.ee. But the fact that hate speech is rampant in Threads yet .world admins want to "wait and see" make the Lemmygrad defederation even clearer and funnier in retrospect, lol. I complained back in the day when Hexbear was defederated that I'd rather let users choose for themselves whether they wanted that or not, and I got told to go to another instance. Now that we are federating with Threads anyway, might as well do that.
Edit: Typos
You don’t have to look far on hexbear or lemmygrad to find people cheering on the murder of Israelis on October 7th or denying genocides like the Holodomor so I’m not sure what you’re talking about when you say neither instance is hateful. Meanwhileongrad is full of screenshots of ridiculous hateful bullshit.
Edit: I might add that they’re extremely ban happy and yet would cry when their rants were deleted or when they received bans for spamming on other instances. Blatant double standard. Shit, I’ve had comments deleted for “hate speech” from Lemmy.ml for saying that Hamas and Iran are a big part of the problem in the Middle East.
Most instance admins are federating with Threads/Meta. Even if you block the instance yourself, it doesn't prevent you from seeing Threads users' comments and the hate, harassment, and extremism on that platform from spreading throughout federated instances.
there is no one single entity, or group of entities, dominating it all.
This is what Zuck wants to change with Threads.
It's not. He wants to create a social media that exploits its users without being accused of monopolistic behaviour.
All the tasty data collection and surveillance with none of the calories.
Edit: Since so many people are misinformed: No, blocking Threads on an individual basis is not a solution. This only blocks posts from Threads showing up in your feed. It does not block Threads users' comments from spreading hate and extremism throughout federated instances, and lemmy users will still be subject to potential harassment from Threads users. (See the harassment of the LGBTQ+ community on Threads for examples...)
Here's a comment of mine that states my argument against federating with Threads.
Also, I was not trying to debate the issue here. I was looking for recommendations for alternative instances... I'd appreciate anyone actually responding to my comment.
Original comment: Anybody have recommendations on a decent instance that won't be federating with Threads? Maybe one that allows community creation but isn't full of tankies?
I'm jumping ship from .world if they go through with federating with Threads. Such a shame to see the effort put into building this great instance come undone.
This place decided to disregard what the majority of their users want and turn the neighborhood to shit way faster than reddit. I thought we'd at least have a couple years before instance admins started selling out to such a shitty company that's going to make the fediverse a less safe place for their users.
Meta will also do anything they can to EEE and I'm not convinced the fediverse is as invulnerable to such exploitation as some users seem to be.
I was looking for recommendations for alternative instances… I’d appreciate anyone actually responding to my comment.
OK.
Largest Lemmy instances blocking Instagram Threads are (according to fedipact.veganism.social) lemmy.ml, lemm.ee, lemmy.ca, Hexbear, feddit.de, Beehaw, Lemmygrad, lemmy.dbzer0.com, lemmy.blahaj.zone, discuss.tchncs.de, sopuli.xyz, aussie.zone, feddit.nl, lemmy.zip, midwest.social, feddit.uk, mander.xyz, ...
Just because Lemmy.world doesn’t agree with about defederating with meta doesn’t make them sell outs. Like you said, you are jumping ship; just like the fediverse intended.
For better or worse, Lemmy.world is intended to be a catch all instance for normies so it makes sense why they would not defederate from meta.
There are lots of hypotheticals here.
I expect the lemmy.world admins to block servers that are frequent sources of hate and extremism. I don't expect them to speculatively block servers because some people guess they might be. I'm pretty skeptical that a majority of users want preemptive blocking. I don't, and the votes and comments I see in most conversations on the subject suggest that's a position held by a very loud minority.
I'm not sure Threads users will be all that interested in interacting with Lemmy. It's an awkward UX to participate in Lemmy conversations from Mastodon, and I believe Threads has essentially the same format. Threads is likely to have a bigger impact on Mastodon servers, and I don't think any of us can reliably predict what that impact will be yet.
I disagree on user support. Look at the posts heavily discussing the matter, and also pay attention to the vote counts.
Also, it's not a hypothetical when there is already a systemic issue and the company has a notorious history. Look at my comment here for my fleshed out argument on this subject with citations.
I wasn't intending on debating the issue here; I was only looking for recommendations on alternative instances.
Same. So what if someone doesn't want to federate/defederate, but I don't think people should be hassling admins to defederate
You can always, as a client, block individual instances in your settings
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy