This is exactly what I think of a great design system color handling.

The heart is the mapping of semantic CSS colors to modifiers, and thethey can be slapped on every components.

There is always color definitions, then semantic colors such as --color-primary-muted, --color-primary-vivid and then css variables used by the components.

A generator is available as snippet on https://codepen.io/cferdinandi/pen/dPojzmN

Diffusé via de la publicité malveillante redirigeant sur un faux site de KeePass afin de déchiffrer les mots de passes.

Pour chaque degré, la production alimentaire diminuera de 4.4% par personne. Les zones impactées sont inégales.

Venn Diagram of stoners, D&D players, bank robbers and movie directors

A classic image with text in it looks like this: "[image]".

Meanwhile, alt text convey the information: "[description of image including the text]"

Malgré une miniature aguicheuse, le contenu est pertinent et instructif.

La ministre des affaires numériques danoises

Cette réalité, c'est que toutes les administrations américaines ont le pouvoir de déconnecter n'importe quel individu, entreprise ou gouvernement étranger de l'infrastructure numérique fournie par les grandes entreprises américaines. En ce sens, il est donc inutile de blâmer Microsoft pour le pouvoir de sanction dont est investi le Bureau ovale. Mais nous pouvons certainement lui reprocher d'avoir enfumé l'Europe sur les risques.

Cela ne signifie pas qu'il faille se couper de toute technologie américaine, mais cela signifie qu'il faut rejeter tous les services qui peuvent être désactivés à partir de Washington.

Cela intervient avec la mise à jour forcée de Windows 10 vers 11 avec la fin de sa maintenance.

À la maison, j’ai décidé de chuchoter pour m’adresser à mon mari. Surpris, il m’a demandé pourquoi je parlais en chuchotant.

• Pour ne plus être espionnée par Google!

Mon mari a rigolé.
Alexa a rigolé
Siri a rigolé
Mon frigo a rigolé

4 plugins: Web Clipper, Sync, Bases and Maps.

• Avoid splitting content into multiple vaults.
• Avoid folders for organization.
• Avoid non-standard Markdown.
• Always pluralize categories and tags.
• Use internal links profusely.
• Use YYYY-MM-DD dates everywhere.
• Use the 7-point scale for ratings.
• Keep a single to-do list per week.

Very few folders. Navigation works with the quick switcher, backlinks or links within a note.
The categories group mainly the notes together.

There are two folders though: references about things that exist ouside in the world (books, movies, places, people).
Clippings (as a kind of Shaarli).
There are also three admin folders that don't show up in the navigation: attachments, daily (used as reference), templates.

Two folders are downloadable (and shared with the public): Categories and notes

Notes are linked as much as possible, even if the link does not exist yet. It's similar to a wiki.

Common properties in templates:

• Dates — created, start, end, published
• People — author, director, artist, cast, host, guests
• Themes — grouping by genre, type, topic, related notes
• Locations — neighborhood, city, coordinates
• Ratings — more on this below

Few rules:

• Property names and values should aim to be reusable across categories.
• templates are composable: they can be added one with another.
• short property names are better
• default to list instead of text is there any chance it might contain more than one link or value in the future. See https://github.com/kepano/kepano-obsidian/blob/main/.obsidian/types.json

The author has a separate vault for his own site.

Mon résultat: 6 tonnes de CO2, 5700 litres d'eau par jour.

the many ways AI is making humans less productive #1:

• I have to prove I am human when visiting website
• websites are generally slower because they need to check if my browser is an AI bot
• I spent time every week now, restarting services affected by AI scraping bots

And I am not even using AI

La fleur de Lys est une banane épluchée

All I see so far is this will need more computation or battery drain for this.

The library is available at https://github.com/Specy/liquid-glass

IPv6 needs to be better deployed and supported everywhere.

1) You don't "upgrade" to IPv6, you offer it inline with IPv4. It has never been a forklift replacement (there is another rule about this).

2) I have worked for numerous ISPs over the years, big and small. Way more than three I can tell you, and the small ones are almost always the ones pushing IPv6 hardest, because CGNAT is fucking expensive. The big ISPs are the ones who are ignoring it. I've only worked for one small ISP that was opposed to it, and their attitude changed when they ran out of IPv4 space, and saw their choices. CGNAT or buy more space on the open market.

[...]

"Le seul comparateur indépendant de primes énergie"