There are a lot more speech programs on Linux now. I was a bit curious and searched through the distribution package managers recently.

• Live Captions
• Linux Voice Control
• Speech Note
• Nerd Dictation
• Sherpa Speech
• Piper
• Numen

Some use Vosk or Onnx as runtimes.

I was told that it’s great that there’s lots of links here. Links are kind of a chore, but an obsessive habit (from academic times). There’s some semi automation happening but the main downsides are:

1. Checking if they still work
2. Checking if relevancy hasn’t changed

The other con || pro (take your pick):

3. Friends more in the know, may dissect && tear you a new one when the content and the link disagree (with reality).

Insanely knowledgeable people are also out there online too. On occasion, when I bother with emails, I always end up learning extremely fascinating stuff.

Jargon is strangely funny out of context. I have a crude setup that de-jargons and disambiguates stuff, which causes those of you much more knowledgeable than me to ??? occasionally.

• git clone - foolish person doppelganger?
• chromium - the metal?
• codium - drugs?
• terminals - airports?
• prompt - fast?
• posse - gangs?

Maybe the best kind of educational mischief looks just wrong enough to prompt an AI assisted investigation. I’ve surprisingly tricked quite a few people into understanding web feeds.

I know there’s a lot of interest in meshes (and alternative networks). I tried out a yggdrasil mesh for a good whole ten minutes or so some planets ago. I have notes running around somewhere in the (a)ether.

• GNUnet
• Zeronet
• Freenet/Hyphanet
• Invisible Internet
• The Onion Router
• Inter–Planetary File System
• WireGuard
• Yggdrasil
• Gemini

If I can hack a good intuition on networking this (new) year, I’ll perform my final pseudo disappearing act.

Contact forms are magical informants. Can you smell what kind of spam the spammers (and scammers) are cooking?

1. AI traffic/content farming services
2. Blockchain services
3. Coin recovery services
4. Guest posters for any of the above
5. Link sellers
6. Cloaking dealers
7. Cyber security spooks
8. Rich people asking us poor people for money
9. Visionary astrologers and foretellers

Incus is worth a look. It’s the fork of LXD, a container and vm orchestration/hypervisor program for cluster setups and infra models. Incus sits on top of the lower level LXC (Linux Containers).

• Incus Documentation: https://linuxcontainers.org/incus/docs/main/
• Incus Package Files: https://github.com/zabbly/incus#readme
• Incus Repository: https://github.com/lxc/incus#readme
• Incus Demo: https://linuxcontainers.org/incus/try-it/

Two newer meta-ish search engines for encyclopedias (about 30+ wikis):

• https://encyclosearch.org/
• https://encycloreader.org/

The best CSS Framework? I don’t know. Complexity moves in mysterious ways. The many interpretations soc model must be satisfied.

1. CSS in CSS (canonical)
2. CSS in HTML (write once and time driven)
3. CSS in JavaScript (framework driven)
4. CSS in Shadow DOM (company/department driven)
5. CSS in Scoped Formats (IDE driven)
6. CSS in Preprocessors (design system driven)

I’d say, choices reflect environmental factors (social or otherwise) at play. If you’re lucky enough to choose, then suitability favors what draws the finish line closer?

I’ve no advice since I’d rarely have the time/luxury to choose anyway. I’m usually thinking about the possibility of more types, sub–types (i.e in #1: bem, classless, etc), and the transposition strategy and speed between each class/type.

Mathematical Markup Language (MathML)? I’ve thought about LaTeX/TeX strategies on the web for a bit ever since someone asked years ago about different approaches. I never got to poking around on my blog, but since then the masters have delivered unto us;

1. MathML (XML based web specification)
2. KaTeX
3. MathJax

In format conversion land we’ve been given; LaTeXML, make4ht, texmath, temml, and Pandoc.

Some nix language gotchas I’ve experienced while using NixOS personally:

1. Avoid with expressions unless with the inherit keyword for identifying hidden attributes in scope.
2. Avoid the rec keyword unless there’s tracking/control of infinite set recursion (self naming/references).
3. Avoid importing more than 1 instance of <nixpkgs> for any evaluation chain unless there’s magic compute and “infinite” memory.

Tricky is numero three, but crucial for fast feedback regardless of the current thing? I don’t poke around as much to know anymore but; legacy, flakes, community, and possibly others.