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)
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.
When they mess up (which happens a lot), why does he always go down the “you’ve hurt my feelings, we are only human route” ? That’s why they never learn from their mistakes and carry on acting like fools.
I can’t be bothered watching most of their videos anymore because they are so superficial, it’s clear he’s done no or little research and (if it’s on a topic I’ve got some interest in) I can see it’s really innacurate.
A few people have reported that the downvote button disappears and re-appears.
(Some instances don’t allow downvotes but that’s not what’s happening here)
Succeed doesn’t mean to become the greatest, it means to establish itself and survive.
In my opinion the feature you talk about will ultimately end up with small groups or single user instances shouting into the void as hardly anyone is federated with anyone else.
I don’t recognise that expectation. I simply expected to be able to join and interact with friends/online acquaintances without someone else’s decision about something I have no control cutting us off.
As for migration, in most cases you can’t yet migrate your post history and migrating your followers/following list is hit and miss.
These are practical issues that need sorting if the fediverse is to succeed and last. Otherwise people will end up back on managed services like Bsky, threads and Reddit.
Have you seen the jokey post going around. This is what it feels like in the fediverse.
“Hey, can you switch instances? Your admin favorited a joke that I didn’t appreciate once. Might need to block you otherwise. Oh, and that crowdfunding platform you use? Back in 2006 they let an organization I don’t personally align with use their platform. You should abandon that. Also, -”
But what happens if the instance you are on is defederated through no fault of your own. As has already happened, even not through the fault of the instance admin but another instance making a mistake and adding it to a block list.
There isn’t an easy way to migrate everything to a new instance. And the migration options we do have a a bit buggy.
Perhaps people have seen the survey of ex-mastodon users? It really brings out that federation is simultaneously an advantage and a problem.
At the moment, it looks like the only solution is to have multiple accounts and when you do it’s starkly evident that there’s content that you miss because of federation issues
I’m beginning to think you might be trolling but I’ll give you the benefit of the doubt.
Some estimates put literacy in the ancient world as high as 40% excluding people who could read and write their name and basic words The decline in literacy after the Roman Empire is well documented and didn’t increase again until the Middle Ages. Buring and Van Zanden put the year 1451 as the point when it began to rise again.
If you want to see some discussion have a look here https://forum.paradoxplaza.com/forum/threads/literacy-rates-of-the-ancient-and-medieval-world.340325/
But what happens (as did recently) when instances change direction? What happens (as did last year) where one instance admin had the wrong contact details for another so a message didn’t get through and ended up with an instance blocked and defederated for no good reason. What happens when an admin has an episode and gets in an argument that results in tit for tat blocks.
How can any new user know this might happen? How can they know what they are signing up for when descriptions are so brief?
Defederation is a good thing but unfortunately the people are human and fallible.
The point is that as a user I have no control who else is on the instance but could get defederated anyway.
From the posts I’ve seen several admins have clear mental health issues. Silly rivalries and imagined upsets cause whole instances to be defederated. It’s sad in a way as most federations have councils or independent regulators to step in so that members don’t lose out by the actions of others. But not the fediverse.
That’s not what you asked for. I gave an illustration of the Bible being needed in English (which most people read) rather than Latin. So I gave you a source.
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.