Coracle is suddenly fixed.

Coracle canceled?

That sale ($373M) probably happened months ago because financial reporting is delayed. A smoke and mirrors show for Blackrock to play their hand while people are distracted. Over $15B transacted (approx 551k BTC) on the Bitcoin network today. My hunch is they are scooping up coins on the cheap before SEC v Grayscale decision.

This is where i think petnames work well. If you petname the real McCoy, and your client shows your petname in a special font or color, you can have it say "(the real) Jack" and not be fooled by other "Jack"s. (I keep meaning to add this to gossip, it is a small and easy change, but I keep diving deep into the hard stuff first).

Of course initially this doesn't help if you don't know which keypair is the real Jack. That probably has to be discovered out of band though (e.g. professing your keypair on Twitter).

Maybe 1984-aware clients could flag as "possible impostor" any account that other people have reported as being such.

what is DVMs and where can i learn about it？

WHAT A DAY TO HAVE (LESS THAN) ZERO FIAT AVAILABLE

#plebchain #stack #mercy

I’m no longer interested in letting machines or 3rd parties with no information about me creating lists of anything for me. I want to organically find new people and topics to follow and let things play out as they would offline. If that means I don’t make any friends, that is on me. But at least I don’t have to worry about Nostr becoming Twitter or Facebook. I understand onboarding refugees from other networks, especially those who are less technically inclined, is an important problem to solve, but I don’t think cloning the experience they are looking to escape is the answer.

Great write up. What are your thoughts on the idea of using DVMs for user onboarding? As we start to see client apps implement suggested topics and accounts to follow during initial user onboarding, it seems like a custom feed or custom list of recommendations generated by a DVM for that user would be a better approach than a handpicked list of topics/accounts. The idea is that, assuming the DVM isn’t maliciously manipulating results, the custom feed/suggestions would be more reflective of the individual user’s bias/interests instead of the bias/interests of whoever creates the handpicked lists.

Until we’re in a hyperbitcoinized world, I think it makes sense in general to set prices in #bitcoin terms (with bitcoin as the preferred payment), but if someone *must* pay you in fiat then calculate the amount in fiat based on the 20/50/200 day moving average.

Of course this also applies in the reverse case if prices/wages are initially denominated in fiat.

Using the moving average reduces risk for both sides; it’s a win-win.

Uhh whatever nip 24 is

I deleted my instagram account. Don’t know why it took me so long.

I think I was in the first 10 accounts on the platform, and one of the first angel investors. Kevin was our intern at Odeo.

When they sold to FB I stopped using it.

Will be interesting to see what happens with the @name…

IMHO the fact that nostr identities use self-created and self-managed keypairs is not a flaw, nostr does not need a way to bind keys to names, nor does it need identity provider services.

If you want to bind a key to a name, use a petname. That idea was there from the start (afaik). What is a name anyways other than a way for you to remember who that key represents?

The whole business of binding keys to other sorts of identifiers was always murky to me. Why are these other sorts of identifiers important? Who are they important to? Are the centralized? Do they promote centralization? Why should I trust some 3rd party with this binding?

Back at Sun Microsystems IT, I made a proposal I was (and still am) very proud of, but it wasn't accepted and probably wasn't really well understood either. The proposal was to send new recruits a javacard with a Sun PKI keypair pre-generated on the card, along with a serial port smartcard reader (this was pre USB). They would fill out their job applications under a session authenticated by (or else digitally signed by) the keys on that card. Everything the company knew about the person happened through those keys. In this way, the problem of authenticating people before giving them a keypair disappeared. The problem of binding some knowledge about them to a keypair was solved, because all that knowledge was acquired in the first place through that keypair.

I have no idea who fiatjaf really is. I don't know his real name. No third party bound some identifying information about him to his keypair and shared it with me in certificate form. And yet I have a good idea who he is and how much I trust him and in which regards. "By their fruits shall you know them" - Matthew 7:16

Nostr has other issues. How to roll over a keypair. How to export/import private keys without risking their exposure. IMHO these are much better issues to have than ... oh shit Thawte/StartCom/Comodo/DigiNotar/TurkTrust/NICCA/CNNIC/WoSign/LetsEncrypt/Symantec/StartCom/GoDaddy/Certinomis fucked up and aren't trustworthy.

I'm eager to join the club and implement new-style DMs in gossip. Should I do 580, 686, or 706 (or are they functionally equivalent?)

LOWER

Let’s go lower 🙏