For a mini PCs, K3s or even Nomad (not really Kubernetes), would probably be better solutions. Should be easier to manage in a lab too.

Really looking forward to SSO support!

… 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”.

Yes, I am significantly more active here than I was on Reddit (at least recently, my decline on posting/commenting on Reddit started a few years ago).

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.

I’m using Kubernetes, not docker compose, so this doesn’t exactly apply to my implementation.

My problem with email was a transient issue in resolving “smtp.sendgrid.net” inside my Kubernetes cluster.

I think setting up a relay would resolve the issue for me, but I’m not sure.

Saying that, I thought I had resolved the issue, but I didn’t get an email notification for your reply. I don’t think my SMTP issues are fixed lol.

Awesome, that’s super helpful, thank you!

I guess I’ll also look into an SMTP relay. That could be useful I guess.

What’s the sql query you are using? And which table do you remove them from? (Looks to me they show up in multiple tables)

I feel like that doesn’t really resolve the issue at all… it is merely a workaround.

On top of this, would manually deleting the user from the database be a good idea? I’m assuming not.

Right, is that starting at like 12 EST or PST?

Ah, that’s based off the AMA he “did”. So nothing newer than that?

The CEO just tripled down and said they are not changing their intended API pricing regardless of how many subs and users go dark.

Link? That’s not good news :/

Did he get caught editing comments again? And the shadowbanning?

I don’t think I’ll go back except for niche content/communities I don’t expect to see here for a while.

Pretty much! There isn’t currently a way to migrate accounts though, so keep that in mind.

Might not be a feature you need now, but it is a nice-to-have from Mastodon that I’d like to see available everywhere.