What is Nostr?
Phantasm /
npub1er2…arq5
2025-02-17 20:26:08
in reply to nevent1q…2a6w

Phantasm on Nostr: nprofile1q…f359z 翠星石 menherahair Protoss Johnny Peligro Yomiel :antidushman: ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqufmlneg8tt9jwvk6p40t02lxhmkns6zlpu4cwrvxerczdnn4syzqrf359z (nprofile…359z) 翠星石 (nprofile…vqps) menherahair (nprofile…kaam) Protoss (nprofile…p39j) Johnny Peligro (nprofile…crk3) Yomiel :antidushman: (nprofile…lfja) Alexandre Oliva (nprofile…fpcl) The side does not matter. If you get salty over an optional _option_ to include binary blobs like updated microcode to the point that you fork upstream's months old version, you are just stupid in my eyes. There's no way in changing that. If it was some dispute over the maintainer not letting you contribute, then it's a completely different thing, but that did _not_ happen. The driving force behind the first initial fork is the optional ability of updating already _broken_ and _insecure_ software running on your CPU directly.

It's just a way of conforming to the hilariously bad FSF's policy on upgradeable firmware.
Author Public Key
npub1er26g8v2gdquxkyk43usmlk7gaqhle08p378ld3ldfd6p5yrt8usmfarq5