{
  "export": {
    "source": "https://urth.darkrealm.vip/thread/urth/2043",
    "note": "Exported from an unofficial mirror of a public mailing list. Copyright in each message remains with the person who wrote it.  Email addresses are obscured as `user at host`, the form the original archive published. This file was rebuilt from parsed fields rather than retained headers, so it is faithful in content but not byte-exact.",
    "addresses": "obscured as 'user at host'"
  },
  "archive": "urth",
  "thread": {
    "id": 2043,
    "subject": "Isid Iooo IoooE (\"Hoo-oo-WEE!\")",
    "messages": 1,
    "voices": 1,
    "first": "1999-12-18T16:00:51+00:00",
    "last": "1999-12-18T16:00:51+00:00"
  },
  "messages": [
    {
      "message_id": "<urth-v0028-0645@digest.urth.net>",
      "from": {
        "name": "Mitch Bailey",
        "address": "chemmie at mindspring.com"
      },
      "date": "1999-12-18T16:00:51+00:00",
      "subject": "(urth) Isid Iooo IoooE (\"Hoo-oo-WEE!\")",
      "in_reply_to": null,
      "reply_link": null,
      "blocks": [
        {
          "kind": "text",
          "depth": 0,
          "text": "Let me chime in impertinently here to Mr. Ansley's letter of the 16th, as I haven't read the story yet, but was intrigued by the observation\n\n). I have always suspected that the\nanswer involves replacing the capital Is in the second and third parts of\nthe name with 1s and the lower-case os with 0s. Thus I get ISID 1000 1000E,\nif I make the first part uppercase at the same time. Unfortunately, this\ndoesn't suggest anything definite to me either, although it does look like\nthe identifying number of a machine, a computer model number, for example.\n\n\nI suppose you could read that \"Isid\" as I.S. Identification [number], whatever I.S. might stand for.\n\nOn the other hand, William, since you read some I's as 1's to get apparent hexadecimal numbers, try reading the \"s\" as a numeral 5 as well? I don't know the context in which this name comes to us, but if it comes of unsophisticated people trying to decipher nearly illegible labeling, then a \"s\" for \"5\" sub seems reasonable. Then you could read the whole assemblage as two 64-bit hex numbers and one 128-bit hex number:\n\n151D, 1000, 1000E\n\nNow, what their significance might be, I still couldn't say, but maybe this is a step in the right direction.\n\nBTW, in honor of my new personal account, I have chosen a list name for myself which I'm sure all can agree is quite appropriate.\n\nTalarican, a.k.a. Mitchell Bailey"
        }
      ]
    }
  ]
}