Mid 50s, first went online on a 70s BBS, JANET user in the 80s.

  • 3 Posts
  • 195 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle






  • That may well be true, but sounds like general exposition. I should point out that I’m not requesting a detailed roadmap and I don’t think anyone requested communication every step of the way.

    The initial announcement made it sound like launch was imminent. That was months ago and so I imagined (perhaps foolishly) there would be some sort of update posted and hoped it would be in plain English.

    Edit: In fact at the time of the launch jgrim said to stay tuned for regular updates!














  • 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.