Not fire Chef.
hawkwind
joined 1 year ago
Not fire Chef.
Ah yes, the “local taxi lobby.” Uber helped show a lot of us what a fucking joke that is, not just in Ottawa.
Innovation, choice, quality and freedom are the choice spices for capitalism soup. These shit-cook-legislators kept sprinkling in taint like protectionism, cronyism, extortion and corruption thinking nobody would notice. Well guess what? Now it’s just taint soup.
Why does it matter who’s serving you taint soup? The problem is there’s no other soup and they keep telling you it’s fine.
There never was love for flatpaks and there never will be. I’ll never forgive them for killing my son.
NSA Access Only!
Was the OP a blahaj account, or someone from a different instance?
Ahh. I see. I took a look at the script. "Blocked Users," is not reported by an instance, but rather It's calculated by this script by looking at "Blocked Instances," which is reported. How many active users each blocked instance has and then summing this together, the script shows "BU." I was thinking it was an explicit list of users the instance blocked based on ban/block lists.
It's a derivative, but still useful metric, I guess. BU could be high, but BI could be low and vice-versa.
This could always change at the whim of an admin as well. It’s good to have admin “teams” and even foundations, but a lot of the time there’s one person making those decisions.
Users and communities could be more portable. Admins should get to decide what is on their instance for sure, but right now there’s kind of a “lock in.” Which give admins disproportional control / responsibility. IMO.
You mean blocked instances right? AFAIK an instances “blocked users” is not published in aggregate. You’d have to comb through the modlog.
A quick, but a little dirty solution for this, would be communities having “tags” in their metadata. This wouldn’t prevent spam, or an accumulation of four trillion tags, but you could easily add “only these tags,” or “not these tags,” to any feed. User objects have metadata that is used like this (as the “bot” flag) already. I’m just familiar enough with the code to know it wouldn’t be a slam dunk, but it’s also not a breaking change or re-write!
More “portable” and secure identities would have been a good feature. The client could have handled most of the crypto required for signing and validating content. As it stands now, the instance Admin has complete control over your identity. Portable communities would follow that easily.
Most of the syncing issues are actually between the large instances or instances that having performance issues.
If the blahaj admin(s) are working in the best interests of their users, and/or moderating out criminal content then that’s just swell.
On the other hand, if they’re trying to control other people… that’s bad form.
I always cringe when I hear: “you live under my roof, you live under my rules.” This has that kind of “feel;” yea?