I used to think that there would be 1, main ‘Fediverse’ with all of the ‘big instances’ connected to each other. The recent Threads debacle has shown me otherwise.
The point of the Fediverse is that there is no one single entity, or group of entities, dominating it all.
Right now it feels like whatever the big instances do, we kind of have to go along with to be a part of anything. As the Fediverse grows, there will be more options to suit different types of users.
I think it’s fine if big instances federate with Threads and it’s fine if they don’t. People can just join instances that align with what they want. It’s not like defederating means being cut out of the Fediverse, that’s not possible.
Great design. I’m eager to see how it plays out.
You must log in or # to comment.
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
deleted by creator
I’m pro federate, but honestly, this seems fair. However Lemmy wouldn’t need it, as to see a threads post on lemmy, the person would have to @ the lemmy community in their post.
deleted by creator
Yep. And the ones that do know and want to post to our communities would probably have the right intentions anyway
All true, and making this a feature would simply be implementing the inverse of the new capability… overriding an instance level block instead of imposing one not already at the server level.
deleted by creator
I think you only made a case for having two or more levels of instance block, that already exist. One due to objectionable/illegal material that cannot be overridden, and another for something like threads where a significant number of users may not want to be opted in automatically, or want to block it due to purely ideological, non-illegal reasons, which would effectively be put in place by automatically adding the instance block to user accounts that can be removed at any time, which arguably can already be done with minor changes. That’s essentially what dansup is doing, complete with including a command for Pixelfed instance admins to apply the optional block to all user accounts.
That’s not how Bluesky does it. Sure it empowers users which is great but if there is a PDS for example with lolicon, one I don’t see it making past the content filters but if it did the BGS/Relay would blacklist that PDS
Jerry Bell did it first!
Good to see more reasonable people in all of this.
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. :)
Thanks for the tip!
I am unreasonably excited about this. Where I live, there’s no decent options for Internet or cell signal. Which means normal calling/texting doesn’t work, and regular Wi-Fi calling/texting is choppy at the best of times. My whole family uses WhatsApp for everything. I’m hoping I can get them to switch to something like this once it’s stable.
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.
Well not technically yet. LW is still on 0.18.5
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.
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, …
Can’t you block threads yourself once .world updates to 0.19.0?
That’s such a misinformative false ‘solution’ people keep peddling…
No, blocking Threads on the individual user level does not stop comments made by Threads users from showing up on federated instances, even for users who block Threads.
That means users who block Threads will still see hate/extremism and are still subject to potential harassment by toxic Threads users.
I think there are many reasons to block threads but is toxic users one of them?
There are lots of toxic users on Lemmy too. Should we be blocking lemmy.world or lemmy.ml because they have a few toxic users too?
deleted by creator
On the other hand, interacting with Lemmy from a Twitter style timeline sucks, so I doubt we’ll see any Threads people on here.
I wouldn’t be so sure about that. I’ve seen people interacting from Mastodon here already.
deleted by creator
What are boosts?
deleted by creator
In a Mastodon level this is not true. Blocking Threads.net prevents you from sharing your content with them and for their content to show up. Pixelfed has also enabled user level Authorised fetch which will prevent Threads.net from attempting to fetch that users content
That’s good to know. Thanks.
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.
Would you create a community, and if so, what kind?
I created !vans@lemmy.world and have been planning on trying to revive my efforts to grow the community, but I’m sure hell not doing that if Threads is being incorporated. I’m instead going to strip the community of all of the content I posted.
I also want to create a community for my city, but I’m never going to do that on an instance that allows Threads/Meta incorporation. Also have wanted to recreate r/OldSkaters from reddit.
If I wanted to deal with Meta, I’d make an account on one of their privacy/rights-infringing platforms.
As established already, blocking Threads does not block user comments from showing up. Even if it did, I still would not host a community on an instance federated with Threads unless there was a way for the communities themselves to fully block Threads interaction.
But the only way to fully block Threads is by defederating from it.
Nothing ever stopped you from creating you own instance. With blackjack and beers.
I don’t get, even if you are part of .world and they are federated with threads.
Can’t you just personally block all threads?
You personally can defederate without it affecting anyone else.
No, that’s a half-measure at best… It only blocks Threads posts from showing up in your feed. It does not block Threads users comments from showing up on federated instances, even if the individual user personally blocks them.
I am legitimately fearful for LGBTQ+ users, as their community members have already been harrased on Threads by the far-right.
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.
What kind of “tasty data collection and surveillance” will Meta have access to that they didn’t before federating?
they will have an excuse to do it openly instead of trying to do it secretly and inevitably getting caught
That doesn’t answer my question.
But the fact they can just defederate makes it much harder.
How does defederating make it harder?
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!
In some ways, I trust my data more with a highly scrutinized company such as Meta than a random weirdo spinning up his instance with a home server in his cabinet.
That’s what I don’t understand about the pushback. Yes we all want privacy, but Lemmy here and the fediverse is not built around the idea of privacy. It’s literally a protocol that shoots out whatever you type to anyone who wants to listen. You can type on any server and it’s going to end up on any other server. Can’t be mad because someone like Meta is seeing that and going “Hm, we have servers, we could listen to that data.”
neither of you are looking at all the data harvesting that occurs on platforms like Meta and Reddit. Telemetry, keystrokes (not just submitted, but any key typed iincluding backspaced ones), and more, and NONE of that is harvested on this platform.
That’s why I’m not switching or anything, my user will be on my instance, but if they federate and users true the surveillance instance that’s on them
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
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
I agree, the original idea of the fediverse is awesome. However, I believe the big players will decide almost everything about it in the end, simply due to influence on decisions being made.
I’m kind of happy as long as big tech is not running it
Wait for it. It’s coming. That’s why Meta is doing this. We’re in the “embrace” phase of “embrace, extend, extinguish”.
I don’t see how to avoid it, unless the courts step in. The only reason why we’re using the World Wide Web instead of the Microsoft Wide Web is because the US sued Microsoft and won.
FOSS 4 Life, bb!
