None necessary, but thanks.

Lamenting that a phone or tablet can’t use zwave for networking is really strange.

It would be, if anyone were doing that.

So Thread is a low-power radio, and Matter is the protocol? Does it is the same frequency ranges - 2.4 and 5 GHz? Or does it have a different spectrum? One of the reasons I chose zwave initially was because the standard allows far more devices in the spectrum than ZigBee, and WiFi crowding is already an issue with only all of the phones, tablets, computers, and devices that I couldn’t get in zwave.

I also have the prompt set to the host name. I’ve never understood why people included their usernames; I don’t log in to more than one account on each machine.

How are the battery lives of your devices? I have motion sensors throughout my house connected via zwave, and I replace their button batteries about every 18 months. Does Matter run over a low energy technology?

As long as it isn’t github.

Publish that puppy. It can’t hurt.

Don’t do it in github, though. Sourcehut is better; or if you crave that cluttered, JS-heavy feel, Gitlab.

Maybe! How is it better than keeping a README?

If it’s just a command, I put it in a readme. If it’s a series of commands, I put it in a shell script. What would your tool bring to the party, and if I’m going to turn to a third party solution, why shouldn’t I use Salt or Puppet instead?

Harder to encrypt though, so I question “more secure.”

We started with plain text. Then everything got more complicated, and everything came with its own incrutable DB. Now we’ve come full circle: todo.txt, calendar.txt, plain text markup documents^[1].

Some things don’t need to be more complex than they are.

If you do, use the -k option - it locks access to the rook service to only the user session. Rook works without it, but is more secure with it.

Have you ever used OwnCloud, before the fork?

I hated administrating OwnCloud, and that’s kept me away from NextCloud. OwnCloud was a big, resource hogging, hot mess; did NextCloud do a huge refactor and clean it up?

Shamelessly shilling my OSS project, rook. It provides a secret-server-ish headless tool backed by a KeePass DB.

• Headless server
• Optional and convenient integration with the kernel keyring (on Linux), for locking the server to only provide secrets to the user’s session
• Provides a range of search, list, and get commands
• Minimal dependencies and small code base make rook reasonably auditable

You might be interested in rook if you’re a KeePassXC user. Why might you want this instead of:

• Gnome secret-server, KDEs wallet, or pass? rook uses your (a) KeePass DB, while most other projects store secrets in their own DBs and require (usually manual) sync’ing when passwords change.
• One of the browser secret storage? Those also keep a bespoke DB which needs to be synced, and they’re limited to browser use. Rook supports using secrets in cron jobs or on the command line (e.g. mbsync, vdirsyncer, msmtp, etc, etc).
• KeePassXC? KeePassXC does provide a secret service that mocks Gnome secret-service, but you have to keep KeePassXC (a GUI app) running even if you only rarely use the UI. Rook can also be used on a headless machine.
• The KeePassXC command line tool? That requires entering the password for every request, making it tedious to use and impractical for automated, periodic jobs.

Rook is read-only, and intended to be complementary to KeePassXC. The KeePassXC command line tools are just fine for editing, where providing a password for every action is acceptable, and of course the GUI is quite nice for CRUD.

Or maintain a repos. Which would force people to create an account on one of the free VCS servers, pay for an account on a non-free one, or run their own.

Did you look at Pelican?

I have not, but I will. I may also look at Zola, although it, too, appears at the surface level to be tightly coupled with markdown.

the template language is buggy and inscrutable

It’s just Go templates, which are pretty solid; I’d be surprised by any bugs, unless they’re in the Hugo short codes. The syntax is challenging, even if you’re a Go developer and use it all the time. It’s a bespoke DSL, and a pretty awful one: it’s verbose, obtuse, and makes some common things hard.

Go is my language of choice, but my faith gets shaky whenever I have to use templates.

I’m not a huge fan of Python; despite its popularity, it’s got a lot of problems, not least of which is the whole Python 2/3 fiasco; which, years later, is still plaguing us. However, if I can containerized it so it isn’t constantly breaking in the background when I do a system update, I’m not opposed to using a project written in it. At least it isn’t Node; I won’t let that crap onto any server I admin.

Edit: Zola has the same problem as Hugo.

Ah, Ok.

I do as (or a similar workflow): I rsync the content directory and let Hugo on the server render. My sites are public, but perhaps they’re just much smaller or not as popular; Hugo renders even my largest site in about a second, but for a large, slow, heavy-use production situation I could see a push-and-swap process for a more atomic site update.

I don’t see the degradation you do, but there are so many possible variables.

My biggest gripe about Hugo is how limited it is in supporting source document formats. There’s no mechanism for hooking in different formats, and the team is reluctant to merge PRs for other formats. When I started with Hugo, I had a large repository of essays spanning a decade and written in a variety of markup, from asciidoc (which I used for years), to reST, to markdown; and markdown is by far the worst. I was faced with converting everything to markdown, which was usually a lossy process because markdown is so limited, or not publishing all of that history. And now we have djot, which is almost the perfect plain text markup language, but I again have to first do a lossy conversion to markdown to get Hugo to consume it. It low-key sucks, and I’m actively looking for an alternative that has a more flexible AST-based model for which new formats can be added; something that consumes a format like pandoc’s AST.

Hugo has a watch mode, right? It should rebuild if it detects changes.

Good choice. I’ve been running Radicale for years, reverse proxied behind Caddy, and it’s been solid.

Very probable! When replying, my client only lets me see the comment I’m replying to, so losing track of who said what is a common problem for me. I assumed you were OP because I didn’t think anyone else was advocating for Plebbit.

This is the way.

I will say, Jellyfin’s aggressive transcoding has brought even my relatively modern, 12-core AMD to its knees, but for everything else, more RAM has been more important than CPU or GPU specs for self-hosting. Before Jellyfin, I hosted the entire house on an ARM-based micro.

That said, the game changes if OP wants to do any LLM stuff. Memory is still important, but the GPU starts to play a bigger role.

If I could know only one stat for making a decision, though, it’d be RAM.