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.
I'm not convinced either one of us knows what the software is SUPPOSED to do, and I am pretty sure nobody knows what it's actually doing. Here's another thread: https://github.com/LemmyNet/lemmy/issues/3163
There is some discussion. https://github.com/LemmyNet/lemmy/issues/2947
I am still fairly confident that it shouldn't be storing images, but I'll admit my pict-rs directory is growing quite fast compared to the database. Have to keep a close eye on this.
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 "[email protected]" in the search box and clicking search. The retrieval happens whether you look at the results or not.
A handy chart: https://i.pinimg.com/originals/18/a4/2f/18a42ffa5c733c7c6bb86b547fb0647f.png
It's a cruel irony that we use an enclosure to help print materials with a higher Tg but the printer itself is printed of materials with the same or lower Tg. It makes perfect sense that your ABS parts are going to get mushy when you crank your heated bed to 100 and put the whole thing in a box. :)