3 ms·
The other post linked from the one you're commenting on (https://blogs.loc.gov/thesignal/2020/11/an-archivists-perspective-on-legacy-files/ https://blogs.loc.go
by kragen 5y ago
The other post linked from the one you're commenting on (https://blogs.loc.gov/thesignal/2020/11/an-archivists-perspective-on-legacy-files/ https://blogs.loc.gov/thesignal/2020/11/an-archivists-perspe...) talks specifically about the problems of preserving and reverse-engineering dual-fork files, so the problem is not what they're unaware of, Charlie. You just aren't aware of the problem they're trying to solve.
The LOC, the Internet Archive, and the UK National Archives don't benefit from proprietary compilers for proprietary operating systems like SuperCard; their remit is to preserve these files for centuries or millennia, not until the next update of macOS X. If SuperCard interprets a HyperCard stack differently than original HyperCard did, or SuperCard on a new version of macOS X displays or behaves differently than it did on the previous version, that's a failure of digital preservation. Unless, that is, you notice --- and to notice, you need to emulate the original HyperCard environment and/or be sufficiently familiar with the semantics of the file specification. If https://news.ycombinator.com/item?id=29555959 https://news.ycombinator.com/item?id=29555959 is to be believed, SuperCard is 32-bit-only and so will not run on the most recent version of macOS X, which lack 32-bit support, which if true demonstrates the enormity of the problem.
As for streams of bytes, a disk is a stream of bytes, or rather a collection of fixed-size blocks of bytes. HFS is looking at flattened HFS files that have been "squished" to fit on a medium that does not, itself, implement HFS. Therefore anything that you can represent with an HFS dual-fork file can also be represented losslessly in a stream of bytes. (You do of course benefit from understanding the dual-fork structure.) HFS+ actually went further, implementing files with an arbitrary number of forks, like sections in ELF or PE. As GeekyBear points out, NTFS did the same, leading to path traversal vulnerabilities in early Microsoft web servers.
- sokoloff 5y agoWouldn’t an effective (and seemingly easier) digital preservation approach be to virtualize an older Mac OS (System 7 even) and just run HyperCard on it?
- kragen 5y agoYes, that's one of the things they're doing, but in the screenshots they're using MacOS 9. It's less effective if you want to do things like full-text search, copy and paste, or render the vector graphics (though maybe those were MacDraw and not HyperCard?) at a different pixel resolution than the emulated Macintosh supported, or with antialiasing. There may also be metadata or "forensic" data that isn't visible directly in HyperCard itself, which may be of interest to future historians. Aside from the emulation/undocumented-format problem that the librarians here are suffering from, a really big problem with born-digital archival work for more recent formats is copyright. Although libraries are permitted to make copies for archival work, in many cases the software tools they would need to make those copies don't exist, because those tools would circumvent an effective technological protection measure within the meaning of the DMCA, so writing and distributing them is potentially a crime. So in effect copyright law is privileging the business interests of Harvey Weinstein, Dan Brown, Bob Guccione, and Adam Sandler over the academic interests of scholars, historians, and the Library of Congress. I don't think there's anything wrong with Pee-wee Herman or Amy Poehler making movies, but I don't think it's worth sacrificing the intellectual heritage of humanity to buy them second vacation homes.
- chongli 5y agoFunny you should mention the DMCA. The Library of Congress is uniquely empowered by the DMCA to grant exceptions to it. So if there are any cases where the law is deemed to be a barrier to this effort then the LOC can grant themselves and their colleagues an exemption.
- kragen 5y agoThe Librarian of Congress has the opportunity to grant such exemptions in a rulemaking once every three years, which then expire if they are not renewed, which makes them a risky basis on which to base a product; probably the LoC would have to develop the software themselves, which isn't really a strong competency of theirs, instead of relying on outside help. It isn't the kind of thing where a summer intern can ask permission to break a DRM scheme for archival purposes and then be successfully preserving material the next week.
- duskwuff 5y agoYes, and honestly that's going to be the only effective way of preserving some stacks. In particular, some stacks included XCMDs/XCFN resources, which contained native 68k code and could interact with the OS in arbitrary, unrestricted ways.