It's occasionally breaking for us due to imgur rate limiting the lemm.ee server. I am planning to disable proxying for a few well known image hosting sites (including imgur) soon - it requires some additional development, but I think I'll be able to do it in the next few days. Sorry for the inconvenience!
sunaurus
joined 2 years ago
Hey, this post is quite old, actually you can find the latest info in the sidebar of our front page:
- Image uploads are enabled 4 weeks after account creation
- Image upload limit is 500kb per image
Hey! Thanks for the report.
I think the first issue is not something I can help with - probably the Connect app needs to fix something on their side.
For the second issue, see my comment here: https://lemm.ee/post/34118135/12479638
It's a full new game that you need to purchase separately, but all the marketplace stuff you've bought for 2020 will also come with you to 2024
We finally have a release date for Microsoft Flight Simulator 2024!
I have identified two reasons for broken thumbnails right now:
- For some, the source website is simply not allowing our server to download the image (mostly due to server issues on the remote side)
- For others, it seems that some types of URLs are breaking thumbnail generation. I think I found the bug here and will try to submit a fix soon.
That's definitely not intentional - it's a custom error message which we have just for lemm.ee, not a standard Lemmy error, and it seems I need to tweak it a bit for it to work correctly in 0.19.4. Thanks for reporting this!
Yes, lemm.ee has all the standard Lemmy features. However, the format for this request has changed, and it seems the app has not been updated yet.
For technical context: your app is trying to use the singular post_id field when marking posts as read. This field was marked as deprecated several releases ago, as it was replaced by a post_ids array field, in order to enable marking multiple posts as read at the same time. The deprecated post_id field has been removed in Lemmy 0.19.4.
Regarding your question:
Lemmy federation basically works by copying stuff from their source instance to all other federated instances. So if I write a comment on lemm.ee, other federated instances will get their own copy of my comment. They will also all know that the "authority" for this comment is lemm.ee.
If an admin on another instance decides to delete their local copy of my comment on lemm.ee, then they are always free to do so (for example, some instances might want to moderate more strictly), but any actions they take like this are limited to their own instance - for the rest of Lemmy, lemm.ee remains the authority for this comment, so individual remote instance admins taking actions won't have any effect on any other instances.
As for the original topic of modlog federation, basically it just boils down to this: just like with the comment example above, Lemmy instances also save a local copy of incoming federated mod logs. The Lemmy software does not yet have 100% coverage in terms of federating mod logs (for example, there are no federated logs yet for instance admins banning remote users), but this coverage has been increasing, and I expect this will eventually get to 100% (just needs more dev time really).
Also, if some instance admins try to tamper with their mod logs, then other instances can still see the real history, because there is no way for an instance admin to delete copies of their mod log from other instances.
Banning a local user from a local community does actually federate already
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