I keep reading that WSL2 uses 9p, but that's not _exposed_ anywhere, right?

I'm starting to think the person who handed me a bread bowl for this wasn't a doctor.

I've often wished I could find back-references and search my bookmarks as if they were part of my Obsidian database. This would help with that.

I keep bookmarks as a Markdown file so I can sync it using Syncthing. I use either Obsidian or KRunner (desktop-only, similar to mac's Spotlight) to open bookmarks. It's been working well enough for me.

The KRunner plugin I use doesn't have a comprehensive Markdown parser, but it works great with the format I've been using. https://github.com/andrewrabert/krunner-markdown-bookmarks Ex:

  # Bookmarks
  ## Code
  - [GitHub](https://github.com)
  - [GitLab - Arch Linux](https://gitlab.archlinux.org)
  ## Social
  - [Hacker News](https://news.ycombinator.com)
  - [Reddit](https://www.reddit.com)

It would be cool to have an Obsidian plugin which retrieved favicons for the links.

Rust had something similar: https://github.com/rust-lang/rust/issues/13871

I'm not sure about proxmox, but ZFS on Linux does have encryption.

The policy(?) change came ever since "SSL added and removed here ;-)", right?

That's when I remember seeing a broader shift towards app-terminated TLS.

Does this page not work with middle-click scrolling for anyone else?

Looks like that may have been caught in the crossfire when they blocked right-clicking.

>when they blocked right-clicking

Which is a stupid thing to do.

Especially since it's free to redistribute with attribution.

A barrel roll or an aileron roll? Most people call an aileron roll a barrel roll (no thanks to Star Fox)

Can you elaborate?

It's open source. You can be pretty much 100% sure that they won't do a bait & switch.

Not strictly relevant, but:

I've yet to see tools that handle zero-downtime-migrations well. The manual task of keeping two versions of the same query / model alive (version N and version N+1) is... well, how else would you handle it?

While tools that can generate the model or schema are nice, they never seem to account for this.

Is there some alternative approach I'm missing?

Have your query as a function in the database. BEGIN, do the migration, replace the function, COMMIT. Postgres DDL is transactional so at no point does the function stop working.