I made this tool to help self-hosters, new admins, or smaller instances have more global and updated content on their instances.
This is the similar to Lemmy Community Seeder but is designed to be run periodically to capture new communities, and include EVERYTHING by default.
EDIT: As noted in the comments, this is an admin tool. Please do not run it as a user if you don’t know what you are doing. If you want a better “All,” ask your admin first! That said, lemmony in no way constitutes abuse! You can cause a DOS with curl, but that’s not what curl was written for. This tool is to legitimately use an API to enhance our experience. Admins that desire to accommodate high volume on a public service will not know this tool is running against, or on their instances. If it causes performance issues, that is unfortunate. They are free to throttle, ban or block API access to their instance in a multitude of ways.
EDIT 2: Donate to your instance/admin if you like Lemmy!
I did something similar. When I federated around 700 active communities the instance used around 3GB per day. That’s too much. Include EVERYTHING?
I’ll call the coast guard because you all will be drowning lol
Quite a bit of space could be saved with database compression. The database side of things has lower hanging fruit right now though.
Really? Like a lot? I thought the biggest space hog was images by far.
Images are not federated, they only live on the hosting instance.
Thumbnails might copied though, I’m not sure.
Does the image get stores on the poster’s instance or the instance hosting the community they’re posting to?
The poster’s.
Hmm. Could you help me debug https://nrsk.no/post/160040, since the image from post https://lemmy.dbzer0.com/post/481984 is hosted at https://nrsk.no/pictrs/image/e899afcc-83fa-481e-b9d4-f5e0e693c1e3.jpeg?
I would initially think the image was federated as per the system design but you obviously know more about how my instance works than I do.
Any tips will greatly appreciated, I also suggest you make a github report since this is a bug every lemmy instance seems to struggle with.
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.
If the lead developers discusses this not as a bug but an inconvenience then there’s nothing I can ever say or show you to ever convince you otherwise.
Enjoy your non-proxying Lemmy experience - Since your pict-rs directory is growing but not due to your instance caching images it’s probably the docker log bug that was discussed over a year ago.
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
EVERYTHING by default. Also working on “discover only” for searching without the subscribe-to-everything. That said: It’s far less than 3GB per day for EVERYTHING I can see, plus: you don’t HAVE to keep it forever. Were you doing something that got other than text?
Do you have a link to a documentation concerning retention/cleanup for instances?
I don’t. I haven’t looked yet either because I haven’t crossed that bridge. I think there were some admins on matrix chatting about it though. It will become an issue for large instances like near term, so I suspect someone will tackle it very soon, if they haven’t already.
Images federate, friend. There’s a lot of cat pics on the lemmyverse.
They’re not supposed to, and don’t call me friend, buddy.