@ek216
3,473,663 sats stacked
stacking since: #57444longest cowboy streak: 216 verified stacker.news contributornpub16x07c...2j2s96s89d
0 sats \ 1 reply \ @ek 5h \ on: Building a bitcoin engineering school - Lisa Neigut at The Bitcoin Commons bitcoin
woohoo, @BenAllenG, you got a shout-out
Didn't know that you attended Base58 and that it even was your first programming class, that's crazy, mad respect
Linux really makes you appreciate simple things like having sound.
And when you have sound, it makes you appreciate when the sound automatically switches from speakers to headphones when they are plugged in.
Both changing and not changing Bitcoin present equal risk of unknown unknown, it is inherent in the very nature of what that is.
That's an interesting point. I am not sure I agree. Does the risk of "unknown unknowns" not decrease over time? Intuitively, I would think so but maybe I am missing something.
And it looks great, but to this date, it doesn’t have a one-click backup option, which is why I didn’t feel safe putting my corn on there.
To be fair and to the extent of my knowledge, what LND calls backup is more like an emergency recover which can fail since your peers need to cooperate with you to recover your funds.
Maybe someone else can expand on this, it’s been some time since I last read about this.
update: I’m talking about SCB as explained here. I read some controversy around naming it backups since it’s not a backup in the common sense where you can recover from failure without any third party interaction required.
My biggest purchase mistake in the past 3 months might have been to save money by purchasing a 1m USB-C cable to recharge my laptop and not 2m. I was in a hurry and didn't think it through.
After all the hassle with it, I am going to buy the longest USB-C cable that I can find.
To be fair, it's normal procedure during bug reports to ask the user about the behavior they are seeing and what they want to see so we can confirm we understand your problem and can fix it.
A good bug report should include this:
- Description with actual behavior
- Steps to reproduce
- Expected behavior
Since you used "fix" here, we assumed you are talking about a bug and not about a feature request. Sorry for that misunderstanding.
Regarding the request: This was discussed during implementation but we went with user relays adding to the defaults for now, not overriding them.
They mean this: https://base58.info/
I think it would have been better if the new version with less features was packaged separately as
keepassxc-minimal as was raised in the discussion and not as a "rugpull" by replacing the existing keepassxc package.Security needs to work with user interests in mind, not against them.