Thank you.
Possibly add an update on the announcement post(that promised regular updates)?
Mid 50s, first went online on a 70s BBS, JANET user in the 80s.
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!
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.
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.
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.
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.
Phones encrypt the data by default, your password or pin is also needed to authorise the connection with a computer.
However, many people do insecure things like storing passwords etc in Notes applications, or having simple PINs that are easy to guess, don’t update their devices, or even turning off security features (if they can) because they won’t take a small amount of time to understand them.