Significant whitespace is a dealbreaker for me. I never tried Nim for this reason

I think a better way to look at it is that money is no guarantee of happiness, but it usually doesn't hurt, can often help, and you're much more likely to be unhappy if you're poor/struggling.

Whereas I am not trying to take anything away from Woz (I’ve never met that Steve, but by all accounts he’s a really nice guy), I can’t help but feel that his personality and the ethos he espouses have been made a lot more possible by the fact that he had a lot of disposable income…

I saw cuneiform tablets over at the Penn Museum. The text was a lot tighter than what is on these tablets. Still a really neat concept, and it's neat that you can actually read it.

Tbh really curious if these will date to our era and confuse a lot of archaeologists later.

> large object promisors will work like this: - You push a large file to your Git host. - In the background, your Git host offloads that large file to a large object promisor. - When you clone, the Git host tells your Git client about the promisor. - Your client will clone from the Git host, and automagically nab large files from the promisor remote.

This doesn’t seem to solve the issue of the long download time / big repo size. Or is the author describing the use of promisors remotes in conjunction with partial cloning? Unless I missed something it is not stated explicitly.

Exactly. If large files suck in git then that's because the git backend and cloning mechanism sucks for them. Fix that and then let us move on.

Nah - it generalizes fine.

They're doing exactly what I said - adding PoW (anubis - as you point out - being one solution) to gate access.

That's hardly different than things like Captchas which were a big thing even before LLMs, and also required javascript. Frankly - I'd much rather have people put Anubis in front of the site than cloudflare, as an aside.

If the site really was static before, and no JS was needed - LLM scraping taking it down means it was incredibly misconfigured (an rpi can do thousands of reqs/s for static content, and caching is your friend).

---

Another great solution? Just ask users to login (no js needed). I'll stand pretty firmly behind "If you aren't willing to make an account - you don't actually care about the site".

My take is that search engines and sites generating revenue through ads are the most impacted. I just don't have all that much sympathy for either.

Functionally - I think trying to draw a distinction between accessing a site directly and using a tool like an LLM to access a site is a mistake. Like - this was literally the mission statement of the semantic web: "unleash the computer on your behalf to interact with other computers". It just turns out we got there by letting computers deal with unstructured data, instead of making all the data structured.

The entire reason people choose "permissive licenses" is so that it won't last forever. At best, the community can fork the old version without any future features.

Only viral licenses are forever.