I'm usually pretty pragmatic and not so much for cutesy names when it comes to coding, but I still like our tiny module that cares about cleaning the (HTML) body of scraped websites, called `shampoo` 😆

In Firefox’ developer tools, network tab, why are the response headers listed *before* the request headers? Because you are usually more interested in the server response? From a flow/timeline perspective, listing the request first, would make more sense, no?

🔖 “Add annotations, hereso unto for known as "Biscuits", to the end of the line of closing tags. Such Biscuits could include ids and/or class names. Make <div> soup digestible!”


Interesting, 73 includes a decoder: “WAMP-formatted WebSocket messages (JSON, MsgPack and CBOR) are now nicely decoded for inspection in the Network panel.” mozilla.org/en-US/firefox/73.0

🔖 HTTPX is a fully featured HTTP client for 3, which provides sync and async APIs, and support for both HTTP/1.1 and HTTP/2 — and breaks with some of (minor) quirks (python-httpx.org/compatibility)


I know, separation of concerns etc., but I replaced Templates with the much more flexible Jinja2 again. Good that these are (almost) first-class citizen in Django nowadays. 🐍

For a new front-end “app-like” project, is now the obvious and best choice, correct? Or :javascript: ? …nah

🔖 All you need to know about hyphenation in CSS | Clagnut by Richard Rutter clagnut.com/blog/2395