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. :)
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.
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.
When I discovered, I felt bad for not checking. As for the load stuff. I intended and wanted to see All the things, and I don't currently have resource problems for my instance. :) We'll see how that fairs as things continue to grow!
I'm happy to help or take PRs for lemmony. There is also https://github.com/Fmstrat/lcs which I didn't know about until well into lemmony.
In Germany they pronounce it VasMan.