If you have a ACSM (the file type Adobe Digital Editions uses for DRM) I’ve been using https://www.acsm-converter.com to strip the DRM and return a standard epub
I tried it on my codebase. There's a lot of overlap with tools like Oxlint / ESLint, I'm not sure that's too valuable vs. a more focused tool that actually focuses solely on 'slop' signals. These lint rules tend to get very opinionated which is why those tools expose so many configuration options.
One real bug tho:
> [ERROR] Imports "mdast" but it's not declared in package.json
A type-only import like `import type { Blockquote, RootContent } from 'mdast';` is actually acceptable if `"@types/mdast": "^4.0.4"` is included in the package.json.
Nice ideas! I've been using the `?` shortcut in atuin [0] which accomplishes the same sort of thing, but these days also has access to an Agent-like experience which allows me to prompt something like "Conventional Commit message for unstaged changes" and it will call `git diff` (after asking permission, of course) and then generate the commit message.
You can strip the DRM fairly easily these days if you have an ACSM file, I vibecoded this the other day after I couldn’t find any online converter that actually worked: https://www.acsm-converter.com
I'm having a hard time adjusting to the Project Panel on the right (and, at least for me, hidden by default) - seems like they're trying to bury the concept of a 'file'?
It's certainly interesting though, and I'll give it some time - the post says "It feels more natural once you've spent a little time with it"
Cute! Cactus for me. Nice animations too - looks like there were multiple of us asking Claude to reverse engineer the system. I did a slightly deeper dive here if you're interested, plus you can see all the options available: https://variety.is/posts/claude-code-buddies/
(I didn't think to include a UUID checker though - nice touch)
I've posted here before about Claude Code's easter eggs [1] and they're back with another one this year for April Fools: Tamagotchi-style "buddies" appearing as ASCII art companions, determined by your userId.
Thanks to the Claude Code source code leak I was able to reverse engineer how it all works. Due to their PRNG choice (Mulberry32) it's trivial to crack all 4.29 billion seeds in seconds.
Some findings:
- 1% legendary chance: 42,989,564 seeds out of 2^32 produce legendaries
- Stats & shiny appear to be dead code: rolled but never read anywhere. Pure bragging rights?
- Commons can't have hats, only uncommon+ rolls from the hat table
- "God" rolls exist: legendary + shiny + a maxed stat at 100.
Did gemini-2.5-flash-image get an upgrade as well? I just got the following, which is fascinating, and not something I've seen before:
> I'm sorry, but I cannot fulfill your request as it contains conflicting instructions. You asked me to include the self-carved markings on the character's right wrist and to show him clutching his electromancy focus, but you also explicitly stated, "Do NOT include any props, weapons, or objects in the character's hands - hands should be empty." This contradiction prevents me from generating the image as requested.
My prompts are automated (e.g. I'm not writing them) and definitely have contained conflicting instructions in the past.
A quick google search on that error doesn't reveal anything either
That’s weird, pnpm no longer automatically runs lifecycle scripts like preinstall [1], so unless they were running a very old version of pnpm, shouldn’t they have been protected from Shai-Hulud?
Does anyone here understand "interleaved scratchpads" mentioned at the very bottom of the footnotes:
> All evals were run with a 64K thinking budget, interleaved scratchpads, 200K context window, default effort (high), and default sampling settings (temperature, top_p).
I understand scratchpads (e.g. [0] Show Your Work: Scratchpads for Intermediate Computation with Language Models) but not sure about the "interleaved" part, a quick Kagi search did not lead to anything relevant other than Claude itself :)