RIP my bitcoin node ☹️ ### The Bad News: The drive is "Mechanically Exhausted" There are two massive red flags in your data that explain exactly why your system is struggling: #### 1. The "Load Cycle Count" (ID 193) is astronomical - Raw Value: 1,261,658 - Value: 001 (This is the "health" score, and it is at the absolute bottom). - Explanation: This count tracks how many times the drive's heads have parked and unparked (usually to save power). Most consumer hard drives are rated for about 300,000 to 600,000 cycles. - Your drive has done over 1.2 million cycles. It has been "parking" its heads constantly for years. This causes massive mechanical latency. Every time Bitcoin Core needs to read a tiny piece of data, the drive might be "waking up" the heads, which causes a massive delay (latency spike). This is a prime candidate for your timeouts.

Im trying out #armada. What server should I join?

GN nostr

Im going to ask again: why does every nostr app feel the need to overwrite my relay list the first time I open it? I'm looking at you vector

TIL what kind 15 private file messages are. Of course this was after I slopped up a tool to encrypt files with sender/recipient npub/nsec and upload them to temporary hosts to share via url. Note to self: every time you have a "good idea" check if it's already implemented in amethyst. It probably is.

Im conveneing a meeting of the nostr board of directors. @Derek Ross has failed to provide sufficient value to shareholders during his term as CEO. The floor is open to nominate his replacement. View quoted note →