Secure Scuttlebutt is (was?) a protocol for high-latency communication between occasionally-networked humans. Pro: https://scuttlebutt.nz/; con (not read in detail): https://derctuo.github.io/notes/secure-scuttlebutt.html. I think it was supposed to be able to spread messages over Bluetooth, assuming a sufficiently connected web of nodes between person A and person B. Public keys were identities, and were bound to devices; unfortunately people may have multiple devices, or change devices over time, so this was a hindrance.
IPFS was supposed to be the Interplanetary File System. I think that was just because whatever pieces of content you ask for, you also cache, as part of the design: you keep a copy on the near side of the small high-latency pipe. But that's mostly about file transfer, not interactivity.
UUCP was definitely made in a time where a latency of days for delivery of email or netnews was common.
In the early days of CGI, the Web was just one way people imagined interacting with applications; another way was email. RFC 3834 has some recommendations for people who are going to automate email responses. There used to be services you could email a URL to, and receive the web page back as an email.
Using ed (in my experience) involves looking up the screen, or up the roll of paper on your teletype, to see what the lines of your file were, and imagine what they are now, given the changes you've wrought to them since they were printed, and then turn them into what they should be. With Mars rovers you have a simulation that you issue your command to, before sending it off to Mars. With correspondence chess you might keep a physical chessboard for each game you have going, and/or send a form back and forth that keeps track of several moves.
People used to do computation at universities and businesses by writing programs at their desks, submitting them to be typed on punchcards, and receiving printouts some time later. They would "desk check" their programs before sending them in, because each compute job took a couple days to come back.
I mention all these because, in an extreme censorship environment, any local state (session history on paper, an app on a smartphone, an odd device) might not be good to have around. So usability may require reducing the total amount of state that a command carries. The current working directory at the time a command is run changes the meaning and outcome of the command; you may not remember that directory in a day or two. The vocabulary and syntax of command-line switches are easy to look up in online manuals - but are there offline manuals? I don't know if this avenue of inquiry helps you, but it's interesting to think about for a moment.
I've been using a tshort dactyl manuform 4x6 for 5 years now, having never planned to use it for even 1 year. I only commonly use the two innermost thumb keys; I didn't think I would like the thumb cluster from watching a video of someone typing on it, and I indeed don't like the thumb cluster. The switches are Kailh Brown; one of them started to stutter and I replaced it with ... a TTC Brown or some such.
I've printed, but not finished, a Splaytyl. I think it's going to feel nice, but it's only 4x5, and I'm nervous about not having Tab and Enter on the base layer.
I have heard that there is some arrangement whereby you run FreeBSD on your hardware, with Linux in a bhyve virtual machine; you hand your physical wireless card into the VM, where LInux's drivers can talk with it; and route packets from the main system through it. -- Ah, https://blog.desdelinux.net/en/wifibox-the-project-that-allows-you-to-use-linux-wifi-drivers-in-freebsd/
To try to set up such a thing as your first entry into a BSD might be frustrating, but if you kept on until it worked, you would definitely have dived deep. (Dove? Doven? Diven?)
I'm a long-time Linux user now using FreeBSD on my home server. The first few times I looked at BSDs, they seemed old and stale, like nothing was happening there, and the coreutils were less comfortable to use because they were missing some switches. But what I've learned is that FreeBSD builds incrementally, without undermining itself, and my own understanding of it can do the same. What I've learned about previous versions of FreeBSD is more likely to still be true about the next version of FreeBSD.
BSD people often mention how the BSD in question is built as a whole, not cobbled together as a distribution. This difference can be stated far more quickly than it can be fully understood: like a culture, of which you gather a nuanced understanding from a broad survey of its literature, rather than a movement, whose goals are painted in broad strokes by a manifesto.
Anyway, welcome! My experience has been that #freebsd on libera.chat is more lively during US daytime hours than later at night. The Handbook is definitely your first documentation stop. ZFS, with its snapshots and replication, seems to be the most-hailed feature of FreeBSD; DTrace didn't even make the top 10, but when I didn't understand why NFSv4+Kerberos was failing, it was indispensable. Have fun!
CollapseOS used to emulate the Z80 using... libz80, i think it was called? lib6502 is also a thing.
Yeah, I did one for my Dactyl Manuform and just oversized it by a couple millimeters and stuck Amazon bubbly envelopes on the inside. The bottom of each half is flat, the same shape, and rubberized, so the covers just go over the top, I clap the bottoms together (tee hee?), and chunk the whole thing in a lunch bag that barely fits. It stays together without slipping and without any attachment between the two cover halves. Janky but it's worked for years.
I 3d-printed a hard box for my Fourier. https://gitlab.com/jaredjennings/fourier-box. (wince, there is no photo nor even an STL in that repository.) I wanted it to fit in my backpack with a laptop and books, so it holds the two halves side by side, not stacked. I had to print it in two pieces and friction-weld them together. That sounds fancy, but it just means you take a piece of filament, put it in a Dremel chuck, and draw on your model. Wherever you push down, the friction makes the end of the filament melt. Then I put on some Sci-Grip 4 (dichloromethane), which further solvent-welded the joint.
If you wanted to make one like this for your cepstrum, you'd need to do it in more pieces because that's larger than a Fourier. Your case would end up to be the size of a laptop. You might not want that.
They are made (I think) to be implementable - even, to give implementors some flexibility. Then everybody goes and buys a tool to do it, and not that well. I thought 15 years ago that security configuration was a (voluminous) subset of system configuration and system administration, ripe for automation and rigorous documentation - not something to pay a different vendor for. But the market says otherwise. When you can split some work across a whole team, or even into a separate company, instead of glomming it into one job, that's worth money to businesspeople.
The C128 has a Z80 too ;) I don't reckon there was an SX128 though
There are many ways to be more selective about from whom to accept email. SPF, DKIM, DMARC, and various blacklists are among them. They are supposed to make life harder for spammers. But they have also made running a mail server something that few dare to try anymore. Setup is not easy, but getting blacklisted is, and it causes silent delivery failure, and takes days of work to fix.
As a result, most of the email is run by Microsoft and Google. But that didn't stop phishers. They just go after people at smaller companies where security isn't as tight yet, and then they've got valid Microsoft accounts to send from. Liars and Outliers by Schneier is about this sort of dynamic.
As for PKI: If I may assume you to be, or have been, affiliated with an armed service -- Whose property is your CAC? And why did you use a pseudonym to make this post? (I mean to be pithy, not sarcastic.) I think Liars and Outliers by Schneier is all about this sort of thing - but I didn't get much of it read before it was due back at the library.
Uh, I think the Glove80 uses Choc switches, right? For heavy tactile in Choc you would want Burnt Orange. Not sure whether that's an option they provide or what.
Bastard Keyboards -- I've talked with Quentin and he seems like a cool guy. He's an innovator in the use of printed-circuit boards for keywell keyboards. That's important because it makes keywell keyboards much easier and quicker to make, without the huge cost associated with polyimide flexible PCBs. He has high quality standards, too, in my limited experience of his products.
I agree that you should get a keywell keyboard. I haven't read any specific reviews (I'm down the make-your-own rabbit hole instead), but I've seen some sentiment that the Glove80 is better than Kinesis' offerings, and I believe it's more programmable.
And about that last, if you "have to learn how to type again from scratch," you should use a key layout that will work best for you. This may not be a layout that already exists! Colemak and all its variants, for example, put A and R under your left ring and pinky finger. You might want K and J there instead. Or if it's easy to press the key your left ring and pinky are on, but hard to move them to a different key, you might be OK with A and R. Though Dvorak, for example, has left-handed and right-handed variants, I don't think there are any predefined layouts for people who want to type more letters with their right hand than their left -- or to be more likely to need to move fingers on their right hand more often than their left.
Carpalx is a body of work that lets you define the typing effort for each key, and finds an optimum key layout for you. I haven't used it myself - Colemak DH is a sufficiently high local maximum of goodness for me and I haven't gone down that hill to find a higher maximum yet. But the moment you're in may afford you a unique opportunity.
http://mkweb.bcgsc.ca/carpalx/?typing_effort
If you do end up making one, or having one made, you might be interested in something like the Concertina.
Sam Zeloof has made chips in his garage and posted a whole series about it on Youtube. He bought his silicon wafers, he didn't grow them, and his machines do take up the whole garage - but he did the whole thing himself. Fascinating viewing IMO. I don't know anything about where one would get these garnetty materials you mention, though.
I tried Emacs six times before liking it. The time it stuck was when I was editing some code in a language where the include/import statements almost matched the directory structure in the filesystem, but didn't. So, in Vim, I could cursor over an include statement, type gf... and not quite be able to instantly open up the included file. The way gf worked was that it was written in C as part of Vim, and to tell it where to look was a matter of configuration. But I needed a bit of code instead, to make up a couple of places in the filesystem to look on the fly, when I wanted to find-file-at-point (the Emacs term for Vim's gf functionality). Not only was find-file-at-point written in Elisp, but it already had a place where you could hook some custom code in, and documentation about how to do it. The documentation was available inside the editor (as you might expect from using Vim's :help), but it also had a link straight to the Elisp source. I was able to try out my function, change, and try again without restarting Emacs, and debug it step-by-step using edebug.
Anyway - have fun with Neovim. I hear it's spiffy. :)
i got paul through the flames! but he dies if you feed him too much
mmm yeah somewhere in the 20s. it gets way funnier after wordle :D
I haven't built a musical keyboard, but I've taken apart a home (electric) organ or two. I hear that one among the many options you have if a modern pipe organ is being made for you, is different strengths of magnets that initially impede your keypresses, like the pneumatic valves would if it weren't electronically controlled; as well as different woods for your keys. There's a channel on YouTube to which I'm subscribed where the guy is building his own tiny pipe organ (like, 30 pipes, the size of a large suitcase).
The hexagonal key layout mentioned by others, and also often seen on one side of an accordion, is one among several alternative musical keyboard layouts: the white and black keys are sort of a musical QWERTY. Not the best, but the largest installed base, the most likely for new people to learn, and the most likely to be attached to an arbitrary keyboard instrument you come upon.
I have a Folger Tech i3 2020, so named because its frame is made from 20x20mm aluminum extrusion. No bed levelling, no quiet steppers, no all metal hot end, five years old. I've added a part cooling fan whose nozzle I printed off Thingiverse, a janky ring of 24v LED lights, and a cheapo 0.6mm nozzle. Sometimes I have to print part of the first layer a couple of times and move the z end stop to get it right. It takes about 10 minutes every couple of months, so not a big deal.
I say this not to recommend this printer to you today, but to say that even if you don't manage to get perfect prints out of the box, the fiddling it takes to get what you want is probably not that bad.
Besides keyboards, and an occasional toy car or something, I've printed a replacement shade for a little fluorescent kitchen light, an adapter to fit a lampshade that was on sale to a lamp that was on sale, a fancy toilet paper spool, and a custom wrench to try to remove my washing machine's tub. Oh and brackets that hold my cell phone, so I can use my ergo keyboard to type at a terminal on my phone, broadcast my pirate signal, and hack into the Matrix, while riding the bus. :)
