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.

mango jelly solutions videos. Nothing specific about Solidworks there, just good tutorials.

CollapseOS used to emulate the Z80 using... libz80, i think it was called? lib6502 is also a thing.

Sure, go ahead :)

The Gemini capsule is yet to be done, but the wallpapers are available at https://j.agrue.info/wallpapers/

This post inspired me to go find the tiling wallpapers I made 20 years ago. I almost made a pull request about it, but then decided not to, because it's GitHub. My wallpapers used to be on my own website, and now I'm going to make a Gemini capsule and put them up on 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

Oh, like refusing to parse $5. That would be good. Thanks for looking!

Uhhmmmm... "sold for 00"? What part of the software in between this headline and my browser is parsing $5 (which clearly has no value at that moment), and why is it working on input it isn't intended to? What variables would exist and be interpolated into the title if they were to happen in a post title? Is this a known issue? An issue with the bot? An issue with Lemmy?

Do people get messages when you @ them? @krogoth@infosec.pub @jerry@infosec.pub @shellsharks@infosec.pub I don't want to report this post - it's a fine post - but I do want infosec.pub to be safe and secure.

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 what units does that measure in