Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: Brad Spencer <brad@anduin.eldar.org>
Cc: Paul Winalski <paul.winalski@gmail.com>, coff@tuhs.org
Subject: [COFF] Re: Typical Fate of Older Hardware
Date: Mon, 31 Jul 2023 21:59:49 +0000	[thread overview]
Message-ID: <aX95-5D10q9vB9wQNTnlymgjOxf4idLwiIPJOecY7UNABANQoju11K6gFOxDkGT3RIKvrIANcImI094IqNVGbIB3IMW2jtJuWbUyLtfQoYw=@protonmail.com> (raw)
In-Reply-To: <FjMdkRKfgpCxwLtYM8D8Z_jXrCX8PbLsc2mmH35vMeHZEyJq2SJhkEDJnpP81b3hBvdkoD9k4okY4tL-I1XN5XXM9oywA1Ogn56F2uzYOvs=@protonmail.com>

> iron nitrate being formed and the reaction goes apoplectic.

Copper...not iron...thought I proofread better than that.  Iron certainly will not spontaneously evolve from copper metal and nitric acid.  In any case, I had never considered mercury solubility Paul, that's quite an interesting way to go about it.  I wonder if gallium would do something similar...

- Matt G.

  parent reply	other threads:[~2023-07-31 22:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29 23:26 [COFF] " segaloco via COFF
2023-07-30  3:04 ` [COFF] " steve jenkin
2023-07-30  3:33   ` segaloco via COFF
2023-07-30 16:15 ` Grant Taylor via COFF
2023-07-30 20:33   ` Steffen Nurpmeso
2023-07-31 16:36     ` [COFF] " Paul Winalski
2023-07-31 16:52       ` [COFF] " Brad Spencer
2023-07-31 18:40         ` segaloco via COFF
2023-07-31 21:20           ` Paul Winalski
2023-07-31 23:11             ` steve jenkin
2023-07-31 21:59           ` segaloco via COFF [this message]
2023-07-31 17:28       ` Steffen Nurpmeso
2023-08-01  6:30     ` Wesley Parish
2023-08-01 21:14       ` Steffen Nurpmeso
2023-07-30 21:51 ` Paul Winalski

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='aX95-5D10q9vB9wQNTnlymgjOxf4idLwiIPJOecY7UNABANQoju11K6gFOxDkGT3RIKvrIANcImI094IqNVGbIB3IMW2jtJuWbUyLtfQoYw=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=brad@anduin.eldar.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).