Our servers are all hosted in Finland indeed, but we use Cloudflare for DDoS protection etc. Clients/bots/scripts/etc (like FediDB) don’t see our server IP addresses directly, they see Cloudflare IP addresses. FediDB uses the IP address it sees to assume what country the server is in.

The same is true for a bunch of other Lemmy servers as well - a lot of the ones FediDB shows as “United States” are actually hosted in Europe (or elsewhere).

Most applications are handled automatically, a smaller percentage is sent to manual approval for admins. This is based on different signals and the aim is to potentially reduce some abuse, or at least make it a bit harder.

Median time for accepting applications in the past month on lemm.ee was 1 minute and 42 seconds. And that includes the time it took for users to manually verify their e-mails first.

What I mean is that some posters have a bunch of alts on different instances, and if they get awards split between their accounts, then they’ll be at a bit of a disadvantage 😄

This is cool!

Any rules for alts? Can people “claim” alt accounts to sum up their votes?

It’s very unlikely lemm.ee will ever be a suitable host for video content. Please host your videos on other platforms, embedding them on lemm.ee posts will work just fine.

Whenever you give your free time and energy to build something open source for the world, there are always some people who say “why aren’t you giving me 10x more, you lazy dev” 😅

Could I ask you to try again with the app and let me know if it’s working for you now?

Hey, sorry for the issues, please see my comment here for explanation: https://lemm.ee/post/57870550/18964440

Hey, sorry for the issues, please see my comment here for explanation: https://lemm.ee/post/57870550/18964440

Hey, for the past few weeks, we have been tuning different rate limits and other bot prevention mechanisms on lemm.ee. We have had a huge increase in traffic lately, as well as a couple of instances of what was effectively a DDoS.

In other words, the problems likely have nothing to do with your app or different versions, and everything to do with our own measures.

For the mark post as read endpoint, I recently made the rate limit a bit more relaxed, so hopefully users won’t see issues there anymore. OTOH, we are also presenting a Cloudflare challenge for some IP ranges currently, which may inadvertently affect legit users. This was necessary to mitigate a recent DDoS, but we will continue tuning and hopefully restore things to normal for legit users soon.

Definitely not 😄

In my experience, it’s mostly a combination of confusing Lemmy UI + user error:

1. When using the e-mail verification link, Lemmy just shows a blank page with a tiny “e-mail verified” notification in the bottom left corner, which people miss. They then assume that it didn’t work, because all they see is a blank page.
2. When opening the e-mail verification link multiple times, only the first time registers, and further attempts will generate confusing errors. This also makes people assume it didn’t work, but in reality, their e-mail got verified successfully.
3. On lemm.ee, it’s very common for people to sign up with typos in their e-mail addresses (happens few times every week recently).
4. We have a custom question on our sign-up page asking people to state they agree to our rules, and it’s relatively common that people just don’t read the question and write something random in there - we generally don’t accept such applications to try and weed out bots, but I’m pretty sure we also end up rejecting a bunch of legit users this way who just didn’t read the instructions.

Generally I’m happy to provide support to people in such cases if they reach out to me directly, but at the end of the day, the easiest and fastest solution if the account is truly stuck in limbo is just to create another account.

It’s a shame that there is so much potential friction on sign-up, but at the same time, I don’t see us reducing the friction on lemm.ee any time soon, because this is the lesser evil compared to bot sign-ups etc that we have seen in the past.

Hey, there isn’t any default community right now. There are a few different databases that track graphs of such things, for example, fedidb.org.

Thank you very much for the support!

Our infrastructure costs are currently quite stable at around 200€ per month, and considering that the instance is right now quite decently supporting nearly 6000 monthly active users, you could say that you are indeed relatively contributing a ton - you are effectively covering server costs for 60 people!

The fact that it’s a monthly amount is particularly great, because with recurring income, we will get advanced warning if there is danger of funds starting to run low.

We had a few really huge days in 2023, but other than those, it seems like the growth so far in March is definitely outpacing our initial wave of new users in 2023.

The e-mail successfully went out from our side - please check your spam filters etc

It’s the correct error code (the client is sending a bad request - it’s an already used token), the problem is just that Lemmy UI doesn’t really display a useful error page to the user.

That’s just Lemmy behavior for when you click the e-mail verification link multiple times. It basically means “e-mail already verified”.

Can you share the exact error you are getting as well?

It seems to go through for me:

Could you upload an example image which does not work somewhere else and share it with me so I can try to reproduce the issue?