jaredj

Yeah, a flat keyboard will generally beat a keywell keyboard for portability, I suppose. For my current Dactyl Manuform, I printed a hard case that covers each half, and then I set them together bottom-to-bottom and put the whole thing in a bag that happens to be just tight enough. When I put that in my backpack, it's like a large plastic stone. Not flat. Works well enough for me though.

The Glove80 is keywell-shaped, and is a product. https://bastardkb.com/ has fine Manuform-thumb-cluster keyboards.

I have printed a Dactyl Manuform; its thumb cluster has six keys, but is quite different from the Kinesis, I'm afraid. I think the original Dactyl was an attempt at making a more portable Kinesis Advantage. I guess you can maybe generate a Dactyl design at https://ryanis.cool/dactyl/ ?

I'm afraid my advice is a few years old because I haven't kept up. The Dactyl Manuform was supposed to be a stopgap, but it's worked well enough that my focus has drifted to other projects.

See also kbd.news if you haven't before. I used to think, why is this dude making his own website when everybody's already on r/mk? ... And then Reddit sold out.

https://contentauthenticity.org/how-it-works

The page is very light on technical detail, but I think this is a system like trusted platform modules (TPMs), where there is a hardware root of trust in the camera holding the private key of an attestation certificate signed by the manufacturer at the time of manufacture, and it signs the pictures it takes. The consortium is eager for people to take this up ("open-source software!") and support showing and appending to provenance data in their software. The more people do so, the more valuable the special content-authenticating cameras become.

But TPMs on PCs have not been without vulnerabilities. I seem to recall that some manufacturers used a default or example private key for their CA certificates, or something. Vulnerabilities in the firmware of a content-authenticating camera could be used to jailbreak it and make it sign arbitrary pictures. And, unless the CAI is so completely successful that every cell phone authenticates its pictures (which means we all pay rent to the C2PA), some of the most important images will always be unauthenticated under this scheme.

And the entire scheme of trusted computing relies on wresting ultimate control of a computing device from its owner. That's how other parties can trust the device without trusting the user. It can be guaranteed that there are things the device will not do, even if the user wants it to. This extends the dominance of existing power structures down into the every-day use of the device. What is not permitted, the device will make impossible. And governments may compel the manufacturer to do one thing or another. See "The coming war on general computation," Cory Doctorow, 28c3.

What if your camera refused to take any pictures as long as it's located in Gaza? Or what if spies inserted code into a compulsory firmware update that would cause a camera with a certain serial number to recognize certain faces and edit those people out of pictures that it takes, before it signs them as being super-authentic?

60% silent? Relative to wha... oh

My ergo journey started with similar requirements to yours - specifically including the Y and B keys. Along the way, I learned how important layers are for comfort, ditched QWERTY entirely for Colemak DH, bought a 3D printer, and ended up at 40%. Several years ago, there was a term "1KFH" ("one key from home") people used to describe the amazing amount of comfort they found when they never had to move their fingers more than one key away from home position, nor to move their hands.

I'm not saying you have to change your requirements, now or ever, but I think people who start to make their own ergo keyboards may be subject to this sort of requirements drift, such that if they ever make it to the product phase, their products aren't what they initially expected to be building. And maybe this sort of dynamic is what makes it less likely for the product you are looking for to have been built already.

Michael W. Lucas just released a book on how to do this. I've begun but not finished it. https://www.tiltedwindmillpress.com/product/ryoms-ebook/

It took me a couple months to stop thinking about layers.

My first move toward ergonomics was a Keebio Fourier 40%. It had been a few months before that when I started using Colemak on my laptop keyboard; I did that using Windows keyboard settings, and I was taking notes in meetings, so whenever I couldn't keep up, switching back to QWERTY was a hotkey away.

After switching to the Fourier, and iterating many times on the QMK settings, that was the month or two where I had to think through all the control keys, symbols, and function keys I was typing. I didn't quit typing on other keyboards, although I typed on my Fourier as much as possible; and I have not ended up forgetting anything I learned before.

I'm now on the precipice of moving from a 4x6 Dactyl Manuform to a 4x5 Splaytyl (if I can find those dang parts and get the thing built!) and that's too small to have things like Tab, Enter, or the backslash on the home layer. I'm nervous. I've tried making a 4x5 layout for the DM, but haven't ended up sticking with it. I couldn't really get used to keys that are physically there, not doing anything.

Marvellous!

history which may or may not be relevant to you: https://en.wikipedia.org/wiki/Cryptocat

A name I've seen in connection with this issue is Obtainium. From a cursory look, it appears this just streamlines checking for and getting apk's from GitHub release pages and other project-specific sources, rather than adding any trust. So maybe it just greases the slippery slope :)

Security guidelines for mobile phones, and therefore policies enforced by large organizations (think Bring-Your-Own-Device), are likely to say that one may only install apps from the platform-provided official source, such as the Play Store for Android or the Apple App Store for iOS. You might say it's an institutionalized form of "put[ting] too much trust in claims of authority." Or you might say that it's a formal cession of the job of establishing software trustworthiness to the platform vendors, at the mere expense of agency for users on those platforms.

People are not taught how to verify the authenticity and legitimacy of software

Rant: Mobile computing as we know it is founded on the rounding off of the rough corner of user agency, in order to reduce the amount users need to know in order to be successful, and to provide the assurances other players need, such as device vendors, employers, banks, advertisers, governments, and copyright holders. See The Coming War on General Computation, Cory Doctorow, 2011. Within such a framework, the user is not a trustworthy party, so the user's opinion of authenticity and legitimacy, however well informed, doesn't matter.

No, I have not tried that. But I might now. :)

Oh! Oh yeah, that's what I meant, sorry