Could I ask you to try again with the app and let me know if it’s working for you now?
Hey folks! I’m responsible for servers at lemm.ee.
For general lemm.ee policy/admin/moderation topics, please contact @EllaSpiggins@lemm.ee
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 😄
We have automated a lot of this stuff on lemm.ee as well
I’m afraid .world users will also miss out on your mod actions in all of your communities, which is a particularly unfortunate side-effect.
I don’t think it’s the end of the world (:P), though - .world is a big instance, but there are still tons of users on other instances. I mean, even in your communities, I don’t think .world is not making up the majority of activity.
I’m not sure why .world has the 18 age requirement - AFAIK GDPR only requires 16+ if you don’t specifically ask for parental consent. Of course, there is the matter of pornography etc, but for example Reddit allows 13+ users, and all they do for pornography is show an NSFW warning, which Lemmy also has (although this is a good point - maybe the NSFW toggle should be improved to explicitly ask users to confirm their age on Lemmy as well, similarly to how it works on Reddit).
But at the end of the day, each instance is free to create whatever rules and processes they want, and to ban people according to those rules. I would say that .world admins are probably just trying to do their best in enforcing their rules, and unfortunately that means that most likely you’ll be cut off from .world for the next 5 months 🫤
In my experience, it’s mostly a combination of confusing Lemmy UI + user error:
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.
I’ve just restored it
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.
Hey, could you make a post in that community?
Lemmy software resolves it automatically - it marks such instances as dead and stops sending activities to them.
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:
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” 😅