Hey, lemm.ee was undergoing maintenance, please try to log in again now.

Sorry, it was a glitch in the Matrix, the comments are actually here: https://lemm.ee/post/45660045?scrollToComments=true

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

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!

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 💀

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.

They are basically local-only communities on lemmy.world at this point, unfortunately. There is no federation to any other instance for any lemmy.world user posts on those communities.

You haven’t been doing anything wrong from your side - we have just been experiencing some growing pains with a new Lemmy feature (image proxying).

It’s a bit unfortunate that these problems cropped up, but ultimately we will benefit from this new feature, as it will help solve several issues with Lemmy image hosting overall. So I hope you can forgive the issues and trust that the end result is worth it!

Ahh I see the issue & have fixed that example post now.

Basically, I had already fixed the root cause which was breaking the images, but there was a period while I was working on the fix during which some images posted would remain in a broken state. I don’t unfortunately have a fast way of automatically detecting and fixing those broken images unfortunately, but I can fix them one by one manually.

Having said that, any new images posted now are not getting broken. I’ll see what I can do about the broken ones, maybe I can find some way to automate fixing them.

Hey, I’m not seeing any issues at the moment, can you share more details about what is broken for you currently?

I’ve made a few PRs to hopefully improve the image situation, these are all running on lemm.ee as of now as well, so hopefully it’s better now!

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

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

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

The maximum file size limit for images hosted directly on lemm.ee servers is always visible in the sidebar of our front page. The limit stands at 500kb per image currently.

Additionally, It’s also possible to post images larger than 500kb, they just have to be hosted externally. The markdown for this is ![alt text](image url)

I’ve made some experimental changes, please let me know if you notice any difference