The post structure evolves from blogging to structured content.

The idea to use topics is that "users with specific challenges have goals, not categories. They're trying to solve problems, not just browse topics."

Each topic pacck page includes: a brief introduction of 2 or 3 sentences explaining the challenge; "What you'll learn" bullets with clear outcomes, post list with short descriptions and links to other packs.

This pattern makes sense when there is 15+ posts covering related themes, readers ask "Where shoud I start", posts cluster around common challenges or you value helping readers find relevant content quickly.

Other approaches:

• chronological: you publish primarily news or updates
• no grouping when posts are completely independent
• there is less than 15 posts

1. Writing is good for you
2. You control the filter
3. Your blog is an asset

Translate it in french

Acessibility wurde hier betrachtet:

• alle Bilder mit Alt-Text
• korrekte Gliederung
• Formularfelder alle mit Label und Name
• <noscript> Hinweis wo er nötig war
• keine Cookies
• Kontraste geprüft
• Alternativtext für eine Grafik, die anstelle dieser eingeblendet wird

Some people care about it!

We can compute the amount of red, green and blue with the rgb() function. The same applies to color functions.

hsl() has limitations because the percieved color is not consistent accross hue, saturation and lightness values. That's why oklch comes in: it's a 2020 patch of the 1976 version of lch, that itself improves over hsl.

Also color-mix can be used in different color spaces. Transparency is available when two colors have a sum less than 100%, or mix one color with transparent.

In order to avoid repetition, custom functions is coming to CSS.

While some of what we looked at does require some setup — once it’s in place, we can create very robust systems, and, along with the static world of design software, it does beg the question if more design should be done directly in the browser.

#idea #project create the colors of a design system directly from the browser.

The permission system should handle folders and files.

Strategies:

1. (naive) read-time permission queries
2. A simple table (RBAC role based access control).

-- RBAC: Pre-computed permissions
-- access_type: 'owner' (full control), 'shared' (read only), 'path_only' (visible but no access)
CREATE TABLE permissions (
  user_id INTEGER NOT NULL,
  resource_id INTEGER NOT NULL,
  access_type TEXT NOT NULL,
  PRIMARY KEY (user_id, resource_id),
  FOREIGN KEY (user_id) REFERENCES users(id),
  FOREIGN KEY (resource_id) REFERENCES resources(id)
);

3. Attribute-Based Access Control

This approach is very clear and composable. It works great for single-resource access checks: "can user X access resource Y?" It struggles when listing resources, as we would need to execute the policies for each resource and can't directly query the resources table with simple filters.

4. Zanzibar and ReBAC

A 3D engine relying on HTML and CSS.

Compare tiny DNA to the tallest animal

A list of demos built with GSAP

Avec l'IA, l'ingénieur ne va plus dans un premier temps rechercher obligatoirement la solution, mais mettre en place le cadre, les outils, la surveillance, les docu­men­ta­tions, la chaîne de produc­tion et de livrai­son.
Dans un second temps, il va rester artisan. L’enjeu est de remon­ter partiel­le­ment la chaîne, se concen­trer sur ce qu’on veut produire, pourquoi, comment, et traduire le besoin.

La plupart des artisans purs vont alors se raréfier. "Il y a toujours des arti­sans potiers, céra­mistes et porce­lai­niers aujourd’­hui. Peu, mais il y en a. Ils répondent à des demandes diffé­rentes. Certains sont experts pour des demandes hors normes. D’autres, plus nombreux, visent des objec­tifs non utili­taires : le luxe, le tourisme, les cadeaux, les symboles, l’hé­ri­tage histo­rique, l’art."

Alors que deviendra l'artisanat logiciel?

Peut-être à des systèmes critiques où la confiance exige une main humaine. Peut-être à des créa­tions où l’in­ten­tion artis­tique prime sur l’ef­fi­ca­cité. Peut-être simple­ment au plai­sir de comprendre ce qu’on construit, ligne par ligne. Il y a un métier à trou­ver, ce ne sera pas tout à fait le même et il sera proba­ble­ment plus l’ex­cep­tion que la règle.

Coté développement, il y a toujours eu un énorme terrain de jeu hors professionnel avec l'open source.

Using text files. The expenses can be tracked with beancount. It tracks many in or out of many bank accounts with the "double-entry accounting".
Documents can be attached to transactions, etc...

The dataflow is the following:

1. Download transactions from the bank (csv, pdf or ofx files).
2. Convert these files to the beancount format. There are many plugins available.
3. Balance the transactions to get the "double-entry accounting"

In my experience so far, it has been the exact opposite. The entire process has never taken me more than 45 minutes to finish. Considering that I do this once a month, the time investment seems more than fair. And the added benefit is that by balancing these transactions by hand, I get a fairly good idea of what was happening in my accounts in the previous month.

Visualization can be made with SQL queries, or Fava as UI. See a demo

A feedback after 10 years of usage: https://sgoel.dev/posts/10-years-of-personal-finances-in-plain-text-files/

Kxd, Oppo, Vivo, Oscal, Blackview et Hotwav

Table of contents:

1. The internet is bad
2. The invention of the automobile
3. Tools for Conviviality & the industrialization of the Web
4. The Web we want
5. So where do we go from here?
6. Denouement

Illich’s thesis is that technology and its derived tools should serve people in a way that enhances their freedom, creativity, independence, and will.
The distillation of those principles on the web through manual code, hand-built social networks, and blogs, points luminously to one answer to the question of how the Internet can best serve humans:

1. Start small
2. Reduce friction to publish
3. Don't worry about design (unless you want to)
4. Use the IndieWeb
5. Join us in sharing what you've made

Le chat room accessible uniquement selon l'IP.

Côté technique, le site utilise des Server-Sent Events and a REST API.

via https://korben.info/ipchat-chat-ip-collegues.html