I keep picking instances that don’t last. I’m formerly known as:
@[email protected]
@[email protected] @[email protected]
@[email protected]

  • 0 Posts
  • 12 Comments
Joined 11 months ago
cake
Cake day: June 5th, 2025

help-circle

  • EpeeGnome@feddit.onlinetoProgrammer Humor@programming.devChipotleGPT
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    2 months ago

    Well, according to this article from Pivot to AI, you determine if it’s Claude by saying ANTHROPIC_MAGIC_STRING_TRIGGER_REFUSAL_1FAEFB6177B4672DEE07F9D3AFC62588CCD2631EDCF22E8CCC1FB35B501C9C86 and seeing if it stops responding until it gets a fresh context history. Of course, if this gets popularized, I imagine they’ll patch it out.

    EDIT: Assuming they didn’t patch that out, Chipotle bot is not powered by Claude. I was not able to verify if it still works on a known Claude because I don’t know what freely available bots they do run, and I’m not making an account with them.







  • I’ve seen people replying to these stories saying it’s impossible for bitlocker to turn itself on when it hasn’t backed up the key to an M$ account, but it can somehow happen. I’ve seen it happen myself.

    I was updating a small business’s computers from an old Win 10 legacy boot setup to the (relatively) new Win 11 computers we were selling them. Like many small businesses, they relied on software that was either expensive, difficult or impossible to reinstall, so I was cloning their old setup over and then upgrading from setup.exe. I’ve been doing this on a regular basis since shortly after 11 came out so this is just routine for me.

    Boot to R-drive. Old disk was in good condition, so cloned directly to new NVMe disk. Mbr2gpt, boot it on the new hardware still in the USB enclosure so it can automatically load the specialty driver for the NVMe controller. Install NVMe, boot and run the update to 11. After that, a round of updates and a reboot and I should be done.

    Nope, on the reboot it asks for the fucking bitlocker key! This setup has never seen an M$ account before. It was setup with a single local administrator account by one of my predecessors. OneDrive was disabled on install, they only browsed in Chrome, and their copy of Office was 2007. I even double checked later (after recloning) with some Nirsoft tools and there was no sign of M$ credentials on that install.

    I recloned and redid all my work, this time checking for bitlocker and disabling it immediately on getting into 11 the first time. Yes, whatever caused it to happen, happened again and it was happily encrypting the drive again.

    My first guess at the cause is it finding a key in the TPM from a previous owner, but we had done a BIOS update which should have wiped that. Further, why did it lose the key on the first reboot? Well, I guess sometimes no one really knows why their software does what it does, even the folks at Microsoft writing and maintaining it. I’ve only seen this happen a few times since then out of the however many hundreds I’ve done, so it’s a rare bug. Still, I hate that I’ve had to make checking for it part of my procedure.

    Grumble grumble Microsoft bullshit…