this post was submitted on 01 Jun 2024
1020 points (98.1% liked)

Technology

58303 readers
63 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Q. Is this really as harmful as you think?

A. Go to your parents house, your grandparents house etc and look at their Windows PC, look at the installed software in the past year, and try to use the device. Run some antivirus scans. There’s no way this implementation doesn’t end in tears — there’s a reason there’s a trillion dollar security industry, and that most problems revolve around malware and endpoints.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 102 points 5 months ago* (last edited 5 months ago) (29 children)

It's encrypted; the author is pointing out that it has to be decrypted to be used, and then the data can be obtained.

Security and privacy concerns aside, I saw someone commenting on the use case, asking who would ever want something like this.

One problem I hadn't appreciated for a long time was that some people apparently have real problems with dealing with the Windows UI in terms of file access. They don't know where their data is being saved. This, in my opinion, is in significant part a Microsoft UI problem induced by various virtual interfaces being slapped on top of the filesystem ("Desktop", "My Documents", application save directories, etc) to try to patch over the issue that the filesystem layout was kinda organically-designed in a kind of cryptic way back in the day.

But if you can remember a snippet of text in what you were working on, you can find that thing again even if you have no idea where you stored it. Like, it's content-keyed file access.

That's not very useful to a techie. They know how to navigate their system's filesystem, and even if they lose track of a particular thing, they know how to use the system's filesystem search tools to search for filenames or content. They can search for recently-modified files. They know how to generally get ahold of stuff.

But for the people who can't do that, reducing their interface to a single search box might make file access more approachable.

Now, let me reiterate that I think that a whole lot of this is Microsoft repeatedly patching over UI problems they created in the past rather than fixing them. And they've done this before over the decades with stuff other than document access. It's hard to navigate the filesystem to find an installed program a la the MS-DOS era, so they stick stuff in a Start Menu to make it more accessible. That gets too crowded, installers start slapping shortcuts on the desktop. That gets too crowded, installers start adding system tray icons. That gets too crowded, the Start Menu becomes searchable. Each interface just becomes progressively less-usable and the solution each time is to stick a new interface in on top of the old one, which in turn contributes to the complexity of the system as a whole.

But that doesn't mean that they aren't trying to address a real problem.

I think that they'd do better with something like having a rapidly-accessible log of recently-accessed files (like, maybe have the filesystem maintain a time-based doubly-linked list of those) and be able to rapidly search the content of documents based on mod time so that recent stuff gets hit quickly, then trying to make their existing search tools more accessible. That doesn't replicate data across the system and produce some of the problems here. It also permits for fully-searching content, rather than just the stuff that was on a screen when the Recall system grabbed a screenshot and OCRed it. Maybe they've done something like that in recent years; I'm many years out-of-date on Windows.

I'd also add that I think that personal computer systems in general would benefit from giving users better control over where their data is replicated to. It's kind of confusing...you've got swap (well, encrypted swap probably helps somewhat with this). Browser history. Any clipboard manager's retention. Credentials stores. Application-saved copies of in-progress files. Various caches. If you use some kind of cloud-based storage, you're pushing data out to other computers. Backups. Just a lot of state that can be replicated all over the place and is hard to go back and track down and remove. That's even before stuff like issues with doing secure deletion on existing filesystems (which we had a conversation about the other day, everything from log-structured filesystems to wear-leveling on SSDs inducing data replication). If you want something definitely gone, be able to manage your data's lifetime, something that I think that a lot of people -- even non-techies -- would like, you really have to have a lot of technical knowledge of the system's internals as things stand today. This Recall thing is egregious, replicates data all over, but it's far from the first feature that makes it harder for people to understand and control the lifetime of data on their computer.

I don't think that the software world has done a great job of letting people control that data lifetime. And I think that it's something that a user should reasonably be able to expect out of their computer.

[–] [email protected] 46 points 5 months ago (18 children)

There was an article going around a while ago that was arguing most users these days, including the youth we often stereotype as "digital natives" who "get computers", don't understand file systems. They might not even know they exist as a concept.

Which makes sense if you've only ever really used modern UIs. You don't have to know anything about files and folders. I bet a lot of people don't even know they exist in any meaningful way.

Most users are shockingly ignorant, and a lot of them are not really paying enough attention or interested enough to learn much.

[–] [email protected] -2 points 5 months ago (7 children)

I don't think any of the UX problems you're describing have been solved on any platform. If anything Windows is one of the better examples here, because I'll be fucked if I can ever find a file on Android and don't get me started with Linux.

[–] [email protected] 0 points 5 months ago (2 children)

You think this is easier to use than grep?

[–] [email protected] 4 points 5 months ago (1 children)

No, neither is easy to use. The second you have to use a terminal or command line you have completely lost the vast majority of people.

[–] [email protected] 1 points 4 months ago (1 children)

I agree, but are you then implying that the windows explorer file search is good? Have you ever used anything else?

[–] [email protected] 1 points 4 months ago

I didn't say it was good, but it is easy to use compared to a terminal. It won't help you find your file, but it's somewhat intuitive to a novice user - you click around and open folders until you find something that looks like what you're after. It's not efficient, it's downright tedious, but it's at least easy to do.

It's all about the barrier to entry to novice users. Most users are novices, they're the majority of the market so they'll decide what the market leader is.

[–] [email protected] 1 points 5 months ago (1 children)

With the tab-completion in Powershell, for someone who doesn't know all the grep flags by heart, it might be easier to stumble through the options to find the ones you want without looking it up.

[–] [email protected] 1 points 4 months ago (1 children)

But it doesn't list them does it? With e.g. zsh I can have the list of flags alongside their explanation, which is not the case with PS I think? I think even bash has it on more recent distros (not entirely sure)

[–] [email protected] 1 points 4 months ago

Looks like you can use Ctrl+Spacebar to open the "MenuComplete" function that should show you the different available options. I don't think you can get a direct list of the parameters that have explanations without using something like Get-Help though.

More info here:

https://learn.microsoft.com/en-us/powershell/scripting/learn/shell/using-keyhandlers?view=powershell-7.4

load more comments (4 replies)
load more comments (14 replies)
load more comments (24 replies)