• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle


  • I’ve got a Thinkpad 600X (Pentium III, 256MB RAM). I put Debian 12 on it, and the OS is not quite small enough. (NetBSD couldn’t drive my particular CardBus Wifi card, sadly, and 9front couldn’t drive the NeoMagic video properly.) Just Emacs on the console, no X, and eww for web browsing (to your question) and elpher for poking around Gemini. I’m not familiar enough with Thinkpads to know if that’s a useful data point for you.

    Nobody’s mentioned https://www.haiku-os.org/ yet, so I will. I can’t remember what happened with it on my Thinkpad. There are several graphical browsers there, with a range of capabilities, as well as a port of Emacs.

    I guess my real answer is: don’t handle today’s internet with all of its heavy websites? Use the web for documents, and use native applications rather than web apps for other purposes, such as chatting and email.




  • Use the Part Design workbench (you probably are already, but no one’s said it yet). Sketch a rectangle for the top of the whole tray, not the surface. Pad it down 40mm. Add a draft to set the angle of the sides. Use the thickness tool to dig out the middle of the top face - to a thickness of your exact choosing, which will be consistent everywhere. Now you have a trapezoidal bin.

    Then how do you make the separators. Um, draw a sketch with the tee on the inside bottom and pad it… and then the separators don’t reach the angled side walls. Oo, how about this: on the inside bottom, draw a sketch of the small square of material at the junction of the tee, and pad this tiny pillar up to the top of the tray. Then start a sketch on a side wall, External Geometry the near sides of the pillar in, and they’ll be projected onto the angled side wall. Then loft the two rectangles together. Yeah? Yeah? No. That didn’t work. The projection was normal to the angled wall, not to the side of the pillar.

    HAHAHA ok. Select a side of the pillar. Pad it, select Up to Face, and pick the angled inside . Presto!

    Then stick the lip on top and the grippy bit and that.

    I hope this was helpful and entertaining.



  • 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 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 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. :)