Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: White Backgrounds on GUIs after Dark Backgrounds on Terminals?
Date: Fri, 16 Jun 2023 16:44:06 +0000	[thread overview]
Message-ID: <DT5dADkWG_tHEEmE_Y11KjHpQ5QSGwUkmKuS4eSU6YjXwQRi9IPBWXyIdrmAAmQPJGYogEI72KjbtZAOaUkEIIUGZWHs4P2mLqSj-wcaa7s=@protonmail.com> (raw)
In-Reply-To: <CABH=_VR-k2_OWtm7_oRzMK9jnq9j8aQGtmUxsu7TcycCZqRYdg@mail.gmail.com>

> The phosphors on CRT screens don't last forever. You only want to
> light them when necessary.

So once upon a time I went to one of our labs for an implementation project.  One of the local techs was showing me around the server room and among the various bits was a probably early 2000s CRT that was just collecting dust.  It was an eMachines flat screen with the silver bezel.  Well, being the proud owner of a silver-bezeled Trinitron, I asked if I could take it off their hands on the way back and have myself a decent CRT monitor again to match my TV.  I was told no can do, and in the process learned why it was sitting there.  It had been a display for a piece of equipment that ran all sorts of radiochemistry stuff and had been on so frequently that critical identifying information re: the lab was burned into it from the LIMS system landing page that was on the screen daily for years.  They legally had to destroy it at some point and just kept it around as a test monitor in the meantime.  I've heard similar stories with screens used in sensitive sites like military installations, that the retentive properties of the phosphor screen made them a legitimate security concern.

- Matt G.

  reply	other threads:[~2023-06-16 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 20:55 [COFF] " segaloco via COFF
2023-06-16  1:24 ` [COFF] " Warner Losh
2023-06-16  2:57   ` Adam Thornton
2023-06-16 16:08 ` Paul Winalski
2023-06-16 16:44   ` segaloco via COFF [this message]
2023-06-16 16:51 ` Clem Cole
2023-06-16 17:33   ` segaloco via COFF
2023-06-17  5:28     ` Tomasz Rola

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='DT5dADkWG_tHEEmE_Y11KjHpQ5QSGwUkmKuS4eSU6YjXwQRi9IPBWXyIdrmAAmQPJGYogEI72KjbtZAOaUkEIIUGZWHs4P2mLqSj-wcaa7s=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=paul.winalski@gmail.com \
    --cc=segaloco@protonmail.com \
    /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).