Its query planner is also much, much more powerful. Like it’s not even close.

There’s hardly any good reason to use MySQL today. Postgres is easier and nicer to work with, with a strong community backing it.

SQLite is completely different from both and has entirely different usecases.

Postgres, hands down. It’s far better than MySQL in every way.

I’m not, really. They’re one of our largest operating expenses and we’re trying to work on reducing our log output to reduce the cost.

For what they do I’m not aware of any players in the space that come anywhere close, though.

“Lemmy” (the software) doesn’t have any data. It all resides on servers owned by people other than Lemmy’s developers. They have the user data and would absolutely be subject to GDPR.

Again, no matter what Lemmy’s devs put in place, it doesn’t matter because the instance admins can do whatever they want.

GDPR is really designed to target software controlled by a single entity, but this isn’t that. The instances are responsible for their content, full stop. There’s no way of forcing an instance to delete content, and even if there were, since the admins are running it, there’s nothing stopping them from removing such a feature.

There’s also nothing stopping admins from deleting content from their servers (it’s just a database, after all).