Hacker Newsnew | past | comments | ask | show | jobs | submit | nottorp's commentslogin

And Romanians.

Oh I'm sure OpenAI or Anthropic will vibe disprove Turing any day now!

That's an old "AI" joke. It went like that:

They asked a computer how to minimize production expenses at a factory. The computer said: "Do not manufacture anything, expenses will be zero".

I believe it's been around since expert systems at least.


If you're distrustful of anything, why do you trust the number of git stars? It's something easily botted after all.

> When you have to handle a colleague’s computer, it gets much more inconvenient.

Let's add to that: What if you're on holiday and your phone gets stolen or is suddenly 20 meters under water because it fell off the boat?

What if you are a normal person who only has a phone and it simply dies for one reason or another?

You get a new phone then hire the boat again, go above where your phone fell in and hope it syncs your passkeys?


How do you solve these problems other than memorizing every password? I guess you could keep a piece of paper with backup codes, but that works for passkeys too if you use the right manager.

You should always plan for your currently active device to be bricked suddenly and act accordingly.

You either should treat your passkeys with a backup like any data, this can mean multiple hardware keys or a cloud backup of your passkey, like bitwarden or the provider's native backups.


The key word in the post you're replying to is "normal". Non-technical people don't (in my experience) plan for this kind of thing, like at all.

The idea of multiple hardware keys, which have to be enrolled individually to every site, is just not an ordinary end-user friendly activity.

So passkeys may be great for technical users (who are happy doing that) or corporate users (where centralized IT systems can be put in place) but not for standard non-corp users (which realistically, is most people)


Bet you have a home lab.

Not talking about you. After all passkeys are not there to protect people who have home labs and don't recycle passwords anyway? They're for normal people who only have one device.

> who are happy doing that

You think they're happy? I'd say they grudgingly comply at best.

Suppose you do want a secure solution for the main sites your stuff is on. But every piece of shit content mill also wants to set up a passkey.

Edit: wow i missed this:

> a cloud backup of your passkey

... which is protected with what, a passkey?


Do you? If you disable all notifications you have to make a conscious effort to open a time sink. In time you'll start to forget, esp if you get busy with something.

And HN is arguably better than doomscrolling TikTok or Facebook, even with the current LLM/Rust/LLM in Rust spam.


Rain tends to just move the dirt around, at least where I am.

Where do you live? I live in the Midwest (SE MI) and when there's rain it tends to be medium-to-heavy rain and with wind so sideways.

Other continent :)

You ever park under trees?


Ah. Fair enough. Haha.

And rarely. There is unfortunately a dirth of trees in my area since I live in a small farming town.


"Optional global or personal access token used to authenticate extension requests."

Looks like you can even set authentication up so you can run it at home but connect while you're away too...


Except search. I want search. Going to try this project.

Yeah, about search:

    $ pdfgrep -r -i -n -H "your mom" ~/PDFArchives/
Very effective, very fast, very private. Bonus points if the PDF filename itself is derived from a well formulated <title> tag, such that you can just use “ls” ..

Yes, but that's a solution for the stuff you consciously save. While this is a solution for stuff you see but decide it was interesting weeks after you closed that tab and you only have a vague memory of what it was about.

You could combine it with existing products like DevonThink that are meant for researchers organizing documents and provide tagging, semantic search, similarity graphs, and so on.

He includes a photo :)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: