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

> All cameras have the same problems this one.

My perfectly normal camera does not stream shit to Meta servers or any other cloud. It's in fact fully offline. So, no.

Recording is one thing and sharing the same recording with a hostile foreign entity another.

Legally, many places have strict ban on publishing photos/recordings without consent, while photographing itself is generally allowed in public spaces.

This is before even getting into with issues of recordes d material being used as training material etc, which adds additional ethical and legal issues.


Across most of the world it's pretty difficult to walk around a high traffic area without coming across someone using a smartphone to record their surroundings for FB Live or Instagram, and it's been that way since long before anyone had Meta glasses.

Yours might not, but what other people choose to do with their recordings is out of your control.

You may have a specific issue with the fact that the media goes through meta’s services, but that’s not the point that is being made in this thread.

All of the ethical and legal issues apply to all other cameras and camera footage too.


Debian installer runs fine over serial, at least.

By "happened to a lawyer" you mean "was done by a lawyer".

If this is your only blocker you could still use passkeys with a different provider, like KeepassXC?

Not while the spec has provisions to allow sites to mandate certain providers.

The pitch is that passwords will supposedly be phased out entirely as an option.

I've been told by multiple people that the recovery method of passkeys is to enter your username/password. If passwords are eliminated, your final recourse is fucked.

Why would it be that is the only recovery method? The most convenient one is just more passkeys on other devices of course, but you can have any other recovery methods you want. Magic link emails are the most common, but there is nothing about passkeys stopping you from implementing anything you want.

Which is a laudible goal, but something that makes "oh just fall back to the standard insecure recovery process" not a very good response to the concerns about users being able to actually hold on to their passkeys easily and reliably.

"What has science done?!"

With that assertion, every running PC has consciousness and a self-bootstrapping compiler or a debugger attached to itself are sentient?

Doesn't seem meaningful.


> debugger attached to itself are sentient?

No standard debugger is capable of being attached to it's own instance.

Nor does a self-bootstrapping compiler point towards it's own instance.

I think from these two examples I should clarify:

A process that processes itself as an input, is definitionally self-aware.


You would find a mention of that in the initial July incident post from HuggingFace. It looks like it was indeed pretty high up the list.

https://huggingface.co/blog/security-incident-july-2026

> We are working with outside cybersecurity forensic specialists to investigate the issue and review our security policies and procedures. Finally, we have also reported this incident to law enforcement agencies.

Do we expect Nvidia acquisition of HF to have changed the vibe? Note that also the OP is from July, before the acquisition.


> Read the full story here: https://www.effort.news/irregular

That is a better link for the story than the current (alt: https://xxcancel.com/brianchau57/status/2099580981271318606).

It was previously submitted but was quickly flagged out. https://news.ycombinator.com/item?id=49704132


> Note that even OS kernels can have this issue - imagine what happens in virtualized environments with overcommitted physical CPU's scheduled by a hypervisor as virtual CPU's? Yeah - exactly. Don't do that. Or at least be aware of it, and have some virtualization-aware paravirtualized spinlock so that you can tell the hypervisor that "hey, don't do that to me right now, I'm in a critical region".

I can't be the only one who learned this the hard way by cramming too many vCPUs onto too few physical cores and initially wondering where the high load and latencies came from.


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

Search: