HN user

cannonpalms

155 karma
Posts1
Comments75
View on HN

Those whiteboarding sessions and discussions used to serve as useful opportunities for context building. Where will that context be built within the cycle now? During a production incident?

You can already do what you're looking for by reading the browser cache as new data is cached. This would allow you to see the site as it was loaded originally, instead of simply fetching an updated view from a URL. The data layout for the cache in Firefox and Chrome is available online.

The unfortunate reality is that, depending on your personal preferences, "most modern games" require such a ring 0 anti-cheat. Any game that has a matchmaking mode with a competitive option requires a rootkit.

As an aside, I recently found Riot Games' Vanguard installed on my Linux ESP partition... after having installed the game on my windows partition. It rooted every OS it could find mounted. Incredible.

I've found the latency of /compact makes it unusable. Perhaps this is just the result of my waiting until I have 0% context remaining.

Fun fact, a large chunk of context is reserved for compaction. When you are shown that you have "0% context remaining," it's actually like 30% remaining that's reserved for compaction.

And yet, for some reason I feel like 50% of the time, compaction fails because it runs out of context or hits (non-rate) API limits.

I wonder how well a sentence or two in CLAUDE.md, saying to search the local project for examples of similar use cases or use of internal libraries, would work.

Can you provide more information (or links) about that billing model you describe?

The incentive structure behind paying by the search has diminishing returns, as I see it. You need the results to be of a high enough quality to drive the user to want to run another search with you. Beyond that point, though, in the absence of a direct competitor, where is the incentive for you to continue improving search result quality? M

why publish this?

New versions of Akira and any other ransomware are constantly being developed. This code is specific to a certain version of the malware.

As noted in the article, it also requires:

1. An extremely capable sysadmin 2. A bunch of GPU capacity 3. That the timestamps be brute-forced separately

So it's not exactly a turn-key defeat of Akira.

Restricting config to static values removes quite a bit of the value of config, in my opinion.

Yes, logic should live in code, but very often that logic needs to behave differently depending on some piece of (inherently variable, not static) configuration.

Random examples (written from the perspective of personified code): - How many threads should I use? - On which port should I serve metrics? - Which retry strategy should I use?