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.

Kyria is a solid alternative. I was seduced away from it by the Piantor Pro and forgot about it, but the Halcyon Kyria looks perfect. I probably wouldn’t use those outer thumb keys much, but it doesn’t hurt they’re there, and there are plenty of more well-positioned thumb keys from which to choose.

I’d like more stagger on the body section than the birdy44 has, which looks like almost none; it has pinky stagger, but other than that no columnar stagger. The integrated track pads are lovely, though!

KLOR has the same thumb key positioning - the “m” key is too far in - you have to tuck your thumb to get it under your index, which is over the “m” key. It’s the same layout as the Piantor. I was hoping for a thumb cluster positioned more naturally under the resting thumb, with less horizontal thumb movement, like the ErgoDox (and siblings).

Gosh, yes, love that site. I don’t use it much since it’s almost impossible for it to stay comprehensive; for example, it’s missing both the Piantor and Piantor Pro, and the Piantor had been around for a couple years at least.

It is a wonderful tool, though. I think it’d be a full time job to keep it current with all commercially available keyboards, much less all of the bespoke builds.

Hah! I’m having trouble distinguishing between the Cantor and the Piantor Pro, which is what I’m currently using.

My issue with these is the thumb key placement. The innermost two are fine, but having to tuck my thumb almost into my palm to reach those outer (looking at the keyboards, or inner, if you look at each hand) keys is not very ergonomic for me. It’s also a fairly wide horizontal span to move the thumb, and sequences requiring inner:outer are both tedious and unavoidable.

I don’t doubt you like it; for me it’s not ideal.

Thanks for the suggestion!!

The Kyria is nice; that’s what I originally had my eye on. The stagger is right, and while some of those thumb keys are placed absurdly far in, there are enough further out to be useful. I do like the knob options, although I’d never use them.

You know, after I set my sights on the Piantor Pro, I completely forgot about the Kyria. I’m just now seeing the Halcyon series with a load of thumb keys! Frankly, more than I could use; I’m not facile with them and find dancing between layers with them to be challenging, but it does give my a lot of positions to use whichever is most comfortable.

I think that’s the winner.

This is great information. I really do like the look of the Keyboardio, and even have a tiny preference for fixed splay. It’s good to know they’ve fixed the switches;I think that’s what initially threw me off.

I almost got a Keyboardio. I was put off by reviews of the switches, or quality issues, or something.

Size doesn’t really matter; I wouldn’t use all of the keys, but I don’t care if they’re there. I don’t travel with my keyboard.

I’m mainly where I am because (a) I’m maxing my home row usage, (b) I try to eliminate anything that requires me to take my hands off the home row, and © I got sucked into the aesthetics of Chocs. A and B lead to an upper practical limit for the number of keys, so the keyboard size is a function of that and not because I’m trying to save space. C was just a mistake; yes, it’s slick, but I should have gotten full size switches, which would have allowed me to get higher tactility.

Those Keyboardios are very nice looking.

Oooo, that’s better! It’s a few keys short, for me; I need those missing 6. I’m already past my chording comfort level. Maybe a little more pinky stagger, too, but this would probably work.

Thanks, though! That’s the right direction.

The Voyager, like its bigger brother the ErgoDox has tepid stagger. They are the inspiration for this layout; I have the ErgoDox and like the thumb key placement.

Thanks for the suggestion!

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.

Ah. I was wondering where the “Hugo, but Rust” was.

I love these rewrites in other languages. They often learn from, and improve on, their predecessors in a way that having to maintain backwards compatability doesn’t allow.

Are those thumb keys not angled? Could you describe them, or sketch with Paint, or something? Because those thumb keys look angled.

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.

Naw, there are several good use cases for blockchain. Ask a blockchain hater how to implement an auditable change log, and they’ll re-invent blockchain and claim it’s not.

I’m only saying: you specifically mentioned Bitcoin, and then later said design goals included cryptocurrency integration. I’m not opposed to crypto, conceptually - I’m just giving a possible reason why you may be garnering downvotes.

Sure; I’m saying that there are trigger words that are guaranteed to generate negative comments: blockchain, crypto, crypto currency, and Bitcoin.

You said that you can’t understand the negative feedback. I’m giving you one reason why you might be seeing it. Lemmy and Mastodon (the AP FediVerse in general) is not cryptocurrency-friendly. If you mention “Bitcoin” in the post, you’re going to get brigaded. If someone sniffs around on the repo documentation and sees the crypto link, they’ll mention it in the comments and you’ll get brigaded.

I think there’s such a knee-jerk reaction to any mention of crypto currency, even in comparison, that even a whiff of a relationship generates negative reactions. As you say, much of it is based on no actual knowledge about the topic. It doesn’t help that there are some truly deplorable people associated with cryptocurrency, a great many bad actors, and proof-of-work was in retrospect a terrible design decision by Satoshi.

Blockchain isn’t cryptocurrency, and vice-versa, but most people can’t distinguish between the two. If there’s any mention of blockchain on the site, or especially if you mention bitcoin (as you did) you’re going to get crusaders.

Thank you, I’ll check them out.