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
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, this post is quite old, actually you can find the latest info in the sidebar of our front page:
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:
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).
It’s the first option in the dropdown:
Big thanks to all maintainers and contributors!
While there isn’t any built-in ban appeal in Lemmy, there are still a few ways to reach lemm.ee admins even after a full ban: creating a new account (as you did), contacting me on Matrix (I am @sunaurus:matrix.org), or contacting the admins on Discord (there is an invite to the lemm.ee Discord in the sidebar of this community).
Well, one advantage we have over commercial social media is that they need to pay people to write code and maintain the infrastructure, but a lot of work on Lemmy is volunteer-based.
Many admins for bigger instances are basically on-call the whole year for free, open source contributors provide code for free, etc. Even the core maintainers are effectively losing money by working on Lemmy, because while they are getting some income, the sum of money they are getting from working on Lemmy is way smaller than what they would get if they worked typical software engineering jobs.
Basically, if any non-volunteer organization wanted to replicate Lemmy, it would cost them quite a bit more in terms of payroll alone.
Another aspect is scale - Lemmy is able to spread the costs between different instances, and while growth of the network can generally increase costs for individual nodes, they will still end up paying less compared to if they were hosting the entire social network in a centralized way.
We have about 3.3k monthly active users. This is based on users who at least vote/comment/post once a month, so it doesn’t include lurkers. But yeah, in terms of just infrastructure costs, we’re at about 6 cents per active user per month.
We’ve been stable just around 200€ per month for most of this year (it fluctuates up and down a little bit depending on exact usage). I update https://status.lemm.ee once every month with expected running costs for that month, and while it hasn’t changed much in the past months, if it does ever change, you’ll find up to date info there!
Hey, lemm.ee admin here - it’s actually hosted in Finland!