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.

For me it was the prose that alarmed me. Short sentences, aggressive punctuation, desperately trying to keep you engaged. It is totally possible to ask the model to choose a different style - I think that's either the default or corresponds to tastes of the content creators

> 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.

The point being we can simply tell our agents to start at the rug pull point and implement the same features and bug fixes on the Apache fork referring to the AGPL implementation.

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.

The two projects have literally nothing in common. Not a line of code, not the approach, nor the design. Nothing. LLMs are not memorization machines that recall every project in the cut & paste terms you could think of.

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.

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);})()

Why wrap in a lambda?

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.

Could be to allow use of local variables that do not leak into the scope this code is executed in. That's what I use this pattern for.

pro tip: no longer necessary

    { let count = 50; const interval = setInterval(() => { addSnakeNode(); if (--count <= 0) clearInterval(interval); }, 100) }

And polluting the global variable namespace hardly matters when using the console.

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)

https://github.com/vritvo/henge_finder

For me on desktop there's no info other than "Henge Finder requires a desktop or laptop computer" (Chrome/Edge/Firefox on Windows, not exactly uncommon!).

The following in the browser console will enable it:

  document.querySelector('.mobile-block').remove(); document.querySelector('.container').style = ''

Thanks for the summary. Irksome/Curious that the page throws up such a blanket go-away screen when I am using an iPad, which from my perspective is basically the same as a small laptop (only in the browser ofc).