An original and dynamic website about the fantasy Thorgal

I like the tech stack with SQLite. This CMS looks interesting for dynamic data.

Une vulgarisation de la faille d'eMudhra

This would be the best occasion to release all images to the creative common licences

Getty Images – which has supplied photos and video for news agencies for more than 30 years – has been struggling amid a pile of debt and mounting competition from AI image generators.

The bankruptcy occurs because AI generated images are used instead of relying on suppliers.

Another classless CSS framework

DevRel(ish) is an index of tech groups and the gatherings they run — in a room, online, or both — across every part of the industry.

This website has rich colors and scenes. It's different from usual design system.

My feeling is that, overall, the situation here is a bit analogous to the discussion here about why I don't like when people talk about how AI gives a 100x or 1000x productivity increase. There are some things that are sped up by a very large factor, easily over 1000000x. And some things don't currently get sped up at all.

The project folderblog looks interesting: turning a folder into a blog sounds promising for small blogs or people who don't want to go technical.

The project is described on https://folderblog.ninepointlabs.com/

The website is well made to learn french

Webhooks should be considered ordered logs.

Webhooks spread because they were the cheapest thing a provider could ship (one HTTP POST) and the cheapest thing a consumer could receive (you already had a web server, so you just added a route).

Webhooks-for-replication are a local optimum, and the proof is the pile of workarounds on the valley floor: signature schemes, dedup stores, idempotent handlers, retry queues with exponential backoff on the provider side and dead-letter queues behind them, webhook logs with replay tooling because consumers keep asking for replays, and my 3 a.m. cron. [...] The pile has an economy on top of it. Svix exists so providers don’t have to build webhook delivery; Hookdeck exists so consumers don’t have to build webhook ingestion.

So here’s the thought experiment. What if instead of the provider telling us when there is new information, we ask the provider what new information it has for us since we last checked?

So it's a pull-strategy again.

Send Prefer: stream and the response never ends: each change arrives as it commits, over a connection you opened

Ok that's the strategy: an active connexion streaming the changes.

The draft is available at https://welidev.github.io/scroll/.
It pins down the feed, the cursors, the streaming and polling modes, the checkpoints, tombstones, and retention, and it marks the places where my own confidence is lowest.