Daily Shaarli

All links of one day in a single page.

March 8, 2026

Tinder, WeWard, Leboncoin… Matignon teste de nouveaux outils contre l’abstention

Je ne sais pas si c'est sain, de promouvoir les élections de cette manière. Cela ressemble à de la manipulation.
Où est l'éducation civique et l'engagement ?

Quelques applications concernées: WeWard, Tinder, Leboncoin, Blablacar, Lime, Bolt, ou encore sur la chaîne des musiques urbaines Trace TV.

« Mais depuis plusieurs années, la parole institutionnelle a du mal à passer, constate Michaël Nathan »

Ah bien! Mais utiliser ce genre de partenariat pour la vie publique semble toujours malsain... Pourquoi la parole institutionnelle a du mal à passer d'abord ?

Ce qui me travaille est surtout que l'État dépense pour ces communications, alors que cela devrait fonctionner normalement.

Ben Royce 🇺🇦 🇸🇩: "This video was released by #Fo…" - Mastodon

This video was released by #Forbrukerrådet, the Norwegian #Consumer Council, a few days ago. It imagines the career trajectory of an "enshittificator"

It was hard for him to enshittify minor aspects of daily life in person, but became easy for him to do so at scale once he embraced the #Internet and #technology

"Just doing things" is not a path to value (Don't Just Do Things, Part 1)
  1. doing design requires that you first establish an environment in which design is possible and valuable.
  2. [doing design means following a design process. While it is possible to produce outputs that resemble design artifacts without practicing the process, you are not designing as such.

Because Meta ordered employees to become 5x more productive, without the last bit of a clue about how that might be achieved. There will be supply-side outputs: flooding the information environment with emails and summaries, solving attracting problems regardless of their value to the customer, juicing metrics that show users like the product, fulfilling feature requests without value, prioritizing improvements that show up on the dashboard.

So do the right thing.

µJS — Lightweight AJAX Navigation Library

Another one

Laws of UX

I really enjoy the examples provided on the page.

Fitts's Law

The time required to move to a target is a function of the target's size and distance from the starting point.

The target such as buttons must be bigger.

HIck's law:

The time it takes to make a decision increases with the number and complexity of choices.

Miller's law:

The average person can hold about 7 (plus or minus 2) items in working memory at any given time

Format the informations correctly (Phone, Card, Social, Serial, Currency)

Doherty Threshold:

Productivity soars when a computer and its users interact at a pace that ensures neither has to wait on the other. The threshold is 400 milliseconds.

I would say "instant" is reach under 200ms

Postel's law:

Be conservative in what you send, be liberal in what you accept.6

The more formats you accept, the less friction people experience. Validate generously, format strictly.

Zippopotamus- Zip Code Galore

Provide the city and more informations based on the ZIP code and the country.

ZIP Code First

Country -> Zip -> ...

Autocompletes the user input to avoid errors.

  • Use inputmode="numeric" for a ZIP code
  • work with autofill and its autocomplete attributes: postal-code, address-line1, country
  • country first in case of international addresses

See the service for it: https://api.zippopotam.us/

If It Quacks Like a Package Manager | Andrew Nesbitt

Every time a tool has transitive dependencies, it got:

  • Reproducibility. The tree can resolve differently each time, so you need a lockfile to record what you got.
  • Supply chain amplification. A single compromised package deep in the tree can cascade outward through every project that depends on it.
  • Override and exclusion. Users need mechanisms to deal with transitive dependencies they didn’t choose and don’t want.
  • Mutable references. Version tags that can be moved, rewritten, or force-pushed mean the same identifier can point at different code tomorrow.
  • Full-tree pinning. Pinning your direct dependencies means nothing if their dependencies use mutable references.
  • Integrity verification. You need to know that what you’re running today is the same thing you ran yesterday.