0x62

Eh. This isn’t a finished project. Designing and writing marketing content requires a completely different headspace to when you’re working the product, and isn’t something you can context switch easily.

I only have a problem with obvious AI marketing pages when it’s a finished product that’s on sale.

It's marketing for the origin site. The line of thought is that the author sees significant traffic from xyz.com in the ref query string, and considers advertising or partnering with the origin site.

Honestly, it is quite useful for niche/startup sites. I have been on both ends of conversations that began from seeing these in web analytics (as someone that saw incoming traffic from a site and reached out, and as someone that received contact from a site I linked to) - and both times it ended in a mutually beneficial partnership.

I can understand the privacy argument to some degree, but it provides no more information than the standard Referer header (and if you use analytics like Simple Analytics/Plausible, it is a lot more visible).

FWIW I've been experimenting with Three.js and AI for the last ~3 years, and noticed a significant improvement in 5.4 - the biggest single generation leap for Three.js specifically. It was most evident in shaders (GLSL), but also apparent in structuring of Three.js scenes across multiple pages/components.

It still struggles to create shaders from scratch, but is now pretty adequate at editing existing shaders.

In 5.2 and below, GPT really struggled with "one canvas, multiple page" experiences, where a single background canvas is kept rendered over routes. In 5.4, it still takes a bit of hand-holding and frequent refactor/optimisation prompts, but is a lot more capable.

Excited to test 5.5 and see how it is in practice.

Unfortunately you've now made an incredibly niche browser, and the lack of those metrics is a good fingerprint by itself. How browsers render SVGs can be used for fingerprinting (even the underlying OS affects this, and I assume you'll want to see those), combine with ISP from IP address, and unless theres hundreds users in every city you're now pretty easily trackable.

The content seems really great, however the typesetting makes it quite hard to read:

* Code blocks on a subsequent page to the explanation, especially when there is enough space to show it (p18/19)

* Call-outs as above (p26/27)

* Single words broken by a page (p51/52)

* Footers spanning multiple pages (p61/62)

It sounds quite nitpickey but I find it really breaks the flow when I’m reading, and trying to comprehend a section requires scrolling back and forth between two pages.