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.
Kbobabob@lemmy.world 3 weeks ago
Why is the color for blocked green? If you’re stopping something it should be red.
unexposedhazard@discuss.tchncs.de 3 weeks ago
Takumidesh@lemmy.world 3 weeks ago
Generally green means go and red means no-go, regardless of which is the desired outcome.
unexposedhazard@discuss.tchncs.de 3 weeks ago
I agree but its a matter of framing. In safety systems green is safe and red is danger. This would fit here too.
woelkchen@lemmy.world 3 weeks ago
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.
Passerby6497@lemmy.world 3 weeks ago
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.
laurelraven@lemmy.blahaj.zone 3 weeks ago
Yep.
Sometimes “off” is the desired state for something so green is a good way to show it
Wilker@lemmy.blahaj.zone 3 weeks ago
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, 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.
14th_cylon@lemm.ee 3 weeks ago
because *blocked( is considered good and federated bad…
Kbobabob@lemmy.world 3 weeks ago
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.
Monument@lemmy.sdf.org 3 weeks ago
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.