![](https://discuss.online/pictrs/image/cb2cc69a-edd1-4ec3-8195-09b973496dd5.jpeg)
![](https://lemmy.world/pictrs/image/d2e1ce0e-4bc8-48ba-8e8c-e0b6fcef159b.png)
But that’s pretty much the standard answer to any suggestion for improvement.
Mid 50s, first went online on a 70s BBS, JANET user in the 80s.
But that’s pretty much the standard answer to any suggestion for improvement.
Thank you for trying to help, I don’t know what 80% of that means or how it relates to an update.
I just don’t understand why there isn’t a simple straightforward update in plain English
I’m sorry but that also doesn’t make sense. This is what I see.
And then the next card is blank!
Please can someone just give a straightforward English update? It doesn’t have to be detailed just enough so I don’t give up.
I’m afraid that means little to me. Hopefully, someone can give an update.
I commented on the announcement a couple of weeks ago but there was no reply.
The announcement made it sound like sublinks was imminent but if you go to sublinks.org everything is still Coming Soon.
Does anyone have an update on the announcement?
I was trying to explain to an elderly friend that people don’t just phone other people now and certainly not at times they will be doing something.
She found it hard to accept that many people find it rude to be called unannounced.
As an example, at one time if someone was organising a social event (eg party) they would phone around to invite people.
But that’s incredibly rude you are imposing on someone and also asking them to decide or excuse themselves on the spot.
Any news?
Is there any news on Sublinks?
I just tried it and it’s doing the same thing for me. I’m sure it worked previously.
this is just awful, there’s something weird in his arm, his head is on backwards (or his knees and feet bend the wrong way) and there’s a strange blue thing sticking out etc etc
This story has been popping up every few months for about the last decade. Usually prompted by someone with something to promote (a dumb phone, a book about downtime, some course )
I’m not sure why you’ve been downvoted. You are completely correct. There is a trail of partially finished projects. Pixelfed itself is in beta after years and years (and competitors seizing the opportunity with more polished products) , there’s SUP, Loops and that fedi directory to name three more.
For me it’s certain settings such as System dark/light mode and Open links in default browser that turn themselves off occasionally following an update.
You don’t feel much difference because they aren’t ten degrees hotter. OP is mistaken.
Dogs are 1 to 3 degrees Fahrenheit warmer than adult humans not 10. A temperature above 104°F needs urgent veterinary help.
Note that human babies and young children are also warmer than adults by about a degree.
Yeah, and some have screens on the front and back of the monitors. And those keyboards have hundreds of keys.
The first record I chose was Ma Na Ma Na by the Muppets. The first record bought with my own money was Never for Ever by Kate Bush
Also, old.
Nothing really changed. Some people who would have taken a ferry changed to the tunnel. But flights became cheaper so the number of people using ferries dropped anyway.
Had you been able to drive straight through then it would have had a bigger effect.
That’s not my point. If you read back up the chain of comments I’m saying there’s a real need for a native app (given that Lemmy apps won’t always be compatible with it)
(And you’ve quoted a part of the post taken out of context 🙂)
That’s not what I’m thinking about. Was hoping not to get too technical (I’ll try to keep thing simple) but there’s a general concern with PWAs that mean they can only support less secure authentication compared to a native app.
For example, if a device is used offline then a PWA can’t authenticate , so anyone who picks up the device can see the users content. There’s a way around this using what’s called a “service worker” which uses device storage but this would need to be different for each device type and some devices won’t persist between sessions. Also, if a user is in an online session then closes the PWA app, goes offline and then back into the app then the service worker will generate an error.
There are other Lemmy specific issues as well I don’t completely remember the detail but it relates to web clients not being able to set a custom cookie header to ensure compatibility (CORS limitation) There’s an explanation somewhere in the Voyager community but I couldn’t immediately scroll back enough to find it.
They weren’t actually tiny, they were about a metre long. But they do seem out of proportion.
They were very muscular and ended in very sharp talons, so pretty deadly.