Avatar
Ademan
2cb30c36438bad4a2a5107bc98f5cebe6a0229b0554d8cfbd1c99aa3cc7ecec1
Neanderthal hacking on Bitcoin stuff. LNHANCE please!

The key is still that *people* need to change their standard of proof. We could have that kind of credulity today if people didn't trust coindesk headlines and only trusted articles that linked directly to a press release from the SEC's website. (being posted on the SEC's website is sufficient attestation)

In a world where signed messages are standard, people might be more skeptical of random assertions.

Rumors, which can't be expected to be signed by the correct authoritative source, would still spread as usual though, which is what cointelegraph would continue doing.

"SEC approves blackrock Bitcoin ETF" might not fly in such a world, but "Anonymous source says blackrock Bitcoin ETF approval imminent" can't really be stopped without making better people lol

The most expensive single-byte optimization I'm aware of lol

News like this reminds me how little I actually check the price...

I can never commit to giving nixos a proper try. Did you ever just use nix as a package manager on top of your previous distro of choice?

Who is "we"? You got a rat in your pocket, Janet?

Made my first signet musig transaction using my (WIP) rust library!

If you were writing a command line tool to process PSBTs, how would you handle accepting base 64 encoded PSBT strings?

1. as a command line argument? ( --psbt-base64 bUnChOfBaSe64... )

2. on stdin? (with a prompt, or not?)

3. Both? ( --psbt-base64 - means read from stdin, otherwise try to interpret the argument as base64 )

I just tried using coracle with only my npub on my phone. It's mostly good but it seems to show me I have notifications, but not let me see them.

It also made me realize it would be nice to be able to write replies and posts, but in a way that they are queued up to publish once you get home/to a computer with your nsec on it. Probably would want it encrypted, NIP-04 DMs are probably "good enough" for this, the metadata leak is hardly fatal. You'd want a key handshake so that your nsec-having client knows what to do with them.

I guess this kinda looks like NIP-46 but with manual review, and persisted signing requests (and very likely you might perform an edit during review).

I like to think I'd put my life on the line in that sort of situation, but who knows if I'm much more of a coward than I imagine myself to be.

Last comment on this I swear! What about just calling it a "Score" or "WoT Score" and if the user cares enough to investigate what that is, give them a precise description in a tooltip or something. Otherwise, all the user REALLY needs to know is it's some kind of score, higher is better.

I mean every word so far has been an imperfect descriptor, I wouldn't throw out "popularity" just because it's an imperfect match. "alignment" is probably closer to correct, but it's not very clear to a new user imho.

An imperfect understanding of the word "popular" will still lead someone to basically correctly understand the WoT score. "apparent popularity" actually is a near perfect match imho, but it's a bit wordy.

"in groupiness" was my first thought after popularity, but I think it's also a bit unclear to your average new user, and it sounds goofy lol

Under the right circumstances, I like to think so. Definitely wouldn't risk it for my govt though, nor it's "interests", nor its empire (same thing).