I’ve just had a really odd situation on iOS with the latest build. Go into a post and add a comment, come back out and the timeline jumps forward or occasionally back a few posts.
FelipeFelop
joined 1 year ago
Mlem is now in the App Store with full 0.19RC support. Looks fantastic.
It depends what country you are in. In the UK a retailer must accept electronic items for recycling (or provide you with the details of a free recycling service) The local council will have a recycling service (in most areas small appliances can be left out with your recycling bin). For items which might have a value there are companies that will buy them from you for a small amount and then recycle.
Please do not take them to a charity shop without checking beforehand as many cannot afford the testing needed before they can resell.
There have been reports of Samsungs on the newest OneUI giving that message with React apps and some notifications.
That is how I guessed you had a Samsung.
Sorry, I haven’t heard how this can be resolved l, it might need Samsung to do an update.
By any chance is this a Samsung and you’ve just updated OneUI?
Are you using the Android app or the PWA?
Just to add that the following are compatible with 0.19
Voyager - the daddy of Lemmy clients Sync (as of today) Avelon Mlem (RC in beta has full support, production works )
I’m sure there are others
When the first betas of 0.19 went out about two months ago, I contacted the Devs(plural) on Matrix.
Let’s just say Liftoff! Does not work when you are logged in to an instance that upgrades to 0.19 and cannot log in on 0.19. There’s no sign of any commits since August.
He’s moved on and anyway he says PixelPals now makes more money than Apollo did.
I think people are reading too much into a short comment from months ago.
I agree. Also see the numerous release candidates there have been for 0.19 and the lack of backwards compatibility.
There’s not just one Developer. If I remember correctly there’s at least two doing different things.
I agree it’s really annoying to open the link rather than the post.