B) Warning everyone, it slowly eats tokens - If you're like me and on the pro plan, perhaps not a good idea to have its (albeit slow) drain on the tokens.

Not the neatest, but my 'Dad's cookbook' isn't really read by anyone except myself when asking the family what they want me to prep on the weekend for the week.

Step 1: get easily passed, simple looking laws passed to 'protect the children' Step 2: 'oh look at all these people bypassing the law. It's so simple for a child to watch porn with this.' Step 3: increase the requirements bit by bit on the verification

By letting something simple pass, they can claim it's not thst bad, and anyone who argues against it is being hyperbolic.

Or they just are truly that incompetent.

Once this(Zero-mem) passes it's peer review, I may have to see if my system can handle something similar instead/in addition.

I'm quite excited to see growth in these different ways of eliminating token's.

Long winded aside, @langs, have you published your work on this?

I think that's the point OP is pointing out, for better or worse (for what it's worth I believe "He suggests that a prior conflict with the CFIA over product labeling motivated them to close the factory before the inspection began" may be correct).

A company should have plans for cleaning up their product before just walking away and leaving other people to clean up their mess.

Maybe it's rather naive of me, but that's what I believe.

I'm assuming that all works even with application sandboxing (1) or am I mis-reading how that is applied to applications.

Man I need to move my movement to GrapheneOS up to be sooner.

(1) https://source.android.com/docs/security/app-sandbox

From what I can understand of it:

* Read the target user's NTUSER.DAT hive into memory as a backup.

* Open the hive offline using the Offline Registry (offreg) API.

* Modify HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Local AppData to point at \\.\GlobalRoot\BaseNamedObjects\Restricted.

* Save the modified hive and replace the original NTUSER.DAT.

* Copy the user's UsrClass.dat into the temporary working directory.

* Acquire a batch oplock on the copied UsrClass.dat to synchronize execution with profile loading.

* Start a suspended process using CreateProcessWithLogonW(..., LOGON_WITH_PROFILE, ...), triggering the User Profile Service to load the profile.

* Wait for the oplock to break when Windows attempts to access UsrClass.dat

https://blog.projectnightcrawler.dev/posts/2026-07-14-legacy...

update: formatting :s

Comments URL: https://news.ycombinator.com/item?id=48917041

Points: 3

# Comments: 1

Also interesting to see who coined the term prompt injection.

Look I like interacting with these tools as much as the next guy, but I'm certainly not going to trust them with access to information and then allow anyone to send them prompts.

Edit/further thoughts: So (assumable as they said this is disclosed with github's knowledge) this has been patched. But how many different word combinations will it take to find another way to have this occur?

(young-un with the 28.8k starter here, so I just need some stretching to keep up with you old fellas :P)