this post was submitted on 17 Jun 2023
2393 points (96.9% liked)

Lemmy.World Announcements

29034 readers
2 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations ๐Ÿ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 1 year ago
MODERATORS
 

Not that it is not interesting but I would like just a tad more variety on the front page.

Edit btw for those who are wondering the two communities I started are https://lemmy.world/c/newmusic and https://kbin.social/m/musicfeedback/microblog (not sure if I have the links correct for people)

you are viewing a single comment's thread
view the rest of the comments
[โ€“] BananaTrifleViolin@feddit.uk 8 points 1 year ago* (last edited 1 year ago) (1 children)

Part of the problem may be the bugs on the Lemmy instances which have not been showing "hot" content correctly. This may be giving a false impression of an obsession over reddit as posts are stuck on the front page?

I've been browsing a few different communities and am finding things are active, they're just not reaching the default Lemmy front pages. Sorting by new or diving deeper into communities shows a lot of new content.

For example I'm currently browsing from Feddit.uk and this seems to have exploded into an active community in just a week; it's really heartening to seen. I've also seen different content when viewing from Kbin based instances like Kbin.Social or Fedia.io (including from Lemmy.world).

[โ€“] Zetaphor@zemmy.cc 2 points 1 year ago

This bug has been identified and is resolved in the next version release.

The servers that have been keeping hot updated are manually restarting the backend every so often to unstick the bug