d13

Maybe unpopular opinion here, but I just read The Three Musketeers, and it's not even close to The Count of Monte Cristo.

The characters wildly change in tone and basic morals, the heroes are dirtbags, and the plot wanders.

I still enjoyed it, but it just wasn't the same.

“It is possible to commit no mistakes and still lose. You lost today Mr. La Forge, but that doesn't mean you have to like it."

Largely agree, with a couple exceptions: Undiscovered Country and First Contact are good; Into Darkness is bad.

This might be my biggest TNG complaint. The character and the actor are good (or at least decent if we're being picky), but almost every time the focus is on her, the writing is absolutely awful.

I wonder if they are preparing to stop using it. That could be a benign reason for the change in wording.

This doesn't exactly match your goals, but you may be able to adapt it or take pieces from it.

I have containers running on two subnets:

1. LAN + Tailscale
2. LAN only

Subnet 1 has a DNS server, which resolves all of my services to IPs on either subnet.

I have Tailscale set up on a machine as a subnet router (directing to Subnet 1).

Result:

1. When local, I can access all services on the LAN with local DNS entries, both Subnet 1 and 2.
2. When remote via Tailscale, I can access all services on Subnet 1 with the same local DNS entries. I cannot access services on Subnet 2.

This is nice because my apps don't care which network I'm on, they just use the same URL to connect. And the sensitive stuff (usually management tools) are not accessible remotely.

It's also ridiculously simple: Only one Tailscale service is running at home.

This does not solve your issue of broadcasting vs not broadcasting, though. There's probably other things missing as well. But maybe it's a start?

the AI that wrote the article

The linked article is by Dan Goodin from Ars Technica. He's not immune to mistakes, but he's been writing good articles about security for years.

Can we please not accuse everybody of being AI just because they made a mistake?

Logseq has an Android app and clients for the usual desktop platforms. It stores as .md files. It meets your requirements. I'm not sure why you're focused on Firefox support?

One I have my eye on is Silverbullet.md. the creator recently promoted it here and it has some nice ideas. It's a web app that you self host. Behind the scenes everything is stored in .md files.

Thanks for your answers! Very fair thoughts, particularly about the flexibility of keeping things as just files on disk.

Regarding the work thing, I should clarify my use case: I'd like to take work related notes that could contain privileged company data. With a standalone app, I can install it and manage the files on my device (with cloud syncing in an approved corporate way). I could still probably do that here, but it requires the work of running the web server locally. Unfortunately, an external source like a VPS wouldn't be allowed.

I have one more question, if you have some time: One of the things I like most about Logseq is that when there is a list of back links on a page, the context capture is excellent (likely due to it being an outliner). I've noticed that with SilverBullet, the context capture might begin/end in the middle of a word, etc. Is there a way to configure that or plans to enhance it?

This is very cool, and I've been watching the project for a month or so.

I like the query setup and the templates look very interesting. One of my biggest complaints about Logseq is how much of a pain simple query operations can be.

A few things make me hesitate a bit:

• I've been burned on single-dev passion projects in the past.
• As a self hosted web app, it's a bit more difficult to manage on a company owned machine. I know Electron apps get hate, but that would ease some pain here.
• The rapid pace of development is both exciting and worrisome. For example, a recent update completely changed the underlying templating engine from a well-known open source solution to a custom solution. I worry if I rely on this, something might catch me by surprise.

What are your thoughts on those concerns, OP?

So this whole post is an advertisement, then.

I did basically what you are trying to do:

I installed Calibre docker on my server machine with the DB local (important because the DB won't work over a share) and the book storage on the NAS.

Then I installed Calibre-web docker and pointed it to the same local DB and the same book storage on the NAS.

Now I can use Calibre for import, DRM removal, metadata updates, etc. And I use Calibre-web for user management, OPDS feed, etc.

Let me know if you want more info.