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.
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.
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)
To be honest, neither Hexbear nor Lemmygrad has caused any noticable issues for lemm.ee. I recently compiled some stats for lemm.ee rule breakers by home instance, and as you can see in this post (in the “Administration” section), neither of those instances even made the top 10.
In general, mods haven’t complained about those two instances either, and the stats for community bans by independent community mods are more or less very similar. If any users creates issues in a lemm.ee community, then the community mods are free to just ban those users, regardless of what instance their account is hosted on.
if fact I wouldn’t even be able to as my home instance is defederated from these instances and thus such posts would be invisible to me
Preventing such situations for lemm.ee mods is actually one of the many reasons we don’t want to use defederation as a moderation tool on lemm.ee - we rather use site bans etc. Too much collateral damage with defederation, especially when dealing with larger instances which probably have vastly more innocent users than problematic ones. We reserve defederation for more extreme cases, like spam instances & CSAM.
Hey, lemm.ee admin here - it’s actually hosted in Finland!
It’s not really a bug, it’s just a case where app developers need to update their code to support a small change in the Lemmy API. More details here: https://lemm.ee/post/34259050/12479585
By the way, as a mini-present, I have sneakily updated our Lemmy to 0.19.4! It was possible to do this one without any downtime, so I just did it quietly in the background.
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.