My hospital was affected by the big Microsoft update fiasco ...

fea186c2a4678dbc...

npub1l6scds4yv7xmcsmhqnhdy9sggm520q09lvts2m5mkvecgr2mmmeqsuj5rc

hex

44cd761a505fd1ca1462da3a65d5c2220a3e1fbb670ce10675723a26c84f7dfc

nevent

nevent1qqsyfntkrfg9l5w2z33d5wn96hpzyz37r7akwr8pqe6hyw3xep8hmlqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs0agvxc2jx0rdugdmsfmkjzcyyd698s8jlk9c9d6dmxvuyp4daaus9lpdf7

Kind-1 (TextNote)

2026-03-12T16:15:38Z

↳ Reply to fea186c2... (npub1l6scds4yv7xmcsmhqnhdy9sggm520q09lvts2m5mkvecgr2mmmeqsuj5rc)

Do you necessarily need to lose up time for security? I suppose if something requires a restart? Or do you mean if an update breaks something? Server ...

My hospital was affected by the big Microsoft update fiasco a while back and one of the key lessons for me was how awesome it would be to stage or split updates. Like maybe don't update all machines, CTs, MRIs, etc at the exact same time. Do a 1/2 or something. There are arguments against that probably, but it was hell for us. I imagine servers could have something similar if you're willing to bear the cost of that uptime.

Raw JSON

{
  "kind": 1,
  "id": "44cd761a505fd1ca1462da3a65d5c2220a3e1fbb670ce10675723a26c84f7dfc",
  "pubkey": "fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2",
  "created_at": 1773332138,
  "tags": [
    [
      "p",
      "fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2",
      "",
      "mention"
    ],
    [
      "p",
      "010df0c948fe9ab54d2cb7ea420ffa08d57958981b6ea68e83aaa7eb2dd3f05a",
      "",
      "mention"
    ],
    [
      "p",
      "08bfc00b7f72e015f45c326f486bec16e4d5236b70e44543f1c5e86a8e21c76a",
      "",
      "mention"
    ],
    [
      "p",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
      "",
      "mention"
    ],
    [
      "e",
      "c72c9827eb6b898b5f4cd29bb0018bd34fac394208e45568713018bf4356d58e",
      "",
      "root"
    ],
    [
      "e",
      "efcc51eaca8e97be0504f06f1d5993721e9329adda021c9d06ea37fe08ce3260",
      "",
      "reply"
    ]
  ],
  "content": "My hospital was affected by the big Microsoft update fiasco a while back and one of the key lessons for me was how awesome it would be to stage or split updates. Like maybe don't update all machines, CTs, MRIs, etc at the exact same time. Do a 1/2 or something. There are arguments against that probably, but it was hell for us. I imagine servers could have something similar if you're willing to bear the cost of that uptime.",
  "sig": "3cbf3ff8f07b417b46139713caf6b1663d631b76f613347a19320814b6a7491c443f83d6c455e1962806fa31fa70cc37d4e1f3ca0e00a26a8aa79a3caf8cb9f8"
}