There are currently multiple format of feeds: RSS 2.0 (and their old formats), Atom, JSON feed, Microformat h-feed.

The author describes the content-type for each, the absolute URLs norm in the feed and how to advertise them on web pages. Some good practices such as self link, cachine with Cache-Control, styling, feed titles and dates, conditional requests for the feed based on ETag or Last-Modified. WebSub seems to be an interesting standard. Bot access, categories, changing URLs, CORS and performance are also addressed.

Wow it's impressive.

An optimisation to make JSON as robust and easy to update as JOSONB, optimized for query and performant access to the data.

Un livre détaillant l'historique des langages de marquages.

AV1 is argued to be better on the web.

AVIF decodes a low-fidelity rendition befor the full image arrives for example. AVIF is considered slow to decode a 5456x3632 photographic image. 700ms for libjxl

At the time, JPEG XL was a much stronger contender for medium-high fidelity lossy image compression. AVIF now dominates the entire fidelity range, so JPEG XL's one real advantage has disappeared.

So AV1 and AVIF are better for the web, but "My current optimistic hope is that JXL takes off outside the web among professionals working with tools like the Adobe suite or alternatives, and camera manufacturers, smartphone OEMs, and others take notice and begin to think about JXL more seriously."

Head, Heading, Header, Headline

Why Base91? Because it’s a perfect fit for encrypted file names, producing strings that can be stored as valid files on Unix and macOS.

Base84 is the most efficient file name using the maximum amount of compatible characters.

The alphabet is: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789!#$%&'()+,-;=@[]^_{}~`

Franchement, la meilleure réponse aux intelligences artificielles (IA) et pour parler de l’«humanité des sites», c’est de continuer à faire des liens contextuels, dans les articles, vers des pages intéressantes.

En second lieu, c’est de proposer un blogroll de sites que l’on consulte dans la durée et qui nous stimulent.

It isn’t often that new image formats land in browsers. In the early 2000s we had JPEG, GIF, and PNG. The 2010s gave us WebP, which was a modest step up from JPEG. But the 2020s have given us two new image formats that are a big step up from previous formats: AVIF and JPEG XL.

What are the advantage of JPEG XL:

• progressive rendering (the whole image can render step by step)
• excels at lossless imagery and compression improvements

AVIF excels at web-quality photographic images and images with a mix of sharp edges and flat surfaces.

XCF has been GIMP’s primary project format since 1997, and it has served many users well. Over time however, we’ve observed more and more limitations of the binary XCF format. Among other issues, it does not easily support very large or complex projects, such as the multi-page and animation features currently planned for GIMP 3.6.

The new project file format will follow a more common “zipped XML” structure. While the technical details are still being designed and implemented, this change will allow for faster saving since we’ll only need to update parts of the file instead of the whole thing each time. It will also set the stage for much desired features such as auto-saving, which will now be much more feasible.

Non destructive layer masks are also a great feature. PSD support improvements.

The standard is available at https://www.itu.int/rec/T-REC-X.680/

It's used in many applications such as SNMP, CMIP, LSAP. Ididn't encounter a use case yet.

As stated in the video, the ASN.1 GNU library is under-documented and hard to use without examples. The idea, concept and design is well done though.

(via This is better than protobuf - Tsoding Daily)

First files are awesome, because the file format is the API to understand the content.

You may create a file in one app, but someone else can read it using another app.

After this introduction, an everything folder for social media is the theory: the folder would include everything you've created across different social apps. In that world, a “Tumblr post” or an “Instagram follow” are social file formats.

Bluesky, Leaflet, Tangled, Semble, and Wisp are some of the new open social apps built this way.

The author then details a typical social media post in JSON format, and how to store them as files. Domain names can be used to split each social media.

Then how to store a like with identity files (and the standard DID).

An example of such architecture is available at https://pdsls.dev/at://did:plc:fpruhuo22xkm5o7ttr2ktxdo

The apps then reacts to the change made in the social filesystem.

Exif can be useful instead of only be tagged as "privacy intrusive".

My rules of thumb
If you process pixels, normalize orientation first.
If you publish or store user images and want to preserve privacy, strip metadata intentionally.
If you parse metadata, treat it as untrusted input.
If you only need one tag, you can maybe parse one tag. If you need all the things, use a tool that has spent decades learning all the things.

C'est bien pratique pour manipuler un format plus simple que les vcards.

La version 2 rend l'uid optionel afin de suivre le format vCard

After JSON-LD, the working group announced a CBOR-LD.

It follows the JSON-LD philosophy of connecting and structuring data, but for CBOR https://json-ld.org/.

AVIF est à préférer. Le codec est plus performant que VP9 (dans WebP) et H.264 (dans JPEG). La qualité de l'image est aussi meilleure (gammes de coloeur, divers espaces colorimétriques) et sans redevance. Le support d'AVIF n'est pas encore optimal pour les navigateurs, mais atteint Baseline 2024.

WebP est au contraire établi, avec ou sans perte.

L'interface web de Pandoc pour convertir des documents