Thank you.

Possibly add an update on the announcement post(that promised regular updates)?

The point is that calling the computer storage less is what’s wrong.

I can see two issues here:

It’s not really a storageless computer. It’s using EFI as storage to build the ramdisk.

What happens if you need to change things because of a change of cloud account, change of cloud API etc etc

Yes, that’s exactly the point. Combining data is something that must be considered. (And in some jurisdictions like the EU you even need to consider if it could be combined in future with other data)

Not sure I agree entirely. The actions I take are definitely data about me.

Also, in many jurisdictions data that could be combined (even in the future) with other data to identify you or something about you, is considered personal data.

For example, Device ID is AstridWipenaugh’s device and they use the app in the morning.

I think you’ve missed the point. It’s not the data they are collecting but the fact they say they don’t collect data.

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!

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?

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.

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.

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.

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.

Are there any apps being developed for Sublinks?