@hairylarry they didn't move to the orange screens until the Kaypro 16/2 if i recall correctly (the first that could run msdos) - the II, 4,and 10 all had the green screens and ran CP/M
I've been uploading selections from my Public Domain collection to Peertube.
You can see them here https://peertube.mastodon.host/videos/search?search=ajroach42
I'm going to upload a few more things that don't fit in to my podcasts (old sitcoms mostly) and then call it a day for now.
I might talk a little bit about some of the things I've uploaded, and stuff in a minute.
the question is not "can i afford to have a probably not-fully-functional kaypro taking up space"
the question is "can i afford not to"
could fit a cluster of raspi in the space of one of those floppy drives
If you're into working with humans, free software & cryptography, and you love the idea of helping news organizations break their biggest stories based on submissions by whistleblowers, you may want to come work with me! New opening at Freedom of the Press Foundation just went up - boosts appreciated:
I wrote the first program I ever got paid for on a Kaypro II. Show more
It was a newspaper route manager that handled printing route maps (for substitute drivers) and all the appropriate invoices/receipts for each customer each week for a motor route of up to 5,000 customer addresses.
It was written in QBASIC for our newspaper delivery person for $100. I know, it sounds pricey, but it replaced the delivery driver handwriting out bills and receipts on carbon paper triplicate every week, so they considered it paid off after the first print run, and that was what they offered to pay me to do it.
They sold ten more copies of it to other local drivers for $100 each and gave me $50 of it, so I ended up with $600 and a realization that I saw things differently than lots of other people out of it.
I added a link to this story feature to Collab.
The Sun Went Down As the Sun Went Up
The Feather That Fell In Love with a Turtle Dove
@hairylarry Good on you :)
There's lots of us CS folks here in the fediverse, and in niu.moe in particular but most of them green between the ears, and could use a dose of history now and again. It's hard to express how valuable it is having a few old wizards around :)
It's called Graceful Recovery.
When an error happens it can crash your program. That's not graceful.
You can trap or preempt the error and figure out the best way to report the error and continue the program.
That's Graceful Recovery.
On Collab during development I would open a file to read or die. If the file didn't exist program execution halted.
So I have been adding code to check for the file's existence before I open it. If it's not there I post an error message and continue.
i hate all code written by other people, especially the worst person of them all, Me From The Past
I don't think we've settled for ease of use as much as we've settled on "increased engagement"... How to keep peoples eyeballs glued to your product.
Gopher is very easy to use, more so than a typical website today... But a gopher hole gets you where you need,and then you're done.
Most websites have a goal of keeping you there longer.
I finished writing the user interface for Collab. Create user, encrypt passwords, Log In, Log Out, change username, change email, change password, and email verifications.
All using text files on a linux file system for the data.
The only thing I have to keep hidden are the email addresses but I hide all my user data with index.html redirectors and .htaccess deny commands. So no open text files in the user directories.
Tomorrow I hope to update my users to the encrypted passwords and deploy.