FelipeFelop

joined 2 years ago
[–] FelipeFelop@discuss.online 8 points 1 year ago (6 children)

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

Really wish people would learn how to use AI.

[–] FelipeFelop@discuss.online 1 points 1 year ago

yes, there’s lots wrong with picture.

[–] FelipeFelop@discuss.online 3 points 1 year ago (6 children)

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

[–] FelipeFelop@discuss.online 3 points 1 year ago

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.

[–] FelipeFelop@discuss.online 2 points 1 year ago

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.

[–] FelipeFelop@discuss.online 1 points 1 year ago (2 children)

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 🙂)

[–] FelipeFelop@discuss.online 1 points 1 year ago (4 children)

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.

[–] FelipeFelop@discuss.online 2 points 1 year ago

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

[–] FelipeFelop@discuss.online 1 points 1 year ago* (last edited 1 year ago) (6 children)

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

Which is why the native apps are preferred for Voyager.

[–] FelipeFelop@discuss.online 1 points 1 year ago (9 children)

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.

[–] FelipeFelop@discuss.online 2 points 1 year ago (11 children)

That was my reason for asking about sublinks apps.

I know that devs like web interfaces but the truth is you need apps if anything social is going to become established.

It’s a sad fact in the fediverse that routinely apps or even front end GUI aren’t compatible. There’s only so many times this can happen (or instances shut down or not be maintained) before it all becomes a bit much.

So I think relying on Lemmy apps is a mistake.

[–] FelipeFelop@discuss.online 1 points 1 year ago (13 children)

I’m confused now, the post above says that there will be initial compatibility but after that (presumably as sublinks evolves) Lemmy apps will have to display as best they can.

view more: ‹ prev next ›