Claude Code can decrypt summarized reasoning traces sent by the API.
Can you cite specifically what in the linked article or discussion leads you to say that?
HN user
Claude Code can decrypt summarized reasoning traces sent by the API.
Can you cite specifically what in the linked article or discussion leads you to say that?
No, it looks like the domain was taken over by squatters after CA went defunct in 2018, and they're currently using it for AI-generated "content".
Like others here, the content is something that I'm interested in, but I too have a reaction to the LLM-isms. I think part of it is that, once I recognize I'm reading LLM output, I have no way of knowing if it wrote the whole post based on a one-or-two sentence prompt or not, and if it did, how much can I really trust the output to not be hallucinated. If I'm going to read LLM output, I'd rather do so in the context of my own chat with it so I can understand the inputs to it and ask follow-up questions.
Can you put the pre-LLM version of your post on your site somewhere? I (and presumably many others) would be much more interested in reading that, even if the English is a bit awkward.
It's much worse than it used to be. Before it was only really a problem with apps with a lot of menus, and you could access the items by switching to an app with fewer of them. Now, the notch takes up a lot of space, and you hit it really soon on a 14" display—I can only have maybe three third party menu applets on top of my collection of built-in ones before they disappear into the notch.
getsupport.apple.com.phish.xyz
I notice that a lot of scam texts use domains that start with a TLD followed by a hyphen, like:
https://wa.gov-phish.fit/dol
https://seattle.gov-phish.cc/dmv
(Real examples, with "phish" replacing a string of 3-4 random letters)In some ways, it's a more convincing fake URL, since even if you're used to reading the domain right-to-left, your brain wants to start from the hyphen since it's a different character following a familiar TLD. But that type of domain also seems a lot easier for spam detection rules to catch.
Not too sure of the utility of this. It's not an easy sentence to remember, because while grammatical, it's nonsense—it would take some effort. So if I'm trying to memorize a static IP, setting up a DNS name is likely to be easier. And also if I'm going to be using this to memorize IPs I'd like the algorithm to be open source.
All that being said, I think it's a neat idea and a cool tool!
I didn't get that sense from the prose; it didn't have the usual LLM hallmarks to me, though I'm not enough of an expert in the space to pick up on inaccuracies/hallucinations.
The "TRAINING" visualization does seem synthetic though, the graph is a bit too "perfect" and it's odd that the generated names don't update for every step.
it really makes me doubt that what is written there is actually true at all
Indeed, the whole "Ironically, switching from Apache 2.0 to AGPL irrevocably makes the project forkable" section seems misguided. Apache 2.0-licensed software is just as forkable.
Website is offline, archived snapshot: https://web.archive.org/web/20260227201321/https://www.origa...
They are commonly used synonymously. English as she is spoke is not a logical language.
https://www.merriam-webster.com/grammar/could-couldnt-care-l...
https://dictionary.cambridge.org/dictionary/english/could-ca...
I wanted to see if, with the assistance of modern AI, I could reproduce this work in a more concise way, from scratch, in a weekend.
I don't think it counts as recreating a project "from scratch" if the model that you're using was trained against it. Claude Opus 4.5 is aware of the stable-diffusion.cpp project and can answer some questions about it and its code-base (with mixed accuracy) with web search turned off.
I have had issues with resizing Quick Look windows with their rounded corners on macOS for the last several major versions, well before Tahoe. The resize cursor indicator there also doesn't seem to appear at the correct location for the actual resize handles.
Because I learned JS before ECMAScript 6 was widely supported by browsers and haven't written a ton of it targeting modern browsers. You're right that it's unnecessary.
Here's a console command you can run to increase the snake length immediately, and thus the difficulty:
(() => { let count = 50; const delay = 100; const interval = setInterval(() => { addSnakeNode(); if (--count <= 0) clearInterval(interval); }, delay);})()Pagination is also buggy, as the live results interfere with the historical ones.
Ports are a derivative work; you should preserve the original author's copyright attribution.
On mobile there's no info other than "please visit from a desktop/laptop computer", so for anyone else not near one:
Finds when the sun aligns with your street for a perfect sunset view (like Manhattanhenge).
* Enter an address to check for alignment with the sunset (or more specifically, alignment a little before sunset, the last moment the sun is at 50˚)
* Shows street bearing and sun alignment information
* Displays coordinates and next henge date (if there is one)
a linear array of all the 4 billion values, with the key as array index, which fits in 16 GiB
The hash table has the significant advantage of having a much smaller minimum size.
Perhaps text strings as keys and values would give a more interesting example
Keep reading to "If keys and values are larger than 32 bits"
HTML4 was the "sloppy" answer to XHTML
I think you mean HTML5, which exhaustively specified how to do parsing in a fault-tolerant, normalizing way. HTML 4 (and 4.01) predated XHTML 1.0, and HTML 4.01 attempted to take things in a stricter direction, introducing a "Strict" DTD that did things like drop the <font> tag, in pursuit of separating structure and presentation.
Reddit discussion gives some additional context (and background on Brad Spengler) here: https://www.reddit.com/r/programming/comments/1oc38d2/ai_bro...
Apparently, "all you need is [...] this: [bytes]" is the hash of an undisclosed exploit proof-of-concept. And the relationship between Spengler and Linux maintainers has been somewhat contentious for the better part of a decade: https://news.ycombinator.com/item?id=13312723
They removed other maintainers access to their AWS account, and one of them had allegedly taken a screenshot of the root password from a password manager
Inaccurate:
Ruby Central also had not removed me as an “owner” of the Ruby Central GitHub Organization. They also had not rotated any of the credentials shared across the operational team using the RubyGems 1Password account.
I believe Ruby Central confused themselves into thinking the “Ruby Central” 1Password account was used by operators, and they did revoke my access there. However, that 1Password account was not used by the open source team of RubyGems.org service operators. Instead, we used the “RubyGems” 1Password account, which was full of operational credentials. Ruby Central did not remove me from the “RubyGems” 1Password account, even as of today. https://andre.arko.net/2025/10/09/the-rubygems-security-inci...
Ruby Central didn't realize that they hadn't actually revoked any access to the previous maintainers (and that they didn't have the updated root AWS credentials) until two weeks later when André notified them.
What libraries/models is this built on?
Related:
Copy-and-Patch: Fast compilation for high-level languages and bytecode (2020) https://news.ycombinator.com/item?id=40553448 - June 2024 (51 comments)
A copy-and-patch JIT compiler for CPython - https://news.ycombinator.com/item?id=38769874 - Dec 2023 (68 comments)
Copy-and-Patch: Fast JIT Compilation for SQL, WebAssembly, and Others - https://news.ycombinator.com/item?id=28547057 - Sept 2021 (7 comments)
A happy(ish) ending: https://www.reddit.com/r/Mattress/comments/1l81nn6/and_were_...
RealPage enforced adherence to its pricing recommendations through assigning pricing advisors to its clients, providing “lease compliance reports” listing the names of individual employees who overrode price recommendations, requiring employees to provide business justifications for price overrides, and offering some clients quarterly “performance to market” meetings “designed to identify how compliant the client was with RealPage’s pricing recommendations during the prior quarter.” https://www.tnmd.uscourts.gov/sites/tnmd/files/690.pdf
The investigation found that RealPage’s pricing software provides landlords with a shared logic that tends to raise rents. Two types of RealPage’s pricing software collect nonpublic, competitively sensitive data from landlords to feed the algorithms. Landlords who use RealPage software agree to provide their data, knowing that the software combines their data with data from other landlords. The algorithm then recommends rents — in many cases increasing them. In feedback to RealPage about its software, one potential client said: “I always liked this product because your algorithm uses proprietary data from other subscribers to suggest rents and term. That’s classic price fixing.” https://www.atg.wa.gov/news/news-releases/washington-ag-says...
Just "distributing marketplace data".
It's a good write-up but I wish this blog post went just a little bit deeper with the investigation to confirm whether this is the issue (ollama.tymscar.com having an AAAA record); it's missing the answer to "Why is the JVM trying (or initializing toward) an IPv6 path first and not gracefully falling back?"
The idea is to create another page on your blog that has all the RSS feeds you're subscribed to. By keeping this public and always up to date, someone can visit your page, find someone new and follow them. Perhaps that person also has a feeds page, and the cycle continues until there is a natural and organic network of people all sharing with each other. So if you have a blog, consider making a feeds page and sharing it! If your RSS reader supports OPML file exports and imports, perhaps you can share that file as well to make it easier to share your feeds.
This is usually called a "blogroll", which has the advantage of being much less ambiguous/overloaded than "feeds".
There are also fans who record what happens in baseball games purely for their own enjoyment.
https://en.wikipedia.org/wiki/Baseball_scorekeeping
https://www.reddit.com/r/BaseballScorecards/
https://www.reddit.com/r/baseball/comments/1lzpwrq/reasons_i... / https://www.reddit.com/r/baseball/comments/68qdm9/people_who...
It's unfortunate because there's plenty of good, technical, perfectly readable content in the author's blog archive from 2021 and earlier without the overwrought purple prose.
doesn't rsync already use content-defined chunk boundaries, with a condition on the rolling hash to define boundaries?
No, it operates on fixed size blocks over the destination file. However, by using a rolling hash, it can detect those blocks at any offset within the source file to avoid re-transferring them.