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é.

Old school GIFs put on website of the 2000