I'm already on the latest version, released less than 5 years ago! But yes, I'm up to date with security patches -- I am considering going to Slackware current more so I can stop relying on my clanker or manual compilation to get around outdated dependencies. Just trying to give the benevolent dictator for life a chance to work out the kinks for a full release. Always updating to be 'up to date' is one of those things I'll always push back on a little, because up to date often means 'you have all the latest bugs!' Along with the fixes for the older bugs. Separating security fixes from feature updates is something any project worth its salt should be doing. If yours isn't, time to ask why not. And I get that it's not always black and white. That's where documentation and transparency in general have to come in.

Replies (2)

Default avatar
nupe 1 week ago
Certainly something like a bitcoin client should. Core and Knots would just reclassify all their fuckery to security necessary tho.
Possibly. There are a lot of security fixes in Core though. Most aren't what most casual users would worry about as much (often DoS vectors) but not many releases happen without security fixes. It'd be nice to see more segregated fixes. Fwiw you could definitely do this yourself though cultivating PR's separately on GitHub. I wouldn't have a clanker DO it but it should be able to teach you how easily enough.
↑