Damus
tal profile picture
tal
@tal

#bitcoin

Relays (12)
  • wss://nostr.wine – read & write
  • wss://eden.nostr.land – read & write
  • wss://nostr.azte.co – read
  • wss://nos.lol – read & write
  • wss://nostr.oxtr.dev – read & write
  • wss://relay.damus.io – read & write
  • wss://relay.nostr.info – read & write
  • wss://no.str.cr – read & write
  • wss://relay.snort.social – read & write
  • wss://offchain.pub – read & write
  • wss://relay.nostr.bg – read & write
  • wss://nostr.mutinywallet.com – read & write

Recent Notes

Kate ≐ · 135w
To me it looks insane! They are playing making bots all day😂
Kate ≐ · 135w
Yes he does. And some other kids added ChatGPT api to the server, according to my son.
tal profile picture
I've been considering enhancing the credibility of the @nprofile1q... and @nprofile1q... by developing an open-source verifier. This verifier would fetch & compare messages from the mailing lists to their respective Nostr accounts. Every X hours it would ensure all messages have been published and remain unaltered, then sign a "sync validation signature" with the validator nsec and publish. This approach could provide stronger assurance that no additional layer of moderation exists in the cloned mailing lists. What are your thoughts on this? Any ideas on how we can feasibly implement it? Perhaps only reasonable with nsecbunker? @PABLOF7z
tonyaldon · 135w
Great demo!
tal profile picture
That's odd. I've just discovered that the long-form event tagged summary on Coracle displays some random note instead of the correct one. In contrast, Amethyst shows it correctly. Does anyone know why this could be happening?



@Vitor Pamplona
@hodlbod!
PABLOF7z · 140w
yes service providers will assess/price risk or go bankrupt Service providers would choose whom to serve, and at what price. Companies have been managing risk for centuries, it's not new, and reput...
tal profile picture
I understand @Mazin point. High-cost services will only be available to a select few users who pass the stringent reputation test, which is acceptable. But why not implement both options? Why not allow users to pay upfront (a concept I'll call "zapfront" 😄) to specific service providers (based on reputation), and also signal a permission for a delivery of results via an encrypted DM?
1
PABLOF7z · 140w
because a prepayment system is trivial to implement and doesn't require a NIP. look at strike; they've built an entire business around allowing you to buy a bit of bitcoin, they measure the risk of default (ACH fucking sucks) and if you are not an asshole and revert they slowly increase your limit ...
Derek Ross · 140w
I'm sure at some point we'll have a client that does something like this, but that user can just use another client. And most likely as soon as a client starts putting people in jail, the majority of it's user base would jump ship.