<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2026-05-02T23:48:35Z</updated>
  <generator>https://yabu.me</generator>

  <title>Nostr notes by seedubs</title>
  <author>
    <name>seedubs</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://yabu.me/npub1sqkk8s34npcu8yzaa79mfz5glutqkfgpd4l5nlxaswcdwpvykdus0frfgp.rss" />
  <link href="https://yabu.me/npub1sqkk8s34npcu8yzaa79mfz5glutqkfgpd4l5nlxaswcdwpvykdus0frfgp" />
  <id>https://yabu.me/npub1sqkk8s34npcu8yzaa79mfz5glutqkfgpd4l5nlxaswcdwpvykdus0frfgp</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://yabu.me/nevent1qqsxwq6anc24afrmje6qxm4wm57s2f34j2pg49jne35dvhxrwn2986czyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjy72zjl</id>
    
      <title type="html">The main problem with an untrusted payment metadata is that the ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsxwq6anc24afrmje6qxm4wm57s2f34j2pg49jne35dvhxrwn2986czyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjy72zjl" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsxquwvjgw8e6drz25t4mxh9mf8ssz2y3typ0tk9angj6t9scp6e6cczp9nt&#39;&gt;nevent1q…p9nt&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;The main problem with an untrusted payment metadata is that the boost total amount could be faked. With podpay, user signed, you would know the message is at least from Nostr User that paid. Perhaps hosted apps could just mark that field with a slight warning.
    </content>
    <updated>2024-12-07T00:19:30Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsrx8ykxp3sfrs2vd0wjzvhkhvve2f2scj0ykgkq9pr7hurcvaec0szyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjsl3tj0</id>
    
      <title type="html">One nice thing about Nostr is you can generates its ID before ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsrx8ykxp3sfrs2vd0wjzvhkhvve2f2scj0ykgkq9pr7hurcvaec0szyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjsl3tj0" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsg3p8mla676ttqeuw0nf9sy56ygfzlm7xhm0kf6lngssu3jpawkjces2a2m&#39;&gt;nevent1q…2a2m&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;One nice thing about Nostr is you can generates its ID before posting it. With mastodon I think you would have to post first to get an Id to include in the LNURL memo. Apps would have to delete the Mastodon post if the payment failed. I think this works fine but maybe not as slick.
    </content>
    <updated>2024-12-01T03:48:02Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsxt39n52m8rpyjsjjxqufjnydht0dkx0pma6t4fkcun5q95g6xlhszyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjn9mtnq</id>
    
      <title type="html">The BoostBot on irc.zeronode.net, not Fountians, would now need ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsxt39n52m8rpyjsjjxqufjnydht0dkx0pma6t4fkcun5q95g6xlhszyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjn9mtnq" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsygmk00lhcurc68406jtja737xxf803zaht6dect2v50ffdcr5r6clk3wlw&#39;&gt;nevent1q…3wlw&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;The BoostBot on irc.zeronode.net, not Fountians, would now need to run a http server with either a DNS or Onion URL to handle the lnurl bit. Then when an invoice is paid it would query a set of Nostr replays for the naddr thats is linked in the invoice. Then post the message to IRC or wherever. &lt;br/&gt;&lt;br/&gt;Again it would be nice if this Boostbot could tell the Boosting App what Nostr Relays it should post to.
    </content>
    <updated>2024-11-30T21:23:51Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsygmk00lhcurc68406jtja737xxf803zaht6dect2v50ffdcr5r6czyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehj64e7ak</id>
    
      <title type="html">How would this work with BoostCLI and a split to the Fountain ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsygmk00lhcurc68406jtja737xxf803zaht6dect2v50ffdcr5r6czyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehj64e7ak" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsqg2jed4zzd7fyfau2skspx0gkdpn80txm3k0stpw2uf9h0vawf8cd35dly&#39;&gt;nevent1q…5dly&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;How would this work with BoostCLI and a split to the Fountain BoostBot? BoostBot would of broadcasted a Note signed by a user and Fountain would know what it was paid because the naddr is linked in the invoice. Would Fountain repost the Note on its feed or surface it  in the app just by querying the Note by its addr?&lt;br/&gt;&lt;br/&gt;Is there a way to for the Fountain to tell BoostCLI which relays it should boardcast to?
    </content>
    <updated>2024-11-30T21:17:25Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsqg2jed4zzd7fyfau2skspx0gkdpn80txm3k0stpw2uf9h0vawf8czyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjxs9r0c</id>
    
      <title type="html">I want to discus how and if this would work for apps like ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsqg2jed4zzd7fyfau2skspx0gkdpn80txm3k0stpw2uf9h0vawf8czyzqz6c7zxkv8rsusthhchdy23rl3vze9q9kh7j0umkpmp4c9sjehjxs9r0c" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsyarh3w4qx5alcjwjmqvrxkqsznc2uqrr3rekyxeg4aprq6pkyvdcx2yjs5&#39;&gt;nevent1q…yjs5&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;I want to discus how and if this would work for apps like BoostCLI which do not have a centralized server. My main concern is with &amp;#34;trusted&amp;#34; npubs which may exclude BoostCLI Notes.&lt;br/&gt;&lt;br/&gt;From what I understand BoostCLI would first generate or use a provided nostr keys. Construct the boost message in the note and generate its hash id, naddr. Then it would do the lnurl bit including the naddr in the memo/tlv. Then pay the invoice and broadcast note to a set of relays.
    </content>
    <updated>2024-11-30T21:12:33Z</updated>
  </entry>

</feed>