The author provides an history about the base, reset ,normalize and classless stylesheets.

The page itself is a demo of base.css, a classless stylesheet, and document itself.

Each topic is covered by a description, the rules and the relying css implementation. Each rule is well meant for accessibility such as "You should read a caption without having to scrol". It starts with the CSS Properties.

Use CSS properties for customization. There is the root style rules:

1. Set customization options on the the root element for all elements
2. Use native properties for font family and font size options.a
3. For font size, CSS has font relative units to create variations from the root or parent value.
4. For font family, it's useless to use custom property. Its value, a string value, can't create variations. Variation of font family would be by, if possible, using font variant alternates. a
5. Use custom property for line height. This maintains unitless value while creating automatic variations for blocks. b
6. Use custom property for pseudo content. This enables fallback trick for its native counterpart. c
7. Use custom property for the others due to lack of native properties. d
8. Prevent adjustments of font size orientation changes in iOS
9. Remove padding and margin, use box model of border box, and inherit color and font on all elements.

The library defines carefully the font-family, font-size, line-height, line-length, color, styles, blocks, mixes and phrases.

A font family declaration is a set of typefaces to create safer designs. Using multiple typefaces requires a sound knowledge of type pairings: space, type (sans, serif, cursive), wight, width, style normal and italic, cases: smalls, caps and smapp caps, roles: caption, body and display.

Font-sizes are defined with the em unit and relative calculations based on a --font-scale value.

The line height is computed based on the element around it. For example the paragraph following a hgroup with a heading. It creates a cohesive design.
All line height are derived from a --line-height value.

To respect the support of dark and light mode, developers must use the light-dark() function. Prefer human-based color mdoels such as LCH or OKLCH. The primary color component is Hue. Lightness and Chroma creates variations. Variations for one hue is a monochromatic pallete; for 2 hues is diadic; for 3 hues is triadic; and so on. CSS can programmatically create a live pallete from one hue using calc(). A 90deg deviation creates a complementary scheme; a type of diadic.

The web is filled with unsemantic styles: the absence of styles, the misuse of styles, the lack of unique styles. This can be seen through the lens of base stylesheets, as of writing.
All components — blocks, mixes, and phrases of media and forms — should have unique styles.

Blocks define region in the HTML document. Subsections uses one _ for each nesting level.

Mixes use all-round borders to define the boundary of their content

Phrases is all about content and forms. They are inline content, so their block content is maintained within a line height. Each phrase is clearly identified

Un retour des posts publié entre 1996 et 1998. Le web a tellement évolué depuis!

Publié le 17 juillet 1998.

A l'époque, la France limitait le chiffrement avec une clé de 40 bits, là où l'EFF avait cassé un chiffrement 56 bits avec une machine de 250 000$. Donc ce prototype de l'EFF cassait la clé de 40 bits en 3 secondes.

L'auteur recommandait

Bref, il est temps que les gouvernements se décident à autoriser un cryptage un rien plus costaud. Un cryptage à l’aide de clefs de 64 bits est déjà largement plus puissant. Évidement, cela ne résoudra pas le problème de l’état qui veut avoir un oeil sur tout.
Mais sérieusement, est-ce que les criminels en tout genre vont s’amuser à crypter en utilisant des outils légaux ? Non, ces mêmes criminels utilisent des clefs de 1024 bits ou même de 2048 bits (PGP est capable de coder avec une telle puissance et il est très simple à mettre en œuvre)."
Donc, le seul qui est gêné dans l’histoire c’est l’honnête citoyen qui désire simplement éviter que son patron, son provider, une tierce personne aille mettre un nez dans ses affaires

If markup is complicated, then the opposite of that complexity must be markdown

For developers, Markdown has long been the lingua franca of the tools we string together to accomplish our work.

But the truth is, most people today who make technology are actually still exceedingly normal, and quite generous. t’s just that they’ve been overshadowed by their bosses who are out of their minds and building rocket ships and siring hundreds of children and embracing overt white supremacy instead of making fun tools for helping you type text

Even AI uses markdown formatting under the hood.

It’s important for everyone to know that the Internet, and the tech industry, don’t run without the generosity and genius of regular people

The majority of the technical infrastructure of the Internet was created in this way. For free, often by people in academia, or as part of their regular work, with no promise of some big payday or getting a ton of credit.

10 reasons markdown won:

1. it had a great brand
2. it solved a real problem: too painful to write HTML, and a legible plain text is better
3. built on behaviors that already existed
4. mirrored RSS in its origin
5. there was a community ready to help
6. it had the right flavor for every different context, for example the Commonmark and Github-Flavored.
7. Released at a time of change in behaviors and habits: You can get people to change their behaviors when they’re using a new tool, or adopting a new technology.
8. Came right on the cusp of the build tool era: there were new at that day.
9. Worked with view source
10. Not encumbered in IP

The purpose of NetHistory is to give you a feeling for what it was like in the pioneering days of BITNET and the Internet.

Innovations and progress since 1500 per theme

Un métier particulier: archéologue spécialisé dans le paysage sonore. Cool nouvelle, on en veut plus comme celle-ci!

a project to excavate shut down, abandoned web ruins and restore them to surfable, visually accessible, searchable, remixable condition

somewhere between a library and a living museum, we're working on experimental new ways to close the gap between archival and visibility of the web that was lost

Pour le menu, plaçons le sur une page dédiée,

Pas con: si toutes les pages sont légères et mises en cache, alors la navigation sera tout aussi fluide. Le menu peut très bien être une page en lui-même.

Source of markup ghosts:

1. proprietary markup introduced by browser vendors
2. specs which didn*t see uptake like HTML3
3. use case specific markup on devices like WebTV or early smartphones

Some old tags:

• <audioscope> to display the sound over time. A demo https://www.youtube.com/watch?v=tM7YVhar2Dg
• <au> for authors
• <blackface> for double-weight boldface... in HTML 🤡
• <center> oh shit
• <font> and color attributes
• dingbat attribute to embed emojis, extended unicode entities, icon fonts and custom things. Now it is used as < for example and does not rely on the attribute anymore.
• <multicols> ....
• <person> in HTML 3, but it opens the door for so many other tags. Now instead we can rely on <a rel="author"> or with me

and more

Comment OpenOffice est devenu LibreOffice suite à un fork de la cokmunauté.