Now that's definitely strange, but thanks!

Same issue, but I run my own instance. The password is 1,000% correct, not sure what's wrong.

It looks like the issue I was referring to has since been edited, as it's not actually relevant to clearing this database bloat:

https://github.com/LemmyNet/lemmy/issues/3103

Pictrs 0.4 recently added support for object storage. This is fantastic, because object storage is dirt cheap compared to traditional block storage (like a VM filesystem). This helps a lot for image storage, which is a large part of the problem, but it's not the whole problem.

I know Lemmy uses Postgres for everything else, but they should really invest time into moving towards something more sustainable for long term/permanent hosting. Paid Postgres services are obscenely upcharged and prohibitively expensive, so that's not an option.

I'm armchair architecting here so I'm not sure what that would look like for Lemmy (Cloudflare KV? Redis?)

Still, even my own private instance has been growing at a rate of about 700MB per day, and I don't even subscribe to that many things. I can't imagine what the major instances are dealing with. This isn't sustainable unless we want to start purging old data, which will kill Lemmy long term.

EDIT: Turns out ~90% of my Lemmy data is just for debugging and not needed:

https://github.com/LemmyNet/lemmy/issues/3103#issuecomment-1631643416

I plan to support this for as long as I'm using Lemmy, which should be a good while.

All the script really does is generate a docker-compose.yml stack that's best for your desired setup. So even if I do stop supporting the script, you're not locked into using it. You can always manage the Docker Compose stack manually and do your own updates, which is what people not using my script will have to do anyway.

Also, I don't bake Lemmy versions directly into this script, I just pull the latest Lemmy version from GitHub and deploy that. So in theory, unless the Lemmy team changes something major, this should continue working for a long time after I stop supporting it.

If you want to be prepared, I would recommend reading up on Docker Compose and getting familiar with it!

And that is why I don't advertise this as supporting email out of the box, and why it's an advanced option without any support from me. The embedded postfix server is part of the official Docker Compose deployment from upstream Lemmy, and it's part of the officially supported Ansible deployment too. Those deployment methods are what this is modeled after. That is as far as I go on email support. If upstream Lemmy started including some automatic AWS SNS configuration, I would adopt it, but they have not done so.

Everyone who has reported success to me so far are running single user instances for themselves. That is my target audience, and for that audience (and myself), email is not even close to being a hard requirement.

However, if you would like to improve this script by adding support for more robust and secure email systems, I would be happy if you submitted a PR to do just that :)

Thanks! Fix pushed.

Thank you very much for the kind words!

Please be my guest! It would make me happy to know this was helping people join Lemmy!

What version of Android are you on? Android 12 or below? It was removed entirely in Android 13. It can be "patched back in" on a custom ROM, but doing so breaks the recents screen due to incompatible changes made to the system launcher (which handles the recents screen for... some reason).

Or maybe you have a Samsung or other phone that has their own 2 button implementation. But as far as I'm aware, it's gone from AOSP as of Android 13 :(

• I can build my own ROM and add any tweaks I want to the source
• Full filesystem access, not the circus act iOS is running with their "file management"
• I can run any browser I want, download any file I want
• I can sideload any app I want, and install open source apps from F-Droid
• I can use projects like ReVanced to install modified apps effortlessly, and don't have to go through the AltStore/Apple Developer BS to install simple things like uYou
• I can entirely replace my home screen with a different launcher app if I wanted to

How is it ephemeral? My Docker instance for Lemmy logs forever unless I manually clear the logs. My Caddy reverse proxy logs every request too. Both are stored to disk and I'm free to copy them out at any time. They'll keep increasing in size until I decide to clear them.

They're logged through the Docker engine, not the container. A malicious actor would require a sophisticated container breakout attack to even attempt to clear them. Those attacks are rare and highly publicized.

Alternatively, an attacker could try to find my real instance IP from behind Cloudflare (probably not going to happen), somehow bypass my provider's firewall which only allows SSH from my home IP (my home is more likely to be broken into than that), and then somehow defeat SSH authentication on top of both of those (quantum computers aren't quite there yet).

I'm having trouble seeing the risk you're concerned about.

It's likely the Docker images, and maybe the Docker build cache if they built from source instead of using the Docker Hub image.

I've been up for about a day longer than OP, and my Lemmy data is still under 800MB. OP either included non Lemmy data in that math, or is subscribed to way more communities than me. My storage usage has been growing much faster today with all the extra activity, but I won't have to worry about storage space for about a month even at this rate.

And that's assuming Lemmy doesn't automatically prune old data. I'm not sure if it does or not. But if it doesn't, I imagine I'll see posts in about 2-3 weeks talking about Lemmy's storage needs and how to manage it as an instance admin.

EDIT: Turns out ~90% of my Lemmy data is just for debugging and not needed:

https://github.com/LemmyNet/lemmy/issues/3103#issuecomment-1631643416