Deploy or die? Whenever deployment times are reduced to almost instantaneous — that meme comes to mind. There’s even a card game. How magnificent…

NetSurf is still the fastest GUI browser I’ve ever used. It supports stylesheets up to CSS2. This static micro blog renders poorly since it targets CSS3. Maybe some fallback CSS2 directives are in order.

Media clips and text on a screen are obtuse. If that’s consistently true, then choose your poison(s): misinterpretation, miscommunication, misdirection, misinformation, disinformation, dissimulation, and/or propaganda. Everyone gets to play, but no one is immune.

Browsers are on a slow march towards fully adopting user options for standardized/algorithmic color stylesheets. Great debates over what color to paint the bike shed (website) will eventually end. Paint it (mostly) whatever color you want.

In addition to the invert filter, another way of quickly bootstrapping a dark mode CSS stylesheet is to use Chromium’s auto dark mode emulation as an initial reference.

Web mentions and reply by email? The first is easy thanks to webmention.io, but the second is very involved and requires a public email inbox setup.

Fun fact: fetching favicons from various domains is a dark art. Might seem trivial at first, but it’s very complicated. A simple request for a favicon.ico will net strange returns — like serving a text file as a favicon.ico.

Better to leverage a browser which excels at interpreting favicons or contact a CDN of a major search engine. Make sure to cache the results.

• https://icons.duckduckgo.com/ip1/en.wikipedia.org.ico
• https://www.google.com/s2/favicons?domain=en.wikipedia.org

This static micro blog now “multiplexes” RSS feeds natively. The penalty (blood sacrifice) for making this happen is having to run hugo twice — once for it to write markdown and second to reflect it back for hugo to see what it wrote.

If I can win the error handling game, I’ll finally be able to add all my feeds and see how far hugo can be pushed.

If you don’t know which static site generator to use, choose one built in a language that you’re familiar with or want to learn. Under the hood they all use similiar constructs.

Chapter 2.

The sentiment that you cannot/don’t need to support all browsers is kinda accurate. In many scenarios you’ll never be able to support all browsers due to “business” constraints. Cross browser support is possible though.

But… let’s suppose that the only browser in “real” mainstream use is Chrome. It’s logical then to conclude that the only browser you need to develop for is Chrome, and that deduction works well for many companies.