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.

If the only criteria to be in a private channel for admins is being an admin, there’s no use making it private. ;) Unless your just looking to filter out bad actors who don’t want to take 5 min and 5$ to make an instance.

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?

People can defederate from an instance for any reason they want, but if I get what you’re trying to say: you think people should defederate from any instance that has a user that subscribes to all of their communities.

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.

Yup. 256 GB should be enough database space for anyone though.

I think your idea is on the right track when thinking longer term and assuming the worst case in both design and admin behavior. :)

The whole network needs to be split into “active” and “archive.” New activity (or at the very least stubs to where new activity is happening) needs to be updated regardless of where it occurs without having to capture anything extra.

It increases load during execution. Afterward it’s not significant. My instance is heavily instrumented and monitored. The load this incurs subscribing to 24000 communities is less than adding a single, moderately active user to your instance.

It’s a huge miss if the intended design was to silo information.

What this provides, as far as I’m concerned, is essential to prevent centralization to a few instances.

Is there a better way to do it inherently in Lemmy itself? Probably, and I am excited to help with that!

It increases load during execution. Afterward it’s not significant. My instance is heavily instrumented and monitored. The load this incurs subscribing to 24000 communities is less than adding a single, moderately active user to your instance.

It’s a huge miss if the intended design was to silo information.

What this provides, as far as I’m concerned, is essential to prevent centralization to a few instances.

Is there a better way to do it inherently in Lemmy itself? Probably, and I am excited to help with that!

It doesn’t matter. Most of the work is happening on the instance, regardless of where the script is running.

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.

It retrieves the last 10 posts and adds the community reference to your local database. It is the same as putting “!community@instance.com” in the search box and clicking search. The retrieval happens whether you look at the results or not.