+- Eric P -- 44d -----------------------------------------------------------[...]+ | | | 🧠 dumb relay, dumb client. Write the JSON yourself. | | | +-- reply ------------------------------------------------------------------- ---+🧠 dumb relay, dumb client. Write the JSON yourself.
npub1gfh3zdy07r37mgk4hyr0njmajapswk4ct6anc9w407uqkn39aslqqkalqc
+- Eric P -- 95d -----------------------------------------------------------[...]+ | | | Wow this looks great! | | | +-- reply ------------------------------------------------------------------- ---+Wow this looks great!
+- Eric P -- 116d ----------------------------------------------------------[...]+ | | | https://image.nostr.build/6c75a30f1a340d32f35a4a66fbdeb4970d08450beeb1b5293845 | | 97577a69b155.jpg | | | +-- reply ------------------------------------------------------------------- ---+https://image.nostr.build/6c75a30f1a340d32f35a4a66fbdeb4970d08450beeb1b529384597577a69b155.jpg
+- Eric P -- 116d ----------------------------------------------------------[...]+ | | | nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr It seems | | like the new(er) version of Nostrudel requires that you set up outbox relays | | before you can post. Can it show an warning message or something if you don't | | have them set up or try to post without having them set up? | | | | I don't use Nostr too much and it took me awhile to figure out why it was | | trying to post to 0 relays. | | | +-- reply ------------------------------------------------------------------- ---+nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr It seems like the new(er) version of Nostrudel requires that you set up outbox relays before you can post. Can it show an warning message or something if you don't have them set up or try to post without having them set up? I don't use Nostr too much and it took me awhile to figure out why it was trying to post to 0 relays.
+- Eric P -- 127d ----------------------------------------------------------[...]+ | | | I think Nostr is great for discovery. The only method we have for RSS right | | now is a centralized database called the Podcast Index. We could use Nostr | | relays to decentralize that index and provide a way to share music and | | podcasts with friends and others. | | | | I don't think Nostr is suited for hosting content. RSS is a simple text file | | that you can host on any webserver along with your MP3s. Webservers are very | | good at serving small static files like RSS at scale and can do 10k | | requests/sec out of the box. Compare that to Nostr, which can take multiple | | seconds to find a single piece of content spread across multiple relays. | | | | The problem with RSS is the user interface. Many people want a simple user | | interface for it and don't want to learn how it actually works. We do have | | https://musicsideproject.com and https://sovereignfeeds.com that let you fill | | out a form to generate an RSS file. You still need a place to put that file | | and some people don't want to learn how to upload files to webservers either. | | | | I think there's a good opportunity to combine the strengths of each technology | | and build something great. You could build a Nostr app that uses Nostr relays | | for podcast/music discovery, uses RSS to build podcast/music feeds, and uses | | Blossom to host the RSS feed and MP3s on a webserver for you. | | | +-- reply ------------------------------------------------------------------- ---+I think Nostr is great for discovery. The only method we have for RSS right now is a centralized database called the Podcast Index. We could use Nostr relays to decentralize that index and provide a way to share music and podcasts with friends and others. I don't think Nostr is suited for hosting content. RSS is a simple text file that you can host on any webserver along with your MP3s. Webservers are very good at serving small static files like RSS at scale and can do 10k requests/sec out of the box. Compare that to Nostr, which can take multiple seconds to find a single piece of content spread across multiple relays. The problem with RSS is the user interface. Many people want a simple user interface for it and don't want to learn how it actually works. We do have https://musicsideproject.com and https://sovereignfeeds.com that let you fill out a form to generate an RSS file. You still need a place to put that file and some people don't want to learn how to upload files to webservers either. I think there's a good opportunity to combine the strengths of each technology and build something great. You could build a Nostr app that uses Nostr relays for podcast/music discovery, uses RSS to build podcast/music feeds, and uses Blossom to host the RSS feed and MP3s on a webserver for you.
+- Eric P -- 128d ----------------------------------------------------------[...]+ | | | We had that one magical night and then went our separate ways. It sucks. | | | | We did build some cool apps to hopefully bridge the gap: | | | | nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq37amnwvaz7tmwdaehgu3dwfjkccte9ejx2un | | 9ddex7umn9ekk2tcqyqlhwrt96wnkf2w9edgr4cfruchvwkv26q6asdhz4qg08pm6w3djg3c8m4j | | built Podstr and Zaptrax to host and play RSS feeds with Nostr. | | | | nostr:nprofile1qyg8wumn8ghj7cfwdehhxtnvdakz7qgwwaehxw309ahx7uewd3hkctcqyzsf2t4 | | srftxagc8wrcn9elsgzz6450ewyz95z5478nse53etrkx6hp5hgd built a killer V4V music | | app https://v4vmusic.app that has all the features you'd want in a music app | | including Nostr logins, community ratings, spam filtering, playlists, live | | streams, publisher tags, podroll, and more. | | | | nostr:nprofile1qyfhwue69uhnzv3h9cczuvpwxyargwpk8yq5gamnwvaz7tehwde8ydmrdpukxdn | | kd3585urrxf5xcdnv096kuemkd36k76r6wfkhgdekdd38xdrtd4ukg6rj0phkz6mtvfch2cty9ekx7 | | cmpdsqzpauj9g9dk0aymkj7aj4x9ahhaes4nal4tcyqxe5xc68qswpvx3ugq3zarj built | | http://ITDV.podtards.com to highlight the excellent musical talents of The | | Doerfels and also built his own music app https://stablekraft.app/ | | | | nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7etyv4hzumn | | 0wd68ytnvv9hxgtcqyphydppzm7m554ecwq4gsgaek2qk32atse2l4t9ks57dpms4mmhfx5ltf6v | | built https://castr.me that automatically publishes media in your npub as an | | RSS feed. | | | | I would invite anyone who wants to help to check out some of the vibe coding | | tools that are now available, like Shakespeare, Cursor, Claude, Codex, and | | Gemini. Many of the apps I referenced were coded by people who have never | | coded before. It's never been easier to build something and be the change you | | want to see in the (Nostr/RSS) world. | | | | <promo> | | The RSS crowd is having another live concert on January 9th at 7pm to | | celebrate the release of So Big's new album: As If. | | | | The concert is going to have a lot of surprises based on your zaps and boosts | | so tune in! It will be streaming on all of your favorite podcast/music 2.0 | | apps as well as on Nostr/Tunestr. | | </promo> | | | +-- reply ------------------------------------------------------------------- ---+We had that one magical night and then went our separate ways. It sucks. We did build some cool apps to hopefully bridge the gap: nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq37amnwvaz7tmwdaehgu3dwfjkccte9ejx2un9ddex7umn9ekk2tcqyqlhwrt96wnkf2w9edgr4cfruchvwkv26q6asdhz4qg08pm6w3djg3c8m4j built Podstr and Zaptrax to host and play RSS feeds with Nostr. nostr:nprofile1qyg8wumn8ghj7cfwdehhxtnvdakz7qgwwaehxw309ahx7uewd3hkctcqyzsf2t4srftxagc8wrcn9elsgzz6450ewyz95z5478nse53etrkx6hp5hgd built a killer V4V music app https://v4vmusic.app that has all the features you'd want in a music app including Nostr logins, community ratings, spam filtering, playlists, live streams, publisher tags, podroll, and more. nostr:nprofile1qyfhwue69uhnzv3h9cczuvpwxyargwpk8yq5gamnwvaz7tehwde8ydmrdpukxdnkd3585urrxf5xcdnv096kuemkd36k76r6wfkhgdekdd38xdrtd4ukg6rj0phkz6mtvfch2cty9ekx7cmpdsqzpauj9g9dk0aymkj7aj4x9ahhaes4nal4tcyqxe5xc68qswpvx3ugq3zarj built http://ITDV.podtards.com to highlight the excellent musical talents of The Doerfels and also built his own music app https://stablekraft.app/ nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyphydppzm7m554ecwq4gsgaek2qk32atse2l4t9ks57dpms4mmhfx5ltf6v built https://castr.me that automatically publishes media in your npub as an RSS feed. I would invite anyone who wants to help to check out some of the vibe coding tools that are now available, like Shakespeare, Cursor, Claude, Codex, and Gemini. Many of the apps I referenced were coded by people who have never coded before. It's never been easier to build something and be the change you want to see in the (Nostr/RSS) world. <promo> The RSS crowd is having another live concert on January 9th at 7pm to celebrate the release of So Big's new album: As If. The concert is going to have a lot of surprises based on your zaps and boosts so tune in! It will be streaming on all of your favorite podcast/music 2.0 apps as well as on Nostr/Tunestr. </promo>
+- Eric P -- 154d ----------------------------------------------------------[...]+ | | | They're just standard Lightning nodes that use Keysend rather than Lightning | | Address/LNURL/Invoices to receive payments. Most of them (other than Fountain) | | are self-hosted and self-custodied rather than being hosted by a custodial | | wallet. | | | | Both Keysend and LNURL are ways to get around Lighting's requirement that a | | sender needs to ask the recipient to generate an invoice before they can pay | | them. There's no way to send a "spontaneous payment" in standard Lightning. | | | | Keysend works by sending the payment with an empty invoice. The recipient's | | node just receives the sats and ignores the fact that there's no invoice | | attached. The sender uses the node's public key to send the recipient sats via | | the Lightning network. | | | | LNURL works by putting a publicly-accessible webserver in front of the | | recipient's node who's only job is to generate invoices for people who ask for | | them. The sender uses the recipient's Lightning Address to look up the | | webserver, sends a request to the LNURL callback, and gets an invoice back. | | They then can pay that invoice on the Lightning network. | | | | V4V nodes chose keysend because it's simpler and requires no additional | | lookups or servers in the middle of the payment process. You just send a | | payment from your node to the recipient's node through the Lightning network | | and that's it. | | | | Wallet providers, including most of the ones the Nostr folks use, chose LNURL | | and ignored keysend entirely, which is why many here are unfamiliar with it. | | | +-- reply ------------------------------------------------------------------- ---+They're just standard Lightning nodes that use Keysend rather than Lightning Address/LNURL/Invoices to receive payments. Most of them (other than Fountain) are self-hosted and self-custodied rather than being hosted by a custodial wallet. Both Keysend and LNURL are ways to get around Lighting's requirement that a sender needs to ask the recipient to generate an invoice before they can pay them. There's no way to send a "spontaneous payment" in standard Lightning. Keysend works by sending the payment with an empty invoice. The recipient's node just receives the sats and ignores the fact that there's no invoice attached. The sender uses the node's public key to send the recipient sats via the Lightning network. LNURL works by putting a publicly-accessible webserver in front of the recipient's node who's only job is to generate invoices for people who ask for them. The sender uses the recipient's Lightning Address to look up the webserver, sends a request to the LNURL callback, and gets an invoice back. They then can pay that invoice on the Lightning network. V4V nodes chose keysend because it's simpler and requires no additional lookups or servers in the middle of the payment process. You just send a payment from your node to the recipient's node through the Lightning network and that's it. Wallet providers, including most of the ones the Nostr folks use, chose LNURL and ignored keysend entirely, which is why many here are unfamiliar with it.
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | The Lightning network already uses other nodes to route payments. Doesn't | | BOLT12 just extend this concept to also route messages? | | | +-- reply ------------------------------------------------------------------- ---+The Lightning network already uses other nodes to route payments. Doesn't BOLT12 just extend this concept to also route messages?
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | https://github.com/getAlby/hub?tab=readme-ov-file#optional-configuration-param | | eters | | | +-- reply ------------------------------------------------------------------- ---+https://github.com/getAlby/hub?tab=readme-ov-file#optional-configuration-parameters
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | Well at least until the Alby Nostr relay goes down. You did switch that in the | | AH config, didn't you? | | | +-- reply ------------------------------------------------------------------- ---+Well at least until the Alby Nostr relay goes down. You did switch that in the AH config, didn't you?
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | That's the logical alternative to the LNURL payment flow: | | | | Instead of: Payer -> HTTP/LNURLp -> Recipient | | Do: Payer -> Nostr Relay (Hopefully not Cloudflared) -> Recipient | | | | Of course if we adopted keysend or BOLT12, the payment flow would be Payer -> | | Recipient without any middlemen. | | | +-- reply ------------------------------------------------------------------- ---+That's the logical alternative to the LNURL payment flow: Instead of: Payer -> HTTP/LNURLp -> Recipient Do: Payer -> Nostr Relay (Hopefully not Cloudflared) -> Recipient Of course if we adopted keysend or BOLT12, the payment flow would be Payer -> Recipient without any middlemen.
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | It looks like you can fetch the offer code from NIP-01 or NIP-05 | | https://github.com/shocknet/CLINK/blob/main/specs/clink-offers.md#integration- | | with-nostr . | | | +-- reply ------------------------------------------------------------------- ---+It looks like you can fetch the offer code from NIP-01 or NIP-05 https://github.com/shocknet/CLINK/blob/main/specs/clink-offers.md#integration-with-nostr .
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | It would be good for running some local LLMs | | | +-- reply ------------------------------------------------------------------- ---+It would be good for running some local LLMs
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | That's the best thing about having a de-Googled phone. All of the | | notifications go away and you realize that none of them were ever important. | | | +-- reply ------------------------------------------------------------------- ---+That's the best thing about having a de-Googled phone. All of the notifications go away and you realize that none of them were ever important.
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | Decentralize harder! | | | +-- reply ------------------------------------------------------------------- ---+Decentralize harder!
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | Unfortunately, the most popular Lightning implementation (LND) still doesn't | | support BOLT12. Every major implementation except them supports it. | | | | I would love to kick LNURL to the curb and go full BOLT12, but it can't happen | | until they get with the program. | | | +-- reply ------------------------------------------------------------------- ---+Unfortunately, the most popular Lightning implementation (LND) still doesn't support BOLT12. Every major implementation except them supports it. I would love to kick LNURL to the curb and go full BOLT12, but it can't happen until they get with the program.
+- Eric P -- 159d ----------------------------------------------------------[...]+ | | | Looks like a great space! | | | +-- reply ------------------------------------------------------------------- ---+Looks like a great space!
+- Eric P -- 160d ----------------------------------------------------------[...]+ | | | The only constant in life is change | | | +-- reply ------------------------------------------------------------------- ---+The only constant in life is change
+- Eric P -- 160d ----------------------------------------------------------[...]+ | | | Ooo What's this? 👀 | | | +-- reply ------------------------------------------------------------------- ---+Ooo What's this? 👀
+- Eric P -- 167d ----------------------------------------------------------[...]+ | | | nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc I have | | more Castr PRs for your consideration: | | | | https://github.com/dergigi/castr.me/pull/18 | | https://github.com/dergigi/castr.me/pull/19 | | | | I think the NIP-53 works now too: | | https://github.com/dergigi/castr.me/pull/9 | | | +-- reply ------------------------------------------------------------------- ---+nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc I have more Castr PRs for your consideration: https://github.com/dergigi/castr.me/pull/18 https://github.com/dergigi/castr.me/pull/19 I think the NIP-53 works now too: https://github.com/dergigi/castr.me/pull/9
+- Eric P -- 199d ----------------------------------------------------------[...]+ | | | I'm not cool enough | | | +-- reply ------------------------------------------------------------------- ---+I'm not cool enough
+- Eric P -- 199d ----------------------------------------------------------[...]+ | | | I thought her emoji was 🤡 | | | +-- reply ------------------------------------------------------------------- ---+I thought her emoji was 🤡
+- Eric P -- 208d ----------------------------------------------------------[...]+ | | | Yessir? I didn't know there were multiple of me. That could be pretty useful | | in the future. | | | +-- reply ------------------------------------------------------------------- ---+Yessir? I didn't know there were multiple of me. That could be pretty useful in the future.
+- Eric P -- 208d ----------------------------------------------------------[...]+ | | | We originally chose keysend because you can send metadata (sender name, total | | amount before splits, message, podcast, episode, app name, etc) along with | | payments through the Lightning network. You didn't need any web server or | | service sitting in the middle. | | | | Keysend also just lets you send a payment without requiring the other side to | | generate an invoice first. Most of our feeds have payment splits in them for | | the podcast hosts, crew, and anyone responsible for putting together a podcast | | and it's a bit cumbersome to have to generate multiple invoices for every | | single split. | | | | We've since updated the spec to allow for a Lightning Address to be used in | | the feed which allows the app to use either keysend or LNURLp depending on | | what the sending and receiving wallets support. | | | | But we haven't completely figured out how to send the metadata to the | | recipient since LNURLp doesn't allow the same amount of metadata that keysend | | does. nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 | | solved the issue by posting the metadata as Nostr notes, but some in the | | community are reluctant to rely on Nostr or don't want their metadata to be | | publicly available on Nostr. | | | +-- reply ------------------------------------------------------------------- ---+We originally chose keysend because you can send metadata (sender name, total amount before splits, message, podcast, episode, app name, etc) along with payments through the Lightning network. You didn't need any web server or service sitting in the middle. Keysend also just lets you send a payment without requiring the other side to generate an invoice first. Most of our feeds have payment splits in them for the podcast hosts, crew, and anyone responsible for putting together a podcast and it's a bit cumbersome to have to generate multiple invoices for every single split. We've since updated the spec to allow for a Lightning Address to be used in the feed which allows the app to use either keysend or LNURLp depending on what the sending and receiving wallets support. But we haven't completely figured out how to send the metadata to the recipient since LNURLp doesn't allow the same amount of metadata that keysend does. nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 solved the issue by posting the metadata as Nostr notes, but some in the community are reluctant to rely on Nostr or don't want their metadata to be publicly available on Nostr.
+- Eric P -- 208d ----------------------------------------------------------[...]+ | | | I'm happy to help. There's a bunch of us here that understand the RSS spec. | | nostr:npub177fz5zkm87jdmf0we2nz7mm7uc2e7l64uzqrv6rvdrsg8qkrg7yqx0aaq7 | | nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9 | | nostr:npub19ha7tju4teqp3dmwv4p28wrcy9zd6h6hxkg5mwvjrlfycweazpkse2q0fa | | nostr:npub1yvscx9vrmpcmwcmydrm8lauqdpngum4ne8xmkgc2d4rcaxrx7tkswdwzdu to name | | a few. | | | +-- reply ------------------------------------------------------------------- ---+I'm happy to help. There's a bunch of us here that understand the RSS spec. nostr:npub177fz5zkm87jdmf0we2nz7mm7uc2e7l64uzqrv6rvdrsg8qkrg7yqx0aaq7 nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9 nostr:npub19ha7tju4teqp3dmwv4p28wrcy9zd6h6hxkg5mwvjrlfycweazpkse2q0fa nostr:npub1yvscx9vrmpcmwcmydrm8lauqdpngum4ne8xmkgc2d4rcaxrx7tkswdwzdu to name a few.
+- Eric P -- 234d ----------------------------------------------------------[...]+ | | | Yeah lnaddress/lnurlp is what we want to move towards, but the boost metadata | | issue has been tricky. | | | | Keysend lets you attach arbitrary metadata (TLVs) along with your payment, | | which is how boosts work right now. The payments and boost metadata arrive | | directly to your wallet/node without any third-party involvement. | | | | Lnurlp doesn't have the same flexibility and only gives you a 200 character | | comment field to use, which is too small for our purposes. We basically need a | | service or api or something to store the metadata for each payment and there's | | no agreement on how that should work. | | | | Nostr solved this problem by having the lnurlp server post the metadata back | | to Nostr as a zap receipt whenever receiving a payment. There's still some | | ambivalence about using Nostr or any third-party service in the podcast world. | | | +-- reply ------------------------------------------------------------------- ---+Yeah lnaddress/lnurlp is what we want to move towards, but the boost metadata issue has been tricky. Keysend lets you attach arbitrary metadata (TLVs) along with your payment, which is how boosts work right now. The payments and boost metadata arrive directly to your wallet/node without any third-party involvement. Lnurlp doesn't have the same flexibility and only gives you a 200 character comment field to use, which is too small for our purposes. We basically need a service or api or something to store the metadata for each payment and there's no agreement on how that should work. Nostr solved this problem by having the lnurlp server post the metadata back to Nostr as a zap receipt whenever receiving a payment. There's still some ambivalence about using Nostr or any third-party service in the podcast world.
+- Eric P -- 234d ----------------------------------------------------------[...]+ | | | Unfortunately you have to pick one or the other. Alby and Fountain are | | basically the only two that support keysend, but they're the two that most | | podcasters use right now. Other wallets like Strike or Primal only support | | lnaddress and don't support keysend. | | | | You can look up the keysend info for a person through the well-known url. For | | example, my well-known (ericpp@getalby.com) is at | | https://getalby.com/.well-known/keysend/ericpp . That gives you my lightning | | node pubkey and a custom key/value for my wallet (basically a wallet id). | | | | You can then use the pubkey, custom key, and custom value to create a | | valueRecipient tag: | | <podcast:valueRecipient name="ericpp@getalby.com" type="node" | | address="02c7bb6f29f09d92d40d62d64443b688891259dea324406b4678df6235794f24bf" | | customKey="696969" customValue="34" split="1"/> | | | +-- reply ------------------------------------------------------------------- ---+Unfortunately you have to pick one or the other. Alby and Fountain are basically the only two that support keysend, but they're the two that most podcasters use right now. Other wallets like Strike or Primal only support lnaddress and don't support keysend. You can look up the keysend info for a person through the well-known url. For example, my well-known (ericpp@getalby.com) is at https://getalby.com/.well-known/keysend/ericpp . That gives you my lightning node pubkey and a custom key/value for my wallet (basically a wallet id). You can then use the pubkey, custom key, and custom value to create a valueRecipient tag: <podcast:valueRecipient name="ericpp@getalby.com" type="node" address="02c7bb6f29f09d92d40d62d64443b688891259dea324406b4678df6235794f24bf" customKey="696969" customValue="34" split="1"/>
+- Eric P -- 234d ----------------------------------------------------------[...]+ | | | nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 There is | | a small issue with your feed. The value recipient types should be lnaddress | | rather than lightning-address: https://sessions.soapbox.pub/rss.xml . | | | | Also, the podcasting world hasn't fully figured out the switch from keysend to | | lnaddress. So if you want to see boost information (sender name, total unsplit | | amount, message, etc), you have to use keysend rather than lnaddress. I think | | Fountain might work regardless since it also posts this info to Nostr? | | | +-- reply ------------------------------------------------------------------- ---+nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 There is a small issue with your feed. The value recipient types should be lnaddress rather than lightning-address: https://sessions.soapbox.pub/rss.xml . Also, the podcasting world hasn't fully figured out the switch from keysend to lnaddress. So if you want to see boost information (sender name, total unsplit amount, message, etc), you have to use keysend rather than lnaddress. I think Fountain might work regardless since it also posts this info to Nostr?
+- Eric P -- 238d ----------------------------------------------------------[...]+ | | | I like the way Nostrudel does it. You shouldn't need to be prompted for a | | signature until you're actually do something that requires a signature. | | | +-- reply ------------------------------------------------------------------- ---+I like the way Nostrudel does it. You shouldn't need to be prompted for a signature until you're actually do something that requires a signature.
+- Eric P -- 247d ----------------------------------------------------------[...]+ | | | LOL. I don't understand what you did, but good work! | | | +-- reply ------------------------------------------------------------------- ---+LOL. I don't understand what you did, but good work!
No replies found in cached notes yet.
+- Eric P -- 116d ----------------------------------------------------------[...]+ | | | https://image.nostr.build/6c75a30f1a340d32f35a4a66fbdeb4970d08450beeb1b5293845 | | 97577a69b155.jpg | | | +-- reply ------------------------------------------------------------------- ---+https://image.nostr.build/6c75a30f1a340d32f35a4a66fbdeb4970d08450beeb1b529384597577a69b155.jpg
Pubkeys from this user's latest cached kind 3 follow list.
- Alex Gleason 0461fcbe…74dd
- 0b1aef6f7eb2 0b1aef6f…f84c
- ExFrog 0f43f6e2…18a3
- Hash Power Music 16cb4b38…ab94
- 1cbd9bbf3c8c 1cbd9bbf…2f62
- Wavlake 2250f696…248b
- 23103189356c 23103189…e403
- Sir Spencer - Wolf of KC 🐺 23218315…f2ed
- hzrd149 266815e0…08a5
- Joe Martin 28ca019b…b2cc
- 29f16e91607a 29f16e91…d96a
- 2dfbe5cb955e 2dfbe5cb…106d
- 2e80c77b8b94 2e80c77b…e48d
- Kagi 34104ded…9969
- ZEUS 34d2f527…8095
- 36e2c7a70c3d 36e2c7a7…2b75
- 3762d3159bfd 3762d315…5fed
- 3a02709eb796 3a02709e…eb0e
- 3e82be8e4e0d 3e82be8e…4b2d
- Derek Ross 3f770d65…5b24
- 3fe2921a235f 3fe2921a…0fb8
- Eric P 426f1134…ec3e
- Alby 4657dfe8…4b3e
- 48f396bf751c 48f396bf…eddd
- 4b6f261ab671 4b6f261a…033e
- bitpunk.fm is typing 4d4ab737…fad8
- 500a6aa0f6b3 500a6aa0…8e16
- 50a63cca15b1 50a63cca…f637
- 56a6b75373c8 56a6b753…b727
- 577092262e31 57709226…9c02
- 5ea721dd7828 5ea721dd…c06c
- 605343ab36f8 605343ab…c8d4
- 627ffdd6bcc0 627ffdd6…4d02
- 63fe6318dc58 63fe6318…04ed
- Fountain 6538925e…55c3
- 71f397f52d5c 71f397f5…0d9e
- 73cb112da121 73cb112d…631c
- 75fab518bc41 75fab518…0cd4
- 77d806622e78 77d80662…f3a4
- Sir HeyCitizen 79438d33…3ad4
- 814e68274342 814e6827…f2dd
- 8170418bb228 8170418b…dcc8
- 85dd87c00615 85dd87c0…4fc0
- 8806372af515 8806372a…23bc
- 8e27ffb5c9bb 8e27ffb5…715c
- 8f40fd27b5d9 8f40fd27…821a
- 91fc34496959 91fc3449…6765
- 9b21f34dcbfc 9b21f34d…0dbd
- 9d34e78eca0f 9d34e78e…4762
- 9df3800a280e 9df3800a…1fe6
- a91ab68e566a a91ab68e…117d
- b33bf9e97b78 b33bf9e9…f50d
- b64327017bb0 b6432701…ff73
- b9d02cb8fdde b9d02cb8…5e04
- c2c706f0d083 c2c706f0…2f60
- c6928631ded8 c6928631…901d
- makeheroism d28b07a8…00e8
- d73f8e873604 d73f8e87…fa24
- db34f1de110b db34f1de…b4d5
- dbd36ca65776 dbd36ca6…be48
- df4ad57c137b df4ad57c…e40d
- e49744a8127c e49744a8…e09c
- e4f695f05bb0 e4f695f0…1092
- e61093809c30 e6109380…fde1
- ea2e3c814d08 ea2e3c81…6f14
- ec7de4aa8758 ec7de4aa…a33f
- OpenMike eeb11961…1b9e
- f133b246f076 f133b246…8dda
- f4a29f6397c3 f4a29f63…1ea3
- ChadF and 33 others f7922a0a…4788
- f9cd08f5942e f9cd08f5…5174
- fe7f6bc6f733 fe7f6bc6…39a3
Cached pubkeys that follow this user, discovered from kind 3 events.
- Bryan Entzminger 0834bbe3…c59b
- Jin 10b662ea…371b
- New Music Nudge Unit 12c41114…6cf5
- Hash Power Music 16cb4b38…ab94
- Sir Spencer - Wolf of KC 🐺 23218315…f2ed
- Eric P 426f1134…ec3e
- Thomas 46c670d2…7098
- bitpunk.fm is typing 4d4ab737…fad8
- Fountain 6538925e…55c3
- Sir HeyCitizen 79438d33…3ad4
- Nostr Gang 91aeab23…8660
- makeheroism d28b07a8…00e8
- OpenMike eeb11961…1b9e
- ChadF and 33 others f7922a0a…4788
- Strange Love fd2ee25f…373f
+------------------------------------------------------------------------------+
|
|
Identifiers
npub: npub1gfh3zdy07r37mgk4hyr0njmajapswk4ct6anc9w407uqkn39aslqqkalqc
hex: 426f11348ff0e3eda2d5b906f9cb7d9743075ab85ebb3c15d57fb80b4e25ec3e
no cached metadata event yet
+------------------------------------------------------------------------------+
Suggested read/write relays from this user's latest kind 10002 event.
-
wss://nos.lol -
wss://relay.snort.social -
wss://relay.damus.io