It was the result of a DoS attack yesterday, should be mitigated & recovering now.
Hi, there is no free speech policy on lemm.ee, we have very strict moderation when it comes to our rules. We regularly permaban users for breaking our instance rules. We simply don’t use defederation as a moderation tool, preferring other tools like user bans, for reasons outlined here: https://lemm.ee/post/35472386
Our pict-rs (image software) was having some issues, but it should be resolved now!
Can you try clearing all your cookies & then logging in again? I’m not sure if clearing the cache also clears cookies in Firefox.
Hey, I saw this ping, but I didn’t actually get any message from you about CORS headers. Where did you contact me?
Interesting! We’ve had quite a noticeable spike of sign-ups on lemm.ee as well
Hey, the 20 character limit for display names is hardcoded into Lemmy. Even if we changed this for lemm.ee, it would not work through federation, as other instances would not accept such a long display name.
There isn’t any way to do this with the default lemmy-ui unfortunately
Usually, this is caused by external servers blocking the lemm.ee server from downloading images. This is happening surprisingly regularly, I’m not sure if there’s a good fix for this…
The YouTube thing does indeed appear to be a bug, I will look into that separately. Thanks for reporting!
Generally it is indeed possible to take over communities with inactive moderation, but have you tried contacting the mod first?
@[email protected], are you still around?
We had a temporary issue with generating different formats/sizes for existing images. I believe the issue is now fixed, our server is going through a backlog of missing files currently and regenerating them. I believe all broken images will be fixed within the next few hours.
Sorry for the inconvenience!
We had a temporary issue with generating different formats/sizes for existing images. I believe the issue is now fixed, our server is going through a backlog of missing files currently and regenerating them. I believe all broken images will be fixed within the next few hours.
Sorry for the inconvenience!
For now, I just redeployed all of our servers completely, but as I don’t know the actual root cause of the issue yet, I’m still investigating to figure out if anything more is needed.
Sorry for the delay in updating the status page - I actually had gone out for lunch just a few minutes before the downtime started, so I didn’t even realize anything was up until I was back at my computer about 45 minutes later 💀
Actually, we’re using Hetzner’s cloud load balancer for lemm.ee. But if this issue repeats in the near future, then I will definitely consider setting up something else.
There are two useful sections on https://status.lemm.ee for this - firstly, there is an automated check for federation with all other instances on the bottom of the page, and everything there being red is a definite sign that something is wrong with lemm.ee itself. Secondly, near the top of that page, I will always write a status message manually when I discover & start work on any issues. This second part can have a bit of a delay, as it requires manual input from myself, but I have updated it every time we had any issues so far.
I believe I discovered and fixed one cause for intermittent slow page loads, but please let me know if you notice it again in the near future
I use SwiftKey and I hate it, but I haven’t found anything better
I’m in exactly the same boat. 😅
I don’t understand how it has been broken for years. I wonder if none of the engineers working on it actually use it themselves? Deleting all of your local data makes it stop crashing for a few weeks, but then you of course also lose all the learned predictions, and eventually it just gets to a point where it just crashes more and more often and you have to delete all the local data again. It sucks.
If only the default Apple keyboard had support for my language, I would ditch SwiftKey forever.
I think it’s not really on your side, most likely either just something wrong on kbin.social itself, OR a side-effect of the measures lemmy.world implemented against kbin.social recently.
Sorry, it was a glitch in the Matrix, the comments are actually here: https://lemm.ee/post/45660045?scrollToComments=true