this post was submitted on 23 Sep 2024
27 points (96.6% liked)

Fedigrow

597 readers
12 users here now

To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks

founded 6 months ago
MODERATORS
 

Hello everyone,

If you look at https://fedidb.org/software/lemmy?version=0.19.3, you see a few instances that host alternatives to LW communities

Lemmy 0.19.5, has been released on 19 June, we are now three months later.

I've been reaching out to a few of them

Now, important disclaimer

I am personally very thankful for those admins to manage those instances. I have been posting to those communities a lot to try to better decentralization,, and it's very generous of them to give their time, energy and infrastructure to run those instances.

On the other hand, having such long times between updates releases and the instance actually updating concerns me a bit, because it seems to show that those instances are relying on one single admin which could disappear overnight, and might also have trouble with reacting in case of incident.

I guess the opposite view is that it doesn't matter so much, they'll update when they update, and they probably don't prioritize those updates as much compared to an actual incident (which we saw back in the days with the federation issues between LW and Australia / New Zealand servers).

For people curious about LW (still running 0.19.3 as well), they told me they wanted to skip 0.19.5 due to this one issue https://github.com/LemmyNet/lemmy-ui/pull/2629 which if fixed in 0.19.6. It makes sense due the high number of mods they sometimes have per community).

That's it for me, curious to hear what you all think.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 4 points 1 month ago (1 children)

fwiw, for Sync users the update to 0.19.5 is not that great, as @[email protected] still hasn't updated Sync to use the updated APIs for marking posts as read :(

[โ€“] [email protected] 2 points 1 month ago

There seems to be a similar issue on Voyager, which people experience on both 0.19.3 and 0.19.5: https://lemmy.world/post/20046439