mastodon 4.7.3I'm here for old computers, radios, and cool nerdery.
I identify with #Unix #Linux #HamRadio #retrocomputing and #making.
Professionally I am a computer scientist, now primarily an educator of college students. I am a #SystemsProgrammer with deep experience in #networking, #EmbeddedSystems, and #OperatingSystems. I have also worked in #security from time to time.
The operating system you're using has code written by people who were consulting documents that I co-authored to get it right.
Hey look, @veronica@explains.social put out a video on a subject I've spent a lot of time with: AIM and the OSCAR servers. https://www.youtube.com/watch?v=VDQTuJWST4M
She also teased a future post about @pidgin@fosstodon.org, which I look forward to.
I don't know who needs to see this, but here's an UltraSPARC III cpu module. #retrocomputing #SPARC #SunMicrosystems
You can tell that Typst is a successful LaTeX competitor because when I'm done with a Typst session I have dozens of tabs open to DuckDuckGo, the Typst documentation, various Typst packages and their documentation, and the forums.
How many domains is too many domains? Asking for a friend.
(Also why have they gotten so expensive?!?)
Marchintosh is almost over and I haven't even powered up a classic Mac. :-(
A new friend, from Summer of '84. They should have a familiar look, for those of us of a certain set of interests.
640K? What about 64K? Do more with less, right?
We're losing computing history at an incredible rate, but there are people doing just amazing work out there collecting not only information about the technologies, but also the people and processes that brought them to be. If you're interested in that kind of thing but not sure where to start, let me recommend some sites that have some great stories (in no particular order):
https://folklore.org/0-index.html
https://multicians.org/
http://www.tuhs.org/
There are others, of course! #ComputerHistory
https://www.instructure.com/incident_update
"The data fields involved include information like usernames, email addresses, course names, enrollment information and messages. Core learning data (course content, submissions, credentials) was not compromised."
"Canvas by Instructure is fully operational and remains safe to use. Core learning data is not compromised."
So, basically, personal information and federally protected data was stolen, but it's safe because nobody's slides were compromised?
#HigherEd #BigTech
https://blog.himanshuanand.com/2026/05/the-90-day-disclosure-policy-is-dead/
I think this is a use case for LLMs and coding assistants that I can actually see and get behind. The fact that they're exploitative and unsustainably expensive to generate/maintain is still a problem that I don't have an answer for, but running bug and vulnerability checks against your _own codebase_ seems like just a good idea, in 2026. I'm still not convinced for routine code development.
JFK is the second worst airport
