Currently using Nextcloud AIO and it’s pretty decent, though I’ve got 16 vCPU and 32 GB of RAM allocated to it right now, though it’s only using 10% CPU and ~7 GB of RAM at the moment.

I think it takes a while to warm up once you start adding data to it, especially depending on the plug-ins you add and amount of data.

I should look into how to do that on my instance probably. Pictrs always seemed like a bit of a security nightmare.

I disabled Pictrs around the time of CSAM attacks and have yet to bother enabling it again

Uhh… what?? When did that happen? I thought pictrs was a requirement also…

Huh, do you have your lemmy config documented somewhere? I keep running into issues with it and I’m not sure which component exactly is failing, but it’s annoying. I’m using this helm chart currently: ananace/lemmy It works, but I don’t have pict-rs setup in HA either.

They store the secrets in a file? Gross. What a poor way of handling that. Pretty sure environment variables would be more secure. Especially in Kubernetes.

Yeah, I used to host a Matrix instance - could do that for this one too.

The issue is more about setting up the Kubernetes manifests and templating them. I usually use the chart’s built-in postgres and redis config, though using an operator would make it more scalable for sure.

I’m using Authentik for auth, but I do also like Keycloak.

I’ve seen that around, but I prefer to run my own services instead of relying on a ready-built system like that. I find they don’t offer that much customization options usually.

I think both of the ones I mentioned have docker-compose files, which I think I can convert with kompose convert? I guess from there I would follow your steps and then start parameterizing it once it’s running properly.

Thanks! I think I’ll start trying out PixelFed tomorrow.

That’s actually super helpful! I haven’t done much custom Helm chart-ing, and was kinda lost where to start. That really helps break the process down, and the tip about skipping state to start is very wise.

Yeah, that’s the pain point - building and maintaining the charts.

Also, I know the charts likely wouldn’t have to be super complex, but I’m used to working with Bitnami’s charts that are massively complex - I just don’t have the time to go that in-depth.

Oh, I know I could get them to run with enough work. I just don’t have that much time to spend on initial implementation and upkeep of the charts.

I’m using FluxCD, which I believe can do deployments of plain Kubernetes manifests, but that still requires a decent amount of overhead to keep up to date.

Just because it’s not public facing doesn’t mean that it’s not an issue. It might be less of an issue, but it is still a massive vulnerability.

All it takes is one misconfiguration or other vulnerable system to use this as a jumping off point to burrow into other systems. Especially if this system has elevated access to sensitive locations within your network.

🤮

… how the hell have I never heard of this?

I don’t think it’s worth the devs’ time to implement e2ee for DMs, there are lot of other things that need to be fixed first. Not only that, but if it’s implemented in Lemmy, it’d make Lemmy non-interoperable to DM users from other federated platforms such as Mastodon or KBin. Which, I’m not sure works right now, but in theory would be possible.

Also, yes, that is generally the case.

I highly doubt it will, there are many much better solutions available, and as it says when DM’ing someone, you can you Matrix for e2ee. In fact, there is even an option in the profile settings to provide your Matrix username.

Implanting e2ee within DMs is massive scope creep and also really difficult to do properly.

The general rule is basically “never implement your own encryption/security, just use what’s already been implemented by people who actually know encryption/security”.

I’m on Kubernetes, but it’d be the same via Docker - a volume mount (iirc at the same place it stores local data if you don’t use S3, should be in the docs)

My instance has a couple users currently lol

You’d have to talk to the your instance admin, they should be able to go into the database and fix your account.

I changed Kubernetes’ coredns config to forward *.sendgrid.net to 1.1.1.1 rather than my internal Pi-Hole servers, which did seem to help a bit.

Haven’t tried since updating to 0.18.0, so it could be an internal issue as well.