- cross-posted to:
- fediverse@lemmy.world
- fediverse@lemmy.world
- cross-posted to:
- fediverse@lemmy.world
- fediverse@lemmy.world
I’m surprised that there are still instances out there running 0.18.2-rc2 or 0.17.0. Those versions are full of bugs and miss so many features.
I scrolled to the bottom, saw there was 1 instance still running 0.16.6 lol, I clicked on it and saw it’s actually still active, there are recent posts there. Amazing.
Edit: all from 1 user lol no upvotes, might even be a bot.
Some of the larger instances have updated already. It’s beautiful to see.
0.19.5 has passed 0.19.4 now, with 86 vs 85
I’m surprised 0.18.4 has more instances than 0.18.5, considering 0.18.5 was the simplest update ever with just a small hotfix for federating moderation actions (which is a really important bugfix) and it didn’t have any changes to the database or configuration or dependencies
Having a look, the only instance with more than 250 monthly active users on 18.4 is Beehaw. They decided to not update after their disagreement with the Lemmy devs.
They refuse to upgrade and then complain that mod tools are insufficient (which have improved a lot in the meantime). You really can’t make this up.
WordPress has automatic updates for core, plugins and themes. I’ve never had any problems with it, running a very basic WordPress site. Would something like that be possible for Lemmy?
I doubt it tbh. A static wordpress site is infinitely less complex than something that constantly needs to take in and distribute content from/to thousands of endpoints with potentially many different api versions on the other side.
Im not that deep into activitypub stuff but from my understanding, automatic updates are not really a good idea in this case.
Federation doesnt have many breaking changes anymore. The bigger problem is if a database migration goes wrong, then there should be an admin around to fix it manually. Im sure Wordpress has the resources for much more thorough testing so these things dont happen.
Just updated :) The broken “feature in local” function made me paranoid and I’m glad it fixed now.
My bad