1087
Recent Outages
(lemmy.world)
This Community is intended for posts about the Lemmy.world server by the admins.
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Any support requests are best sent to info@lemmy.world e-mail.
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Whenever I get frustrated by the outages I remind myself: still better than reddit.
It's your fault for not pitching in and making lemmy more stable. There, happy, you've been blamed :P
What is the burden if I wanted to host a node and limit access just to myself? Is it just a portal into the rest of the fediverse or is there a large maintenance burden or storage requirement?
Yeah, pretty big storage requirement due to the way pictrs works. Pictrs is the piece of software Lemmy relies upon to manage image storage, uploads, and most importantly: caches pictures from other instances. This takes up a HUGE amount of storage space, and there's no official way to clear this up, see these posts I recently made: first one, second one. The solution I resorted to is renting a 1TB storage box from Hetzner for 3 euros per month, pretty sweet deal but I was kinda annoying by it. So the cheapest deal I could find costs me 6 euros per month: 3 for an Alma Linux ARM VPS from Hetzner, and 3 for that storage box. If you're in for the fun in tinkering (I sure as hell am in), then get ready for a good time. Other than that, if your main line of reasoning is to take burden off of lemmy.world, then I think just go ahead and join another instance. Better yet: join croud funding of another instnace:)
I don't think this is correct, the images from one instance are hosted on that instance, they don't get copied over. What's federated and copied over is text and references to those images (like this
![](https://image.url/image.filename)
). The only images that are hosted on your own Lemmy instance are the ones that you and your users upload, which sure if you have open sign ups and a bunch of people using your instance uploading images then it will become a problem very quickly, but for personal use it shouldn't unless you're uploading a lot of images or even videos.Just use external image hosts for posts and comments, and only use image uploads for your own profile and banner and everything should be fine (if you want extra assurance you can disable uploads in case you forget).
Nah I thought the same but then I manually checked it. In most of the image posts I see, the image URL starts with lemmy.org.il, which made me wonder whether they're actually downloaded or it's some kind of whacky proxy. So I downloaded some of these pics and looked for files of identical size and hash digest, and indeed they were on my disk!
It's not a bad decision to cache pics, because it does make the experience really smooth, and I'm not complaining about it. Mastodon does this as well
Weird because I've checked it before and it doesn't seem to, one notable example is that on the lemmy.zip communities I can't see any of the images at all because something on my network or with my ISP blocks zip domains. The posts, comments and all their text gets copied over to lemmy.world but the images don't seem to and thus they don't display for me due to their domains being blocked.
(Alternate DNS doesn't seem to bypass whatever they're doing to block it, I can only connect to .zip domains through Tor or VPN).
I agree it's definitely a good idea to create a more smooth user experience, would also eliminate the problems that I pointed out with the images not loading due to their domain being blocked.