I’ve made some experimental changes, please let me know if you notice any difference
I’ve made some experimental changes, please let me know if you notice any difference
I’ve implemented a workaround for the imgur rate limiting now!
I’ve changed the logic now to no longer proxy imgur images, so their rate limits should no longer affect us!
Thank you, that’s super useful, I will try to investigate what was going on with that request
Hey, I don’t actually see anything abnormal in terms of metrics. What continent are you connecting from (if you don’t mind sharing)?
Do you know around what time it got slow for you?
Hey!
Around June 9th I found that I could no longer display images in comments & posts. The specific problem seemed to stem from some broken code that was being auto-added
This is most likely due to the imgur rate limiter which is blocking our server (Basically our server is trying to request too many images from imgur). I have a plan to bypass our image proxying for a handful of known image-hosts, such as imgur, but haven’t been able to implement this yet. But it’s coming soon!
In general I intend to keep image proxying enabled for most other sites, though, because it allows protecting the privacy of lemm.ee users, as well as ensures slightly faster page load times compared to always making users fetch images directly from their original host.
But sadly, there’s more. Namely, it seems that lemm.ee communities are no longer showing up in one of the significant FV search engines, i.e. “lemmyverse.net.”
This requires fixing on the lemmyverse.net side - they currently only have support for older Lemmy versions, but I believe it’s only a matter of time before this gets fixed.
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!
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
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
Most actions federate, any exceptions which aren’t federated yet are generally just there because the federation logic has not been implemented (but improvements are constantly being worked on).
Generally federating the modlog is mostly just there for informative purposes. As in, we can check what mod actions were taken on instance A through the modlog on instance B (and there is no mechanism in Lemmy for other instances to retroactively remove or hide federated modlog items, btw).
This should be fixed, let me know if you’re still seeing issues!
Hey, this should be fixed now!
I temporarily transferred the community to myself and was able to undelete it. I’ve transferred it back to you now, should be all good.
They are using an allowlist rather than a blocklist, unlike most big instances. We are linked, but we’re not on their allowlist, so the result is still that they block all federation from lemm.ee.
Can you try logging in first at https://next.lemm.ee/login - or are you seeing this while already logged in?
Aha, I think this restore feature is missing from the standard Lemmy UI.
Maybe this will help: I quickly implemented a very basic restore button on lemmy-ui-next. Can you check if you see a “Restore” button in the sidebar at https://next.lemm.ee/c/eurographicnovels? Note that you must be logged in as a moderator to see this button.
I need to step away from my computer for a while, but if this doesn’t work, then I will be able to look into it further during the weekend.
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