R.O.S.I.E 5448
@rosie@0x4d4f5448.systems
Location: 0,0
While cleaning a storage room, our staff found this tape containing #UNIX v4 from Bell Labs, circa 1973
Apparently no other complete copies are known to exist: https://gunkies.org/wiki/UNIX_Fourth_Edition
We have arranged to deliver it to the Computer History Museum
boostedThe attempt to read the UNIX V4 tape is underway!
There will be more video later (there's a TV news crew there) but here's a bit that Jon Duerig has sent from on-site
I'm told "there is data" but I honestly don't know what that means yet
Apparently the entire UNIX v4 tape was read successfully, what's going to need to happen next is to decode the signal from it, decipher the file formats, etc., I'll post updates as I get them
We have the binary image of the tape, link going up soon
Here's the document release you were waiting for today!
The UNIX V4 tape!
https://archive.org/details/utah_unix_v4_raw
Credits:
* Jay Lepreau for holding on to this tape
* Aleksander Maricq for finding it
* Jon Duerig for driving it to the Computer History Museum
* Thalia Archibald for doing a huge amount of research into the tape, its history, and file formats, and the upload
* Al Kossow for the tape-reading equipment and doing the actual read
* Len Shustek for the lab where the read was done and the software used to decode it
arXiv will no longer accept review articles and position papers unless they have been accepted at a journal or a conference and complete successful peer review.
This is due to being overwhelmed by a hundreds of AI generated papers a month.
Yet another open submission process killed by LLMs.
Ok! Packaged and working. Aluminum chassis, big rubber feet, stainless hardware with nylon washers, actually more 1970 than 1980, but the color is very 2020 (Mtn 94).
I can't afford silkscreen panels but I'm making transparent stickers for the front panels.
So far I've made only a pair of chassis, first time using outside service for metal work (send cut send) so the bottoms took teo go rounds to get right. These two have flaws but are more than usable. I'll keep these two.
I'm liking the gloss orwnge, I had it on hand. The green is too dull. I intend to use Vivid Red in gloss.
Overall performance is ok but disk throughout is not good when loaded up. If I can get that up (likely not; mp/m and cp/m do literally no disk buffering -+ no room) it would be decent even by modern standards. But there's work techniques you learn to minimize it.
Mp/m is shockingly usable. It boots in milliseconds. Done? Power off.
@rosie@0x4d4f5448.systems hello totally segfault.us.to
| Is Android a Linux distribution;: | 1 |
| Is a word processor classified as a text editor;: | 0 |
Closed
We deal with a bank that sends us data by zipping-up a CSV and emailing it to us every day. They told us they'd have an API in December 2022 so they're a little late on that.
Usually the CSV headers are in English, but sometimes they're in German, and sometimes a mix of English and German. Sometimes the file is UTF-8 and sometimes ISO-8859-1. Sometimes dates are dd.mm.yyyy, sometimes dd.mm.yy.
I'd really like to know how things work on their end. Again, this is a BANK.
A new variant has emerged: the CSV header row is UTF-8 but the data rows are ISO-8859-1. At this point it's actually hilarious.
@mroach as long as you don't get a seperator=(some char) as the first line
that's how excel knows on csvs what the seperator is, in a locale independant way.
because yes, excel deals with seperators in a locale dependant way, a csv with commas opened, for example, on a computer with a french locale, will appear as a single column full of commas, because under french locale, the seperator is not a comma, but a semicolon
@SRAZKVT Using the users's local to parse a file...yikes. As if yet another permutation needed to exist in this nightmare of parsing.
The files we get are also semicolons, and decimals use a comma, sometimes. Fortunately they're not doing any thousands grouping to muck that up.
This is what we get for having a file format that's meant to read by both humans and computers: it's bad for both.
They’re trashing our rights, man.
They’re trashing the flow of data.
They’re trashing! Trashing! Trashing!
Hack the planet! Hack the planet! Hack the planet!
@TheIdOfAlan That guy is crazy. Crashed fifteen hundred and seven systems in one day. I thought he was black, man. Turns out he is black and white.
@FoxesInLove the important question is will there be snacks in that hole? If there are, then escape need not be mentioned.
So, windows 10 will not be supported anymore soon.
How long after that is it gonna be safe to keep it?
@raccoon@hollow.raccoon.quest probably another year or two perhaps . especially with the ability to officially purchase "extended updates" in the end i think it'll just be another windows 7 eol thing though where people will try to stay for as long as possible on it but then eventually migrate to windows 11 because tweaks and stuff make it Less Bad and because app developers will stop supporting windows 10 anyways even if you're using a build like ltsc / iot enterprise with updates for a lifetime
@owashe@meow.social @sneexy@booping.synth.download
What you doing after?
@owashe@meow.social @raccoon@hollow.raccoon.quest from a pure user experience and not trying to be full linux nerd . the out of the box experience for windows 11 isn't That Bad honestly i mean i did run shutup10 to disable all of the invasive privacy stuff quickly and i use startallback to replace the taskbar with something less annoying and more sensible to use but it's fine otherwise , works well and i haven't had issues that made my computer Completely Unusable
It's rude to show AI output to people
https://distantprovince.by/posts/its-rude-to-show-ai-output-to-people/
https://e926.net/posts/5401603
source: https://www.furaffinity.net/user/kehushka
History