Using monospace fonts to design based on the ch unit.

Background: https://wickstrom.tech/2024-09-26-how-i-built-the-monospace-web.html

How to cache? It depends of the context: push vs pull and owned vs user.

Push means that the asset is pushed to a central server and then distributed.
Pull means the asset is referenced and the central server has to “pull” the content.
Owned means it’s owned by the central server.
User means it’s user-submitted content.

Push + owned

Make everything push + owned content if possible. "It turns out, however, that you can make a shit ton of other stuff push + owned if you try a little harder. "

How does the client check if they're expired?
Use “stale while re-validate”. Ur welc’

In summary:

• store asset
• use stale-while-re-validate access patterns
• should work offline

Push + User & Pull + Owned

Handle these with hash URLs. Hash the URL and treat it immutably.
Push + User: Forum comment -> hash URL
Pull + Owned: "in-content" assets. That’s where it’s user generated content, but not owned by the server.

Summary:

• Load asset
• Use infinite TTL + hashed URLs
• Should not re-fetch across page/app reloads

Pull + User

That’s where it’s user generated content, but not owned by the server. Posting gifs into the chat is a prime example; linking a blog post and generating a media upload for that is another.

Guess what: this pattern fits for highly dynamic user-generated content, which means it’s the content users link to each other in-platform.

Stable URL, short TTL. YES, SHORT TTL. [...] Debounce + throttle? Sure. Micro-TTL? Yes. Cache? Never.

CLI tools can make great things

Different definition of a UI component, from the minimalistic css one to the SSR full page.

gov.uk does not use jQuery anymore.

L'utilisation incessante JavaScript de pointe a contribué à rendre le web moins accessible, en affectant de manière disproportionnée les utilisateurs dont les appareils et les conditions de réseau sont incapables de télécharger les énormes charges utiles associées à ces frameworks et (2) de gérer la mémoire requise pour exécuter le code du framework dans le navigateur. L'accent mis sur la création d'applications hautement interactives entraîne une coupure d'accès au Web de certains internautes.

Pire encore, les personnes qui ont tendance à posséder des appareils moins puissants et celles qui vivent dans des zones où la connexion à l'internet est plus lente sont souvent celles qui pourraient bénéficier le plus d'un accès bien soutenu au web (par exemple, pour accéder aux services gouvernementaux).

We simply have to recognize 3 things:

1. First, if we do not continue to work to change the Internet, we really will have only two choices: the corporate salad or nothing.
2. Second, the control of the Internet is ultimately in our hands, [... corporations] do not have the power to lock down the Internet to prevent us from going wherever we like, unless we believe their lie that our only two options are to eat their salad or leave.
3. Third, each of us must banish the idea from his mind that he has failed if he creates a website and millions of people don't flock to it. That is corporate thinking, and it has no place on the small web.

Ideally, a personal website should be thought of as a gift to all Internet users.

Corporate search engines will almost never take you to a personal website unless you are either very lucky or you already know it exists. If you already know a website exists, you don't need a search engine to find it. This means only those who are motivated and know how to look will find what they are looking for on the small Internet.

It has a links to specific search engines.

For those who are not technically inclined, sites like these make starting your first blog easy: Bear Blog (free), Nekoweb (free), Mataroa (free or $9/yr for premium), and Write.as ($6/month).

IP and names in URLs can change. They will over time.

HTML mit custom components to load partial templates.
CSS with imports is max two level deeps: one main that has all the imports. Variables, selector nesting and vendor prefixing are now fine.
Design token with https://open-props.style/

Javascript can be imported with <script src="" type="module"> tags.

At the beginning of the century, people played around and gave all kinds of things URIs like "http://example.com/foo.rdf#color".

for one reason or another people demanded the right to be able to use http://example.net/people/Pat to denote Pat rather than a web page about Pat.

The term Resource is indeed enough for REST, but other use cases such as RDF already reserved Resource for something different.

in fact in RDF the resource was allowed to be anything at all. A class, rdf:Resource even used the term as the universal class of all things.

IndieWeb for tech savvy and developers. A technical knowledge is needed.

Indie Web refers to the non-corporate or non-commercial web.

We could find better names: "human web" or the "people net".

There are initiatives derived from the IndieWeb: The Slow Web, The Smol Web.

Webize 😃

Another hypermedia framework

Not sure Tim Berners-Lee’s vision was to have 148 requests transfer 5.3 MB of assets to deliver 15 KB of text

Independant websites are still there. Since Twitter lose users, more independant websites are rising. Other simply remains. The article provide some ezample.

Du ressenti du web des années 90 à maintenant

Web 3 for Read, Write, Own...

If the platform or service dies, you don't own it anymore. The same occurs when a platform can steal.

The author outlines https://mirror.xyz/ as an example. I didn't get into it yet.

Self-hosting is web3 at the end.