Matthew Prince, CEO of Cloudflare, talks about AI bots and publishers.
Some of the points he makes are:

And here are my considerations:

  1. The more a page has "fame", the more it's crawled by the bots.
    The more a page is linked and cited, the more it's crawled by the bots.
    The more a page has fame, the more its content has a chance to be in an LLM answer. And I think sharing the message/opinion/point-of-view is more important than fame per se.
  2. "Ads aren't seen" and "Subs aren't sold" are the same problem: money.

So, given I don't see the ego/fame point as a problem, everything comes down to the money aspect. And so, what's the consequence? That you don't earn by writing on the web ⇒ no clickbait, no ads, free content, more independent publishers and less corporate publishers.

Link to the video: https://x.com/carlhendy/status/1938465616442306871

Read A Programmable Web: An Unfinished Work, by Aaron Swartz.
It makes a bunch of interesting points related to: openess of data, API design, structure of URLs, Digest access authentication built-in HTTP, stateless web, robots & crawlers.

I wouldn't write this today: https://medium.com/@alessandrotambellini03/my-view-of-a-browser-5e7b6122832c .

Yesterday I started building a browser. I'll see where it goes. The first phase is going to be about experimentation.

Converted the Primes Spiral repo to a Gist: primes-spiral.html

About the idiosyncrasies of the HTML parser , Take a look at this Gist: Idiosyncrasy of the HTML parser

In these days I played with ray-tracing and has been the opportunity to use the <canvas>: rt .

I discovered an interesting CSS property: hyphens .

I released on GitHub ReqLoop: https://github.com/AlessandroTambellini/ReqLoop/. This project was also an occasion to play with <template> and ResizeObserver .

http://herpolhode.com/rob/

I revisited and reshaped a little article about the NAND gate that I wrote 3 years ago:
Just a NAND gate

Today I read Idiosyncrasies of the HTML parser.
To be precise, I read the first two chapters and skimmed the third one.
What I understood is that the HTML parser of browsers is built to handle any type of "writing style" plus, without ever throwing an error. In the style of: "Hey, don't worry, however you write it's fine and we are never gonna throw you an error!".
It remembers me of an interview to Brendan Eich where he says that from the first draft of JS the equality operator == was the strict equality one but then, people persuaded him to make it loosely equal.
Were these decisions made to let people populate the web in the easiest way possible without worrying about the programming barrier?
I can draw a parallel with the decision of YouTube to remove the dislike button at the cost of lowering the quality of the content "to let people express fearlessly". Translated: to populate YouTube.

Gemini protocol, browser, Voronoi:
Making UI in Jai

While reading the emscripten docs, I came across this interesting article: The magic behind configure, make, and make install

Salvatore Sanfilippo mentioned VisiCalc in a video and so I wanted to delve deeper into it:
Was VisiCalc the "first" spreadsheet?