Reposting my comment from another thread to spread awareness:

There is a bug in 0.17.4 that stops front pages from updating shortly after the server is restarted, thus resulting in “hot” and "active" showing stale posts.

I have fixed this issue on https://lemm.ee already, you can check our front page to see fresh posts. The fix will soon land in the main Lemmy codebase as well so other instances can take advantage, you can track the issue here: https://github.com/LemmyNet/lemmy/issues/3076

I have also advised other instance admins that regularly restarting their Lemmy server will work as a band-aid workaround until the proper fix is released, so some admins have already implemented this in order to get their post rankings working again, but the proper fix will come in the next release of Lemmy.

There is a bug in 0.17.4 that stops front pages from updating shortly after the server is restarted, thus resulting in “hot” and "active" showing stale posts.

I have fixed this issue on https://lemm.ee already, you can check our front page to see fresh posts. The fix will soon land in the main Lemmy codebase as well so other instances can take advantage, you can track the issue here: https://github.com/LemmyNet/lemmy/issues/3076

I have also advised other instance admins that regularly restarting their Lemmy server will work as a band-aid workaround until the proper fix is released, so some admins have already implemented this in order to get their post rankings working again, but the proper fix will come in the next release of Lemmy.

There is currently a bug in Lemmy 0.17.4 that causes post rank calculation to stop shortly after the server is restarted. It seems like lemmy.world is affected as well.

You can track this bug here: https://github.com/LemmyNet/lemmy/issues/3076

I pinged Ruud about this, he can restart the server for now for the ranks to refresh, but I am also working on investigating and fixing the root cause.

I think voting based on quality of content (and NOT whether you agree with it) is the best approach for healthy discussions. If somebody is a low effort troll, then for sure downvote (and maybe even consider reporting).

OTOH, if somebody makes a well written and thoughtful post about why Totoro is the best Ghibli movie ever, and meanwhile you think Totoro is not even in their top 3, then I would still recommend NOT downvoting 😃

This particular community was removed this morning.

I don't want to go into too many details, but suffice it to say that this is not the first time the responsible users (or, potentially, single user with multiple accounts) has tried to cause disruptions on lemm.ee, so this is why they have been banned from lemm.ee as well.

I know the community is still visible on sh.itjust.works. The reason for this is most likely technical - either the community removal action did not get received properly by that instance, or the fact that one of the mods was a user of that instance has prevented the removal from being acknowledged by sh.itjust.works. Either way, lemm.ee is not hosting this community anymore.

FYI to all admins: with the next release of pict-rs, it should be much easier to detect orphaned images, as the pict-rs database will be moved to postgresql. I am planning to build a hashtable of "in-use" images by iterating through all posts and comments by lemm.ee users (+ avatars and banners of course), and then I will iterate through all images in the pict-rs database, and if they are not in the "in-use" hash table, I will purge them.

Of course, Lemmy can be improved to handle this case better as well!

Nobody knows the future, but speaking as an instance admin, the ideal scenario would be a continued steady growth and not a huge sudden influx 😅

Hey folks! I have spent this morning helping lemmy.world mitigate the issue. I have also sent out mitigation instructions to other admins as well.

For the particular exploit that was used on lemmy.world:

1. It does not spread through federation
2. lemm.ee was not vulnerable in the first place
3. As mentioned above, it has already been mitigated on lemmy.world

So there should not be any reason to defederate. I will continue monitoring and investigating, if further vulnerabilities pop up then I will adjust accordingly.

Interesting! We've had quite a noticeable spike of sign-ups on lemm.ee as well

Thanks for releasing it so quickly!

This "sunaruas" sounds like a cool guy 😛

I really like the overall concept of Lemmy, so I decided to set up lemm.ee to support the Lemmy network with my skillset. I have previously had the privilege of being responsible for running large platforms online (end-to-end, everything from operations to software engineering), and so far, this experience seems to be extremely relevant for running Lemmy in its current state.

As for paying for hosting, my initial plan was to to just pay for everything myself as kind of a hobby, but the userbase at lemm.ee has been very gracious in first asking me several times to share costs, and then actually sending money once I set up donations. I'm not sure yet if this donations-based funding will be sustainable, or if it will fall off after the initial hype dies, but for now it's really awesome to see that there are several other people who believe in lemm.ee and want to share financial responsibility for it.

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.

Wow, tools for putting ads in /r/BuyItForLife must really have corporations salivating

I'm a simple man:

“What day is it?” asked Pooh.

“It’s today,” squeaked Piglet.

“My favorite day,” said Pooh.

Awesome work, big thanks to all who contributed!

Edit: Let's move further discussion here: https://lemm.ee/post/851217

I don't see any Lemmy <-> Threads interoperability happening in the near future anyway. I haven't looked at Threads very much, but from what I can tell, it's mainly going to be a problem for Mastodon rather than Lemmy. Even from a UX standpoint, it does not seem like Threads is really designed to show Lemmy content (and vice versa).

Having said that, Facebook has shown countless times that it's actively harmful to its users as a platform, so there's not much reason to believe that Threads would be any different. If Threads ever becomes interoperable with Lemmy, then I think defederation would be completely justified, unless they can somehow completely change their approach to ads, user tracking and feed algorithms. If that day ever comes, I will make a decision together with the lemm.ee community on how to proceed. But for now, it's not an issue - there is nothing to even defederate yet.

Probably not replace, but certainly it could be a viable and thriving part of the picture. I don't think there's anything wrong with having options.

Well, I'm an Estonian citizen at least 😅

This "ads as posts" thing was one of my two biggest concerns with Threads federation. I really hoped I would turn out to be wrong about it, but at the end of the day, both Facebook itself, as well as big social media influencers, rely on advertising for their profits. For anybody looking to avoid ads on Lemmy, it seems like direct federation with Threads is not a good idea currently. On lemm.ee, "no advertising" has been one of our 4 core instance rules from the start.

My other major concern was Threads having the ability to enforce their feed algorithms on federated instances through sheer number of votes on things they show in their feeds, but judging by what you're saying about the engagement, at least that concern has not materialized (at least yet).