You can use pg_stat_statements to find slow queries. Try sorting by top total_exec_time.

Good example of AI making stuff up instead of simply saying “I don’t know”.

The key is refreshed after 24 hours so it will work if you wait a bit.

There were optimizations related to database triggers, these are probably responsible for the speedup.

https://github.com/LemmyNet/lemmy/pull/4696

True there are a lot of issues related to notifications. I will see what I can do.

Here is the relevant issue, but no one is working on it currently.

We didnt make any changes to the Lemmy version running on this instance during the past week. So it must be something else…

The problem is that a server could very easily lie and claim to have captchas when it really doesnt.

Someone on in the Matrix chat tried this and didnt have any problems.

I see now, if an instance has any site languages configured those will be applied for new users. You can see it in /api/v3/site field discussion_languages. However both lemmy.world and lemm.ee return all languages there.

Edit: Im removing this as part of the PR to set new user languages from accept-language header, it doesnt make sense anymore with that.

Yes contributions to improve this interface would definitely be welcome.

Right my_user.discussion_languages is the correct one. And it being empty means that all languages are enabled (to avoid storing lots of unnecessary db rows). Im testing with a new account on ds9.lemmy.ml and can see posts marked as English without any problems.

I cant really how such a problem could happen and only affect those specific instances. Can you check through the api which languages are enabled on a new account? The info is under /api/v3/site in the field discussion_languages, it should contain numbers from 0-183 which are all the language ids.

I confirmed this just now, when registering a new account all discussion languages are enabled. However this isnt properly indicated in the lemmy-ui user settings.

When you signup, all languages are enabled by default. I believe it was like this since the feature was first implemented. I recently made a pull request so that languages are automatically configured from accept-language header.

This is strange because neither of the communities you mentioned has any language restrictions. Can you say what error is being returned exactly? You might have to use browser dev tools to see the details.

I noticed this bug a few weeks ago and fixed it. This will be included in the next release.

Yet it’s still noticeable that people from the US are way overrepresented compared to all other countries.

Invalidated how?

Well it’s deleted from the database so you can’t authenticate with it anymore.

Hold on the scammer could spend 8000 usd without even knowing the card’s PIN number?