Subnostr

the scales look like crinoid calyces

Replying to

calle

let's code

https://m.primal.net/NzdO.mp4

yes, let's do this

Replying to

Shawn

gm, good people. ☕ Have a great weekend.

gm ☕

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyr040dycdgkxtxt9c00etj3lag6n8gs8kzdl9326wr2qd37sfyfy7m8u7rh when you get a chance, try shooting me a sat at plantimals@npub.cash

Replying to

waxwing

Analogy:

Scientific concept "greenhouse effect" becomes more "non-technical, friendly, appealing" phrase "global warming" becomes deliberately slogan-like completely meaningless "climate change".

Similarly, technical innovation "bitcoin" becomes slightly more sexy-sounding "blockchain" eventually becomes slogan-like and utterly meaningless "crypto".

https://en.wikipedia.org/wiki/Emotive_conjugation

sounds similar to "emotive conjugation"

Replying to

Zapstore

Go to albyhub.com and look for the wallet connections tab, you need to generate a new connection and that will give you the string, it starts with nostr+walletconnect://

got it, that worked. thank you!

Replying to

rejon

Yes, its support it well. I'm using it everywhere now.

https://cashu.me

nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg is responsive as well.

The future is here now.

ha, when you get tired of this, https://cashu.me ;)

that's great man, thank you. lots of running around today, tomorrow I will get it running and send you a bounty if it works.

Replying to

rejon

I'm open to anything that will fix this. you are suggesting I can wire up my cashu wallet to the zapstore app? do they support NWC?

Replying to

Zapstore

Your wallet should give you a magic string to paste into Zapstore

thank you for your help nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpq0r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7sdvr7w9 . I'm using nostr:nprofile1qyt8wumn8ghj7ct5d3shxtnwdaehgu3wd3skueqpzemhxue69uhky6t5vdhkjmn9wgh8xmmrd9skcqg4waehxw309ajkgetw9ehx7um5wghxcctwvsq3samnwvaz7tmxd9shg6npvchxummnw3erztnrdaksz9nhwden5te0ddkx7cmtv4hxwcfwwdhkx6tpdsqs6amnwvaz7tmwdaejumr0dsq3kamnwvaz7tmwdaehgu3dwp6kytnnv4kkjum0dshxgetkqywhwumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wsq3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdsq3qamnwvaz7tmwdaehgu3wd3skueqpr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgpz3mhxue69uhkummnw3ezummcw3ezuer9wcq3qamnwvaz7tmwdaehgu3wwa5kuegpzfmhxue69uhk7enxvd5xz6tw9ec82cspr9mhxue69uhhqatjv9mxjerp9ehx7um5wghxcctwvsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qgjwaehxw309aex2mrp0yhxvdm69e5k7qg4waehxw309aex2mrp0yhx6mmnw3ezuur4vgq3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyqyv8wumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdsq3jamnwvaz7tmnv4hxg6t59ehx7umxd3shyefwvdhk6qpqxnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sq394nw backed by nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qydhwumn8ghj7mn0wd68ytf39ehxymewv9hxwctwdyhxxmcpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0wfjkccte9ehx7um5wghxyctwvsq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshsqgzx2l0739jmazvq4yc8908mtev6v5fygpkmp7qey90w0zay0y6t8ccesg0j Hub. I am not able to find a "magic string" in either. I searched for any extant docs or guides and am unable to make sense of this. can anyone point to a resource that explains what the string is?

my goal is to us nostr wallet connect to fund payments for the apps I use regularly via the zapstore.

Replying to

I only have one issue with zaps. I wish they were splittable. I wish it was widely adopted that an event could have a split tag, and in that tag were several different addresses with the percent of the zap that went to each address. You now have an auditable contract.

If we make a video together and put it in a note, I would like that note to have 50% of the zap amount go to you and 50% to me, and either off us could look at the raw event to verify the splits were what we agreed to.

I agree, this would be a very impactful feature.

Replying to

I am also working on ways to perhaps bridge nostr and RSS. One thing you may be interested in, because you're right, polling is very wasteful, is something The Podcast Index came up with called Podping. The basic idea is when a new podcast is published, the publisher adds a new event to the Hive block chain. The Index and others are watching the block chain through a websocket, and anytime they see that the feed has been updated, then, and only then, does the Index reparse the feed to get the updated data. It's reduced their bandwidth tremendously and has solved the problem of constant polling. I've been considering building a podping to nostr bridge, since podping is also being used to let podcast apps know when a particular podcast is going live. This way the nostr relays can also know when a podcast is going live.

Now, I happen to be a Podcasting 2.0 fan boy, so my heart is with RSS, but I think there are definitely some things that can be improved, and that the nostr and RSS community can learn some things from each other to improve both experiences. Perhaps you're right, and nostr will ultimately be the protocol to rule them all, but until then, I'd like any of the artists, musicians, and writers to be able to have options for getting their art into the world and supported by their fans, so I'll be working to figure out ways for the two protocols to work together or at least be able to be translated from one to the other so the legacy apps will continue to work if and until we transition.

https://podcasting20.substack.com/p/podping

I would have a much more detailed response, but your note only shows up on my phone, via amethyst. on my desktop, primal doesn't see this. hmm

my one quick point here is that value for value is amazing, but I think the much more direct use of zaps via nostr could be a better alternative. or at least equivalent. I want to build things that people with bitcoin find valuable, and nostr is a good starting point for that audience.

Replying to

Sir Libre

Polling in RSS is no longer necessary due to podping which works fantastically.

I appreciate you pointing this out. It does seem to solve the polling problem.

But it seems to me that NOSTR also solves this problem, but does so in a much more elegant way, with a turnaround time of updates to distribution potentially being measured in milliseconds. Not only that, but the content IS the message.

Plus, I like the idea that the NOSTR protocol carries all the things that I want timely updates on. I would like to have a feed that can handle articles, podcast episodes, comments on all of the above, and all the menagerie of note kinds that I have yet to explore, using a single protocol, so I don't need to mix and match betweeen them. Obviously, if there is a superior protocol for a particular kind of content, I wouldn't hobble utility to have uniformity, but it would be nice to minimize the number of integrations, accounts, and book keeping required to both publish and consume such content.

Have you personally used the Podping stack to publish stuff? I'm curious to hear your experience with it.

Replying to

I'm going to offer some pushback, and not because I necessarily disagree with you, more as a thought exercise.

RSS is simply a data structure. It's saved in a file that's easily fetched, but that data structure could just as easily be saved in the contents of a note. So I don't know that we need to get rid of RSS so much as think about other ways for it to be stored and delivered. I think there are ways an RSS feed can be stored on multiple servers, signed so it's confirmed to be the same data stored in each relay, and the feed can have new tags in it to inform the app of the preferred relay, as well as back up relays to pull the feed from if the preferred relay is ever offline. Using key signing, un updated feed can be sent to multiple servers that are able to verify the feed is indeed being updated by the owner, then replacing the existing feed with the new feed. The underlying data structure that has worked for 20 years and on which the entire podcasting industry is built upon has proven itself. If we can figure out ways of storing that data on multiple relays, most of the podcasting apps will be able to continue to function as they always have, and the only change they need to their code is how the feed is fetched.

And as it stands, every relay you're using right now needs a domain and DNS. Your notes are either on your own relay or one your renting from someone else. I'm not sure how npub fixes that we need servers (relays), those servers need to be findable, and the notes attached to your npub have to be stored on those servers so others can see your notes, even when you're offline. The core ideas of nostr offers redundancy and identity, both of which can be adopted into the RSS feed.

I am glad to have a reasonable conversation.

I agree that the file format is not a problem. It successfully conveys the information we need. And indeed, it could be copied to multiple places, signed, etc.

My point is that the same job can be done in a much better way if it were #NOSTRNative. One aspect is that RSS is a polling process where the file is downloaded at a regular interval and scanned for new contents. This paradigm is inverted by nostr, where an event can be published when there is new content, eliminating the wasteful traffic spent polling.

You are right that relays still depend on domain names and servers. I just think that NOSTR will offer a better pathway to substrate independence and uncensorability.

The pathway to a better version of what RSS is trying to accomplish will be found in using NOSTR directly, rather than reimplmenting some kind of identity and auth scheme for RSS.

My guess is that most of the blogs and podcasts I follow will one day originate as NOSTR notes and get syndicated into RSS feeds by services offering such. I am working on just such a service myself. I don't want someone like you to have to choose. I want the content to be addressable in whatever format you prefer.

"The core ideas of nostr offers redundancy and identity, both of which can be adopted into the RSS feed. "

In this we are in close agreement. And thank you for your reasoned response.

Replying to

Since I already have MSP for building music RSS feeds, and LNBeats for consuming music RSS feeds, I figured I can start learning how to maybe put music into notes so the musicians could have their music available in nostr for v4v as well. Having a project is a good way for me to learn something new. Then I remembered nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg did something a few years back called Wavman, and it's very similar to the idea I had.

I think the Wavlake guys are super innovative, and I've reached out to them from time to time with issues and bug reports, because although I have my criticisms, they're making things easier for musicians, and by and large, I think they want to help out musicians. I don't even care that they're making a business out of it and charging for their services, handling hosting is a big deal that they make easier. There's a problem, and they're charging for a solution, that's how the free market works. I just want them to open their player to all the musicians, even those that choose not to host on Wavlake.

nostr and RSS are meant to be a protocol that allows a musician to choose where they host their content, and any and all clients can find that content and play it. They are truly open protocols.

It doesn't look like much came of Wavman, maybe too soon for it's time. But I think it's an idea still worth exploring, so I'm going to continue playing around with the idea, and see about hosting artwork and mp3s on satellite.earth, or maybe a Blossom server (I'm not sure how to use one of those yet), and then having the necessary metadata in a note to allow all nostr clients to be potential music players.

If we can figure out and widely implement splittable zaps, or maybe wide adoption of Bolt 12, I think zappable media in every nostr client is highly feasible. The musicians will have the potential to get financial support for their art and the listeners can use any client they choose to support any v4v enabled musician they choose.

I hope we can get to the time when we don't need RSS anymore. I agree it is decentralized and serves us well even today. but the paradigm of an NPUB being the source of a stream of verifiable notes that contain blog posts, podcasts, any of these things, that's where we should be going.

At the moment you either need to have your own domain or rent space on someone else's to get an RSS feed stood up. While DNS has not yet been fully weaponized, I think we all realize that it can and will be some day. the NPUB separates our content, or at least our reach, from that system. along with all the other obvious benefits.

Replying to

freecritter

Best method to upload a PDF in a note? #asknostr