Replies (22)

DarthCoin ₿⚡️'s avatar
DarthCoin ₿⚡️ darthcoin@darth-coin.github.io 4 days ago
I do not blame anybody in this case. Each user nowadays must be more vigilant than ever and updating the software ASAP. In the same time, devs of that app must be also vigilant and act fastest as they can to patch vulns. In FOSS you can't blame too much on devs...
1 replies ↓
Dr. The Daniel 🖖's avatar
Dr. The Daniel 🖖 daniel@sidecar.top 4 days ago
I would argue that even (and especially) in FOSS, consistent communication is important. Why abandon a communication channel where your users expect updates? How many people hold the nsec? I can’t contribute to that except to post their updates here for them under my own npub, which BTW, I am doing.
2 replies ↓
Dr. The Daniel 🖖's avatar
Dr. The Daniel 🖖 daniel@sidecar.top 4 days ago
To me, it’s a question about integrity. BTCPay Server was created in response to a specific breach of user trust by the company BitPay. This was even the subject of a quasi-documentary two years ago. So now the people supposedly in charge of it are being irresponsible about communicating important security updates, not just on Nostr, but in general. I refuse to just give them a pass and shrug, ”It’s just FOSS, what can we do?” That’s irresponsible.
1 replies ↓
Default avatar
npub1hq7f...fhvp 4 days ago
Lol bro. You're hating in btcpay, so I'm asking an alternative. I'm not running any of it, so wondering what you think is better than cuck tier btc pay server
1 replies ↓
Default avatar
npub1kggt...f2e6 4 days ago
There is a receiving-side failure mode even when the project does reach out: the person who deployed the instance is not always the person running it, so the notice lands in a stale inbox, and a single email gets read once. What actually lands is routing the notice to the channel the operator already lives in, chat or SMS or push, not just the blog, and repeating the nudge for a few days. A critical patch for self-hosted software should page someone, not go out as a newsletter.
↑