Event JSON
{
"id": "77aacf7854888c4901c348e3832b05d20d162c7443d89613418fc94bd3fc5cdc",
"pubkey": "ea01c28d25fdebef270fb11977d88794eaa6e04210af4e9f0d45d2ca4df3e28e",
"created_at": 1702676685,
"kind": 1,
"tags": [
[
"p",
"5756e48c151a59e483a3ee9028206897ac79a32e17e93142baea1c430aefcaa8",
"wss://relay.mostr.pub"
],
[
"p",
"02a0f2cd76233181ace57dc1bcc8c69d14efd1b973613d49e6e28b2cb89aee30",
"wss://relay.mostr.pub"
],
[
"e",
"bcac135f13055e79997b85d448b6126843bb99b4010bc2b9e11764db6981e7f5",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://chaos.social/users/koz/statuses/111586619243190757",
"activitypub"
]
],
"content": "nostr:npub12atwfrq4rfv7fqara6gzsgrgj7k8ngewzl5nzs46agwyxzh0e25qxlme5y Someone actually reported this (might have been on r/prusa, having trouble locating the issue). Given Danny P's spiel on 'we don't run linux that's too insecure', I _really_ have to wonder what clown priorities their firmware team is being fed.\n\nOh, and while we're at it, _another_ thing requiring fixing: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/3351\n\nYes, now you can't PID tune _at all_, rather than just being unable to save it.",
"sig": "8e914a6f10a8847f60ed50c0cb602139beb44bc1a978d75710a6c956f98a34c6f6c607eae8a419f386b074cc3c20a1bbc711d92e53801090c05aa9480ec48a72"
}