The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steve Nickolas <usotsuki@buric.co>
To: Peter Jeremy <peter@rulingia.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] [tuhs] Computer history preservation
Date: Tue, 17 Sep 2019 03:46:15 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.02.1909170336190.71302@frieza.hoshinet.org> (raw)
In-Reply-To: <20190917002825.GA15016@server.rulingia.com>

On Tue, 17 Sep 2019, Peter Jeremy wrote:

> On 2019-Sep-16 15:48:36 -0600, "Nelson H. F. Beebe" <beebe@math.utah.edu> wrote:
>> I came across an article today about another major industry that has
>> been exceedingly careless about preserving its history:
>>
>>        Wipe Out: When the BBC Kept Erasing Its Own History
>>        https://getpocket.com/explore/item/wipe-out-when-the-bbc-kept-erasing-its-own-history
>>
>> It is a must-read for Dr Who fans on this list.
>
> It didn't only affect TV, much of The Goons originals were also destroyed (at least
> one episode now sold by the BBC is an off-air recording by a fan because that's the
> best extant copy).
>
> And NASA destroyed the tapes holding the original Apollo 11 moonwalk
> (https://en.wikipedia.org/wiki/Apollo_11_missing_tapes).

Toei Animation wiped the audio masters for Dragon Ball and Dragon Ball Z. 
What remains is low-quality optical audio from film prints.  (They did the 
same for Dragon Ball GT but some TV stations managed to preserve the 
audio, so it's not as much of a problem as it is for the previous series.)

-uso.

  reply	other threads:[~2019-09-17  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 21:48 Nelson H. F. Beebe
2019-09-16 22:24 ` Gregg Levine
2019-09-16 23:44 ` Dave Horsfall
2019-09-17  0:28 ` Peter Jeremy
2019-09-17  7:46   ` Steve Nickolas [this message]
2019-09-17  5:21 ` Lars Brinkhoff
2019-09-17 15:33   ` Clem Cole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.BSF.2.02.1909170336190.71302@frieza.hoshinet.org \
    --to=usotsuki@buric.co \
    --cc=peter@rulingia.com \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).