hawkwind

joined 1 year ago
MODERATOR OF
[–] [email protected] 6 points 1 year ago (15 children)

Was the OP a blahaj account, or someone from a different instance?

[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 3 points 1 year ago

Say “Teyo, Geometric Tactician” 3 times really fast.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 2 points 1 year ago (2 children)

You mean blocked instances right? AFAIK an instances “blocked users” is not published in aggregate. You’d have to comb through the modlog.

[–] [email protected] 8 points 1 year ago (2 children)

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!

[–] [email protected] 2 points 1 year ago

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.

[–] [email protected] -4 points 1 year ago (1 children)

I'm not sure who you are quoting, or trying to reason with, but I agree with your sentiment. A profit driven company will do everything it can to profit. Are you trying to say we should "only" be mad at the government and not the company, in this scenario?

[–] [email protected] -3 points 1 year ago (1 children)

I get that, and I support everything you're saying. It feels like the workers are getting played by the companies though. Workers should be lobbying for rights to the state, federal and municipal levels, but this feels like a "red herring" of a bill to get behind.

view more: ‹ prev next ›