That also needs updating. According to a post on Lemmy.ml all apps will need updating for 0.19 Some changes are also in 0.18.5 so most apps will need an update to work properly. (you might not be able to Login but if you’re already logged in you’ll see your feed but not the list of communities. The app will have needed to test against 0.18.4b8 or higher)
I emailed him a couple of days ago (as some of the changes are also in 0.18.5 which is rolling out today)
It seems to me that as well as the bullies (apparently it’s all my fault for not choosing instances by running a detailed analysis and not being aware of things that wouldn’t happen for months after I joined!) there’s also users who genuinely haven’t noticed any issues. Although they are on problematic instances and using apps the developer knows needs an update.
So it’s quite possible Lemmy will survive with most users on one or two big instances and some more who don’t know they are on troublesome instances.
Check the liftoff developers chat. They know it isn’t working properly but have had PRs failing.
Have you tried it? It’s unfortunately not reliable.
Wait until it’s updated (it’s missed 0.18.4 bug fix, 0.18.5 is rolling out and 0.19 is imminent)
I like Lemmy, what I don’t like is the haphazard time consuming way it works.
Sync is not compatible (until it’s updated) as more instances roll out newer versions you’ll get authentication errors.
None of those apps cope with the changes. Which were introduced about three weeks ago in beta so plenty of time to update.
Liftoff hasn’t had an update in three months and doesn’t work properly with anything above 0.18.3 and get worse as the version number increases.
It’s a faff though isn’t it ? There’s no easy way to migrate subscriptions. And that doesn’t solve the issue of the web interface or apps not updating.
Is Thunder working with Lemmy v0.19?
Voyager has also entered a period of inactivity and is sadly slowly losing compatibility.
I’d say that was obvious, hence the need for the post of it wasn’t caught in beta.
(Edit: the default installation - depending on method - is to update to the latest version which includes RCs. So v0.19 will become more common in the next few days across instances)
Actually, after a while the community list won’t load.
Similar situation with Liftoff! where build have been failing but the bus factor seems to be two there!
Some clients are going to change the # to %23 which won’t work with Matrix.to where they should be verbatim.
“https://matrix.to/#/#feddit.uk:matrix.org”
Thanks for setting this up. As you say hopefully he’s okay and it isn’t needed.
Unfortunately this is one of the risks of federation. It’s alleviated on e.g. Mastodon as you must have more than one admin.
The last time Tom was not able to respond I asked about what happens. I was told that basically there’s no provision for this situation so all you can do is use a third party tool to migrate your account elsewhere. I was told that eventually hosting will fail or a manual upgrade will be needed then the instance will be no more.
I asked this the last time Tom was quiet. It seems all we can do is migrate our accounts to another instance using third party tools.
After his last quiet patch, he said that there would be more admins the following week but nothing happened. That’s one reason why people were concerned for his well being.
I’ve been told that 0.18.5 includes the changes from 0.18.4b8 that caused the last round of issues with some apps needing to be updated (eg Voyager) For example, Liftoff didn’t update so will have issues with 0.18.5
According to development chat they can test against it on a test instance but PRs are failing.