I love the idea of taking on a monopoly, but I don’t like that, without regulation, it has a low chance of success, and the consumer gets to suffer as the monopoly fights back.

Resume field would get an api endpoint that only returns a json resume, and only if the request header is application/json. And the json resume would have embedded json.

I mean, yea. Happy to have AI as a player in the free market, the problem is that it requires a $0 salary so, kind of unbeatable as far as capitalism is concerned.

Why pay $1 to make $2, when you can pay $0 to make any number over zero? It scales infinitely, unlike the planets resources or human tolerance.

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.

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.

I had a “bearstein effect” moment just now. I had thought wireshark sold out. Like “Wireshark by Rapid7,” but i just checked and it looks like they’ve stayed the FOSS course! Way to go!

FYI for anyone looking to deface more instances, That list is only updated every 24 hours. Depending on when it last run on your home instance, the info could be out of date.

You’re not misunderstanding. They just solve more than one issue, and create a few too.

That’s a personal preference though. You don’t have a need for a relay. There are more than a few people who want to run their own instance and at least browse all the things without having to subscribe to them. This is a news aggregator at the core after all.

I’ve been pondering trying to make one, but it’s not going to be a cake-walk. The tool (that was a script) I wrote ruffled some feathers for it’s potential to destroy the lemmyverse. While I don’t believe that could happen. I’m still interested in something easier and more integrated.

The theory is simple and I am willing to take a stab at it, but there might be road blocks trying to make or incorporate changes to the actual lemmy code.

That makes more sense.

So any comment or post?

I actually wrote it with the flip side of your centralization argument in mind. If a community exists outside of the popular ones a user may never even know of its existence. Having more show up SHOULD be better to prevent centralization no? It requires the users to change their browsing behaviour but at least they don’t have gonsearching offsite.

Thanks! I’m sure you’ll chime in when the lemmyverse falls over because of this irresponsible script.

Your argument does not gain validity by adding irrelevant verbosity:

Federation ain’t doing great.

The linked issue has nothing to do with this script or lemmony.

Federated replication load scales with the number of instances multiplied by the number of communities they subscribe to.

That’s a hasty generalization that you just made up.

Server counts are growing at ~10x per month.

That’s great! I hope they keep growing!

The defaults of this script encourage single-user instances admins to bump their sub count ~70x from something like 100 communities to something more like 7000 communities.

Nobody is encouraging anyone to do anything.

Users of this script actually literally don’t understand how federation works. They think they’re proxying through to the upstream instance while they browse rather than getting firehosed with the entire lemmyverse by they’re asleep.

That single user asked a question and got berated by a jerk.

It doesn’t take a rocket surgeon to figure out that global federation worker queues are not in great shape, or that a default that encourages single-user instance owners who have no idea what they’re doing to bump their sub count 70x isn’t helping the situation. If you think this is in my head I can’t help you. But I can help others understand that running this script with default settings is an awful and unnecessary idea.

You can help others understand what it is. That’s a great thing to do. It would be nice if you could do that without being a dick.

I don’t really think so, but i’m open to working with anyone if they see this happening, up to deleting the entire project.

My dude, I appreciate your spirit, but we’re not going to focus on your irrational fear of abuse. I’ll defend myself for being accused of any such thing, or for being irresponsible. This is intended to make things better, and there’s no evidence it’s doing anything other than that.

If you want to contribute, by all means, show us where there is a problem, other than in your imagination, and it will be seriously considered. Until then, your opinion is still valuable, but you are speaking with authority about something you know little of.