FelipeFelop

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.

Is it “There’s too many legs and arms”?

Really wish people would learn how to use AI.

yes, there’s lots wrong with picture.

There’s AI and then there’s “Oh my God, one of them has a foot pointing backwards”

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.

There is more than one Dev (check GitHub) but no action has taken place since last year.

Aren’t there problems with authentication that cause security concerns when using a PWA?

Which is why the native apps are preferred for Voyager.

Yes, my point is that an App or apps should be part of the design from the outset (see Pixelfed) Good planning rather than chance and potentially messing / confusing people.