Its okay, everyone is wrong about some things.

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

The users who voted all look legit, I also didnt notice any accounts upvoting multiple posts from this user.

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.

It was always normalized, but recently there seems to be more backlash from maintainers.

I dont have time to read all that. The problem with Beehaw is that the admins are extremely entitled, as if we had some obligation to work for them for free. Similar to what is described in OP.

However we are consistently improving the mod tools, and accept contributions in that area. You can see in the dev updates.

What is this “stance on mod features” that you are talking about?

We only do major versions around once a year so those could still be named, while using numbers for minor versions. Lemmy is more user-facing than react, so it would make sense to have a more user-friendly versioning.

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

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.

The automatic language tag should only depend on the community language settings and user language settings. Specifically it will build the intersection of both, and if the result only contains one item (excluding “undetermined”), that is used as the post language. The instance doesnt matter at all. And there havent been any changes in this area in a while, so there should be no difference between 0.19.x versions.

I thought maybe the community language isnt federated properly but its identical on all mentioned instances. Also @Camus@sh.itjust.works mentioned that French is enabled in user settings. There is clearly a bug but I cant think what else might be causing it.

Anyway please report such bugs directly on the issue tracker, otherwise I might not find out about it at all.

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.

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