Interesting new data on Lemmy instance federation with Threads, ordered by Active Users descending.
Source: https://fedipact.veganism.social. New data gathered on 2024-04-28.
Interesting new data on Lemmy instance federation with Threads, ordered by Active Users descending.
Source: https://fedipact.veganism.social. New data gathered on 2024-04-28.
Why is the color for blocked green? If you’re stopping something it should be red.
because blocked is considered good and federated bad…
If you block the road so someone doesn’t drive off the end then you would not use a green sign. I understand the thought process, I just don’t agree with it.
Depends on your view.
On the road you’d use red to indicate that it’s blocked.
But on an issue tracker where blocked is the desired, or in the road scenario – safe, outcome, green would be resolved/safe, and red would be unresolved/unsafe.
The source is fedipact, the people in favor of blocking. So blocked = good = green You could call that biased, but i think its very reasonable.
Generally green means go and red means no-go, regardless of which is the desired outcome.
I agree but its a matter of framing. In safety systems green is safe and red is danger. This would fit here too.
I’m not aware of bugs in the Activity Pub protocol that make federation unsafe. If bad actors can affect safety, the protocol should be overhauled.
Do you have any understanding of what fedipact is about? Obviously this not about software security dangers and rather about the danger that large commercial entities like meta bring to the longevity of a free fediverse.
Unsafe for the forest, not unsafe for the trees.
Which is to say - not unsafe for individual users or from a day-to-day operations perspective, but unsafe in a platform survival way.
Major companies start working with open source projects until they’ve added a significant amount to them, then they start rolling out proprietary parts that work with their additions, then they move away from the open source project, leaving the original project incompatible with a bulk of its users and platform. The project finds itself both quite big and lacking support, with adopters moving to the closed-source implementation(s). This is often called Embrace, Extend, and Extinguish, and it’s been used to harm Open Office formats, messaging platforms, and is currently being used by Google with Chrome to strip away user privacy and redo how the internet works, for the sake of their advertising empire.
Facebook and BlueSky activity pub integration efforts should not and can not be seen as an altruistic gesture.
It’s not the protocol, it’s the users. There’s a vocal group that would rather stay small, niche, and remain in obscurity away from the rest of the world. They fear that they’re going to lose their pedestal and megaphone because their quirky skewed view of the world will be drowned out by mainstream worldviews. They’ll then mask it with claims of “privacy”, “EEE”, or “anti-blahblahblah_that_I_dont_like”.
Big companies did wonders for Mastadon’s adoption, and will likely do the same here. The lack of users and content will be resolved when it happens, and I just hope I can hold out long enough until that happens.
Those shouldn’t use a federated platform then.
Green means good and red bad as well, stop/go is another way to describe it, but colored statuses are super common in software stuff. All my monitoring systems I use are green=good, yellow=warning, red=error/bad
Yep.
Sometimes “off” is the desired state for something so green is a good way to show it
the main idea behind the blockade is that Facebook implementing ActivityPub can easily overwhelm any instance small enough in infrastructure through the sheer amount of traffic that such connection would have on the rest of the Fediverse (case and point, the occasional waves of Twitter users moving to Mastodon), and with fewer instances it can get easier for the company to take advantage of that to take over the network and make it monopolized again.
edit: i didn’t read your comment properly, i thought that was lacking context. sorry x.x
edit 2: https://lemmy.ca/post/11771031 someone else shared this thread, it’s an interesting and important read