Tone Vays and @jimmysong had Chris Guida on. Good job Chris. Tone was getting a bit too excited there but you stood your ground! I'm of the impression generally that BIP110 is dead on arrival and seeing Chris total conviction of the opposite makes me feel like I might be in a bubble? What are prediction markets at? Is there any momentum to the knots side?

How is the situation globally? The Chinese market should be years ahead of our discussion. They don't have Google Play to begin with but China also produces all the hardware. How do people - tech savvy or not - get around these limitations? Are there any AOSP ready phones sold at scale in China? Are these markets sealed off somehow? Some acquaintance claimed that in Chile phone theft wasn't limited to high-end phones "because they ship them to China where there is demand for unlocked phones". BS, right? I can't imagine that the producer of billions of phones would have trouble to get any specifics at scale?!? View quoted note →

If humanity has terminal currency cancer, eating healthy Bitcoin might not be enough. Sure, it would be enough if all would understand the diagnosis but as that won't happen on the individual level, our fight is futile. I think, we can't rely on "everybody buying bitcoins at the price they deserve". We need people to make the switch when they still have financial fire power left or the long tail of the economic spectrum will crush the few who made the switch earlier. That is why we should care less about institutional adoption and more on those who actually most need money to be fixed. View quoted note →

Promise to zap event in the comments View quoted note →

Where are all the bunker devs? I tried to use zapstore/zsp with Amber but it didn't work because zsp treats the secret of the bunker url as an api key while Amber treats it as a pairing code. And there is good arguments for both approaches. pairing code: the bunker app pairs with a client and from then on uses a client key that is not exposed to the user to avoid re-use. This is a very tight link. If you want to use different clients you have to use different bunker urls and while that is hard to setup, it prevents a situation where you cannot know who is abusing the bunker as there is only one client per bunker url. api key: knox uses the secret from the bunker url like an api key and allows ephemeral client keys. This is easier to setup as a bunker url can be re-used and it's more private as the client key is a nostr identity and re-use means privacy leaks. So knox uses a long secret while Amber uses a short one and those differing approaches result in friction. And the nip allows both. I think there should be more clarity in the nip and as both approaches are somewhat valid, both should be supported. Maybe a pairing code should avoid the parameter "secret=..." and use "nonce=..." or something? Also privacy should be possible regardless of the client key being re-used or not, using giftwraps. @Alex Gleason @greenart7c3 @Nostrmo @Russell