If Brontosaurus can make a comeback, so can Pluto!

I know you said this to me earlier today, but now I'm sitting down and letting this sink in. I don't love this.

I'm more than a bit sketched out that there's no reassurance and/or disclaimer about the Obsidian Web Viewer browser's security now that it's a *core* plugin.

That said, it looks and behaves great for general unsecured browsing. I've submitted some suggestions in the Features forums.

It's especially annoying because A. A. Milne passed in 1937 -- so his works entered the Canadian public domain in 2007. The US only got it in 2022 (at the same time as the Shepard illustrations).

This is due to their fixed-term-since-publication rules, applied to many materials published pre-1978.

(Apologies to anyone holding Desk as a surname!)

Obsidian. (Free license for individuals and non-profits.)

It includes the core plugin "Canvas," in which you can link to entire notes. I use it for linking to individual tasks within a larger process flowchart.

Obsidian also supports Mermaid diagrams, if that's your thing.

obsidian.md/canvas

I'm not opposed to using another static site builder, but I'd rather not add new services to the process - and GHP handles Jekyll for me when I'm away from my home computer.

End-to-end encryption on bsky.app makes sense to me, but how will communication between users on independent instances work?

Is this why more protocol work is needed?

And where can I learn more?

For existing file extensions, I think consistency is more important for access than knowing the origin of the letters.

I suspect we're moving away from extensions anyway. They're hidden by default in the common operating systems already, and could soon be fully replaced by non-filename metadata.

This reminds me of the origin of ISO for the "International Organization for Standardization" (as it is in English). Worth checking wiki for that rationale.