The color codes and symbols aren’t at all propagandist.
Oh lol they changed the interface. Just a day ago or so the colours were the opposite.
edit: proof
I thought the same, then I saw the quote at the top of the page and realized it wasn’t strictly for information tracking
Just like red and green lights! :D
Some instances know their embrace, extend, extinguish history and some don’t.
And for those that don’t:
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Can you explain what that means in this context? How does defederating Threads prevent Meta from extinguishing anything?
- Embrace: Join the fediverse with your existing user base that dwarfs the fediverse’s existing user base, and with infinitely more money.
- Extend: Use your size, in terms of users and capital, to steer the direction of the ActivityPub fediverse standard to your advantage and your competitors’ disadvantage. You see everyone else as a competitor because you are a corporation seeking to monopolize the user base.
- Extinguish: See what Google did to XMPP for a concrete example.
Or what Google does right now with Chrome and web standards.
For those unaware of Google’s latest web browser malarkey: Web Environment Integrity
EFF/Cory Doctorow/Jacob Hoffman-Andrews: Your Computer Should Say What You Tell It To Say
Google is adding code to Chrome that will send tamper-proof information about your operating system and other software, and share it with websites. Google says this will reduce ad fraud. In practice, it reduces your control over your own computer, and is likely to mean that some websites will block access for everyone who’s not using an “approved” operating system and browser. It also raises the barrier to entry for new browsers, something Google employees acknowledged in an unofficial explainer for the new feature, Web Environment Integrity (WEI).
I genuinely want Gopher back.
I want to share information and to communicate. I don’t want every bowel movement tracked and monetizes. I don’t want 30 cross site requests when going to a news site. A single story should not require 10MB of JavaScript libraries.
I have no doubt that most of the authors of the original internet are aghast at what their high-minded creation has itself created.
But how would defederating prevent any of that?
The same way we prevented any of that up ’till now: by doing our own thing on our own terms.
It would make Threads unable to see content from instances defederating it and vice versa, preventing the Embrace step.
That’s a common misconception actually, any and all data available via federation is already public and easily scrapable even without running an instance of one’s own. Defederating only hides (in this case) Threads content from users on the instance doing the defederating, but the data is still public. Not to mention copies of it would still be fully available on any extant federated instances.
But they would still be unable to embrace (and, by extension, extend and extinguish) because users from Threads would be unable to interact with users from other instances. Basically, they’d be unable to get rid of a potential competitor using the EEE method.
But how could interoperability lead to extinguishing? That’s the part I don’t understand. By what means could Threads “extinguish” the network of instances that stay federated?
What is fedipact?
“i am an instance admin/mod on the fediverse. by signing this pact, i hereby agree to block any instances owned by meta should they pop up on the fediverse. project92 is a real and serious threat to the health and longevity of fedi and must be fought back against at every possible opportunity”
fedipact.online
This makes it just confusing? The pink heart = good, but the red cross = good too? But again the red cross seems bad as green = blocked.
Sorry I don’t get it.
- green checkmark = blocked
- pink heart = blocked, signed fedipact
- yellow exclamation mark = limited
- red cross = not blocked
It’s a silly hashtag för instances that are in a “pact” to block Threads
why is silly
Because the people signed the pact did it long time ago, before any details about Threads federation was known. It was a typical fedi kneejerk reaction.
is facebook
You’d have to be a dumbass to federate with these megacorps lol. We’re here precisely because of the decisions of one such company.
I guess majority on fedi are dumbasses in that case ¯\_(ツ)_/¯
Mastodon is pretty fucked up anyway because everyone is on mastodon.social.
This is why I love DBZER0
Nice, props to whoever made that site.
https://veganism.social/@nm should have added in the desc.
There seems to a mistake saying that Threads is not blocked by lemmy.zip, when we defederated them months ago.
I know you did, so I went over to double check. Didn’t find any threads.net under the “Blocked instances” section when I searched the “Instances” page. Because blocks have been moved to it’s own tab. The search was running the last few days from what I understand so my first guess is that it’s expecting the 18.5-style instance overview, didn’t find threads.net (again, since it’s under a different tab) and wrongly tagged you.
I’ll link this convo on Mastodon so the creator can check it out.
Thanks for the understanding and help 😊
We’re all in this together.
https://veganism.social/@registrert@mastodon.sambands.net/111604033659552504
Huh. You’d think more instances were blocking, given the amount of buzz.
Being generallky in favor of letting individual users make this call that’s… mildly encouraging. Of course I happen to be in an instance that is blocking, so…
It’s worth noting that this still splits Mastodon pretty much in half. That’s arguably a bigger concern than anything else Meta may be doing. They may not even have to actually federate to break Mastodon, which is a very interesting dynamic.
It’s worth noting that this still splits Mastodon pretty much in half.
Not half, much less than that is blocking Meta. It seems the split is ideological, which means there will likely never be a fediverse where we’re all together, alongside Threads. I speak of experience, I went straight to AUTHORIZED FETCH and whitelist on my masto as soon as I saw how many just didn’t care. But I don’t care about Zuckerbots dropping out of my field of view and they’re probably happy they don’t have to deal with someone as paranoid as me; believing that Meta would exploit us given the chance. So, win win?
It’s not just ideological. Many people and instances on the fediverse have minorities using them. These minorities rely on it to share and discuss in safe spaces. The federation of threads is a threat to these safe space.
Comrade Zuck doing us a favor and ideologically purging the Fediverse of all the liberals by extinguishing all the collaborationist instances. o7
We gotta pump these numbers up
What about limited, what is it?
-
You can follow Threads accounts after clicking through a warning.
-
People who don’t follow those same people won’t see their posts.
-
You have to manually approve followers from Threads.
Basically, it puts Threads in quarantine, without cutting off all connections.
I think this sounds way more reasonable. There’s will always be people like celebrities that I might want to follow, who will probably never be on mastodon or Lemmy. But I also understand the existential concerns for the future of the fediverse.
-
This is wrong. Rwn.lol blocked threads.net months ago.
Check my other comments about what could cause this and how to reach the author of the system.
Not nearly enough.
This is not an exhaustive list. For example, Instagram Threads profiles are available from kbin.social, which is not listed here, though.
True, but I got it hot off the press- Creator have been at it since last night so it’s still first edition of dynamic lists. He also said that there was missing information (like what you mention I assume) but wasn’t able to get the info from the instance.
