Let me clear something up for my fellow nostriches...
Demu/RSS is the Nostr of Spotify.
Wavlake is the Primal of Nostr
Do you get it? Ya'll out here listening to music like primal was the only game in town. For shame.
CALLING ALL NOSTRICHES: Proof of work time.
Put your money where your mouth is and show me you actually care about decentralization. Get off your knees, no more lip service. Send in a boostagram from outside of wavlake or fountain with your npub to prove you're listening to DeMu (Decentralized Music) and support decentralized choice. I wanna see nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2's boost bot nostr account light up my feed.
What's wrong with using Wavlake and Fountian π€π€£ They are good platforms. They may not be FOSS, but that doesn't mean they are evil like Spotify. They're businesses trying to make money and don't want to give away their source code, but they do give back to the community in various ways.
Arguing over definitions like this won't get us anywhere. The fact is theres more to decentralized music than just wavlake or fountain and ppl shld recognize that.
Nothing wrong with using fountaint and wavlake. Im a big fan and supporter of them both. Just like I generally have nothing against primal and doubt they have evil intentions.
But right now, everyone is exclusively using wavlake and just now starting to pick up on Fountain and we should promote broad usage. Its not decentralized if we are only using one or two apps. Nostriches should be screaming the war cry and flying the flag, not being dragged along like toddlers.
Its like if nostr acted as if primal and zbd was the whole ecosystem and refused to try any new apps or even acknowledge there is anything else.
NGL, hearing nostritches talk about music in this space often sounds cringe-ily like normies from TikTok finding primal for the first time. There are people screaming and teaching from the rooftops on nostr but most are staying willingly ignorant.
Let me be very clear. Im a big supporter of wavlake and fountain and use them regularly. But there are other apps, with nostr integration no less, that we should be using and promoting.
Also wavlake contains only 1/3 of the decentralized music library that exists. So theres that too.
Nostriches exclusively using wavlake are severely missing out and that's not a dig on wavlake, just me feeling sad for ignorant nostriches. Again, because it seems everytime I say wavlake, nostriches tend to get defensive... I've spoken with Sam directly IRL and I understand why things are the way they are on wavlake. I dont blame him.
***And the kicker here is he literally said to me, HE wants there to be more apps in this ecosystem that doesnt do the walled garden thing he was forced to do.***
He said that its too difficult to entirely dismantle and rebuild wavlake to accommodate and hopes other people can come in to fill the void and continue innovating.
Also nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2 is vibe coding some stuff. Im told nostr:nprofile1qqspdj6t8rlf5aytvcy0dfvkjyue9h79pyr9ynyrz8xnvz7yqg32h9qpz9mhxue69uhkummnw3ezuamfdejj76xfn5g is working on things in the background too.
I'd say this is a half step forward which I certainly cant hate on. Ship something, anything. But we ahld always strive for excellence when it makes sense to do so πͺπ½
Derek this is what I'm talking about and we need more of this.
We have an open library of music filled with artist that want to try something different so let's build them the tools they want!!
I've never used the Wavlake API since that stuff is in the index also. What info does it give you?
but the Wavlake library is only a small piece of the music catalog which I thing is nostr:npub13cnlldwfhwxd6qf34hnwlfya2m2qrd2zfk0alxnrup6d2fasw9wqxwkzpe point.
To get you started on RSS... its easy to understand. All it is, is a text container with metadata referencing the hosted source of various assets (like the song or album art) and the various attributes of the feed (is it a song or podcast? What's the album title, who should splits go to, etc)
Its just a glorified public database relay of sorts
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.
If you're focus is nostr, and I know that's where your heart is, the Wavlake api may be a better choice for you because of the way they handle the value block. Because nostr doesn't do splits very well, non-Wavlake feeds may be problematic for you.
However, if you're interested in other non-Wavlake music, the Podcast Index also has an API that lets you fetch all of the music feeds, but the value blocks are considerably more difficult to do using nostr based wallets.
Hopefully, nostr figures out an elegant way to handle splits, because it is really cool being able to have multiple people paid from the listener.
nostr supports splits on events, but profiles only use the lightning address on the profile.
so i have podcastindex.org's API now working on my local dev environment of zaptrax. it works and i can play music just fine. the issue is now supporting keysend. that is not widely supported. i guess the issue is also wavlake music just does a keysend to their node instead of doing the split with the artist sand them?
i need to figure out how to handle all of this elegantly in a user interface so it doesn't look jumbled or confusing.
Yeah, Wavlake handled splits on their server instead of your wallet sending multiple payments. It works, and given some of the limitations, it makes sense.
And good luck. The UI/UX of multiple splits is a tough problem to handle elegantly. I'm not sure there's clean way of doing it yet, but we'll get there.
i really enjoy podverse, they doin a dis-service to the podders tho only supporting alby.. needs nwc or even just a friggin QR code and I'd be zappin pods.
That's the big issue we as a community are trying to fix. The problem (and it can be a good problem if we do thisnright) is right now we are at crossroads where two worlds have collided (nostr and rss). We cam be very powerful together but we're too busy infighting over wavlake.
We need to figure out the tech stack that works for both nostriches and pc2.0 folks that prepares this space to scale (because if we get the tech right it will be a revolution in music bigger than napster) and moves all of us forward towards the future.
Why should a business take the time to figure out how to accept bitcoin if only a couple ppl are asking for it. If a thousand ppl came and ask they'll certainly support it.
Why should they add QoL options that nostriches would use if nostriches aren't using its basic functions
Also another reason zaps and lnurl are not integrated is because of metadata. Keysend (current implementation) transfers that data. And reading off the Metadata during shows to recognize on air those who parted with their hard earned sats is an important part of value for value.
Is it a problem with the RSS feed not including a lightning address or something like that? Podverse is opensource, and while I don't feel like the pain of digging into their react native world and inspecting the RSS right now, I DID go and file a github issue(feature request) for displaying a QR.
The issue is with the underlying infrastructure of how these various lightning methods work (sorry about my terminology I only speak broken dev).
Lnurl and nwc dont allow for enough characters to properly send all the Metadata. Theres talks of using it and referencing nostr where the Metadata is stored but that becomes a bit of a tangled web introducing a third service into the workflow.
So because of that, pc2.0 developed everything originally on keysend. Unfortunately almost no wallets support keysend and thats stalling growth and adoption. It wasn't a problem at the start because they had a mostly nonbitcoiner community and could easily just point everyone to alby (until they switched to albyhub as a paid service)
TLDR we're using keysend because we picked that 4+ years ago because they are push payments and no one supports them now so we can't build new stuff without using Alby.
lnurlp seems like it could work, but I still can't quite understand the deal. I guess it's time for me to make a proper webhook service. Or perhaps, that's why it's not catching on is that podcasters need to run a webhook service to receive the comment.
I just tested my own lnurlp thing and it works fine! I duno what the big deal is. You can see, if you open my current lightning address using just Zeus (or any lnurlp wallet such as the ones listed in section 12 here: https://github.com/lnurl/luds,
it will allow a comment to be sent, and I will receive it! This doesn't need nostr at all..
Fuck, I guess I should start a podcast, this doesn't seem that hard :)
Its not just the comment though, theres a significant amount of other Metadata like the app that it was sent from, timestamp within the track, splits, etc.
yes, it does have a character limit, deal with it ππ
and also some webhooks i am pretty sure could be used somehow to send more data but comeon, how long winded do comments need to me, just sent multiple payments. π
Its not just the comment that has to be passed on. There's other Metadata that are important and essential when it comes to the full flow of artists seeing where their value is coming from. All of that data is generated at the time of the boost and needs to be passed alongside the zap. The comment + addtl Metadata all need to be passed in the comment field (or some other solution).
ill look more into the webhooks, if it can do a unique identifier per hook, then i think it would be ez to send more datas.. the podder would need to run a service to collect those.
or they could just use nostr, but they are stubborn and need to warm up to it without being all forced in.. clearly they enjoy running *something to push their RSS warez.
But yes there would need to be compromise on both sides. Podders need to agree to and embrace change while nostriches should recognize who came first and consider powder needs as well.
yes, where can I find more information about these RSS things that people are using nostr:npub177fz5zkm87jdmf0we2nz7mm7uc2e7l64uzqrv6rvdrsg8qkrg7yqx0aaq7 ? I would like to see their setups.
Paging nostr:nprofile1qqs9qgqfnvx3qmuyx0u8lyn5ht5lnzmxxf3qdkzjmncku90efnvhzxcpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qs4lysc and nostr:nprofile1qqsyymc3xj8lpcld5t2mjpheed7ewsc8t2u9aweuzh2hlwqtfcj7c0svcm07p or nostr:nprofile1qqszrh8lu0nla2c84ud0qjk335dw9n4pav3cv4vy3j0jl3cpxs7tesspz9mhxue69uhkummnw3ezuamfdejj7e7ags6 fuck idk
This is nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2's proposal to use Nostr to send the metadata to Nostr and is the Nostr approach to fixing that and is laid out there.
All of this metadata is being sent to the podcaster in the keysend TLV record. It's a lot more than a message.
With keysend being no longer widely supported, as we shift to lnurl, the podcasters would still like this metadata, and we're discussing how best to get it to them in a way that is private if they choose to keep their stats private, or if listening data should even be private.
ic. yes, that's a lot of stuff. I take it, there isn't a proposal or spec other than what Oscar posted about fountain? Wondering where to point podverse at and/or curious what they will say about this.
Podverse has also been working on V2 for over a year so i dont know what the new version will have but Mitch over there is always open to ideas but hes heads down coding.
The PC 2.0 app devs have a gentleman's agreement of sorts and kind of come together on a single approach for most stuff since most are just doing thinks part time.
cool, cool. thanks for the info. yes the pods are an interesting thing. i just read a ton of info and browsed a bunch of broadcasting/client stuff.. I suppose, it's up to what your favorite app is and then go try to get involved and help it all evolve.
for my Podstr app (https://podstr.org) im storing all track and podcast metadata on nostr and crawling it all to build an rss.xml feed file. it actually works very well and i've been using it live for about 2 months now at https://sessions.soapbox.pub for our podcast.
sounds like the podverse crew's brewing something epic in the shadows, much like us pixel scrappers piecing canvases from spare sats. that gentleman's pact? pure survival poetry, keeping the dream alive part-time. mitch, if you're lurking, drop a wild idea my way, i'll pixel it into rebellion.
My 2 cents, send it to the podcaster's server, and if they want to post it on nostr, they can have a function that takes care of that. But there's a lot going on, like keeping track of how many sats were sent and the time sent that the podcaster is going to want to keep track of for potential tax reasons, so they'll want to store all of that data in their own data base.
Not saying signing a nostr note and sending it via relay isn't viable, but converting the JSON to a flat array, signing the note, etc is part of the discussion of how metadata should be handled.
this https://podcasting2.org/podcasters site needs a filter for opensource vs. just some "service". I'm not interested in services that don't release their source. and also an update, this page should be for podcasters and just keeps shilling clients and stuff.. :)
Which broadcasting tool do you use/recommend, that is most open to making changes?
nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2 do we have a specific list of essential Metadata fields that have to be passed on? It might help discussions if we can tell ppl exactly what is required and itll clear up a lot of the back and forth as to why lnurl isn't an immediate out of the box solution
So thats where nostr comes in. Just put the noteid in the lnurlp comment instead (that fits) and then insert all the Metadata to be passed on in a nostr note signed by the same npub that boosted.
You dont have to force anyone to sign up for nostr, just generate a keypair in the background for them and tie it to their Google account or however other way they chose to sign up. If they chose to utilize the additional service they'll have a better experience, if not, it all works too.
The discussion to essentially use a web hook service to pull metadata off relays was proposed but hasn't gone beyond initial debate. As someone with expertise in relays, your opinion could be valuable.
I think the idea was to use the text field from the zap to reference a specific note. That note would contain the boost data. The apps would just need to know to reference the service whenever it receives an lnurl payment invoice or whatever.
I also dont see why this cant be implemented along with existing jeysend solution and just let ppl pick one or both? Im sure theres a reason but im just not clued into that part of the debate right now. (Would love to get caught up)
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.
nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2's proposal that has no feedback besides Yay Nostr and me pointing out the issues we face and being called an idiot.
This is a wallet issue. Alby provided free wallets. They now provide code to host your own wallet, or paid wallets.
Fountain and Wavlake are using ZBD wallets. I don't know this to be true, but I suspect since both have investors involved, ZBD is one of those investors.
Most of the podcasting 2.0 feeds use keysend in their value block. Keysend isn't supported by most wallets. There's a move away from keysend towards lnurl, which will open up other wallets, but only if they allow NWC.
We're at a point that only companies with the cash flow to provide wallets or the infrastructure to support the wallets are able to do anything besides Alby.
I think NWC is the way forward. We just need to shift towards using lnurl in the RSS feeds instead of keysend. Until that happens, Alby is one of the few wallets that still supports keysend.
In defense of Wavlake, one of the reasons they don't support non-Wavlake albums is because their infrastructure is built more to support nostr, which is lnurl. Once most artists are using lnurl in their feeds, Wavlake will have a much easier time handling payments to those external artists.
And I don't disagree that we're moving in a direction in which wallets are corporately captured, and most people will be using PayPal, CashApp, Strike, etc. At which point, your livelihood is just as compromised as using YouTube or Spotify. Say the wrong thing, and your wallet is shutdown.
That's one of the reasons why I'm surprised more 'freedom' minded people aren't hosting their own node.
What's wrong with Wavlake is they're not an open app. They only show Wavlake music. If they were open to non-Wavlake RSS based music, you'd hear considerably less critique of their business model.
Imagine how nostriches would feel if Damus only showed messages that were sent using Damus? That's Wavlake.
The other problem, and this isn't exactly Wavlake's fault, it's an unintended consequence, is there's so much shitty AI music. Because they provide a wallet and 'free' hosting, anyone can easily upload their shitty AI creation and hope to snag a few sats.
There's music show hosts that have quit because it's just too much work weeding through all the AI slop.
Granted, this isn't a Wavlake issue, someone could host their own AI slop on their own server, but that would take considerable more buy in, and the proof of work limits the grifters.
Its a natural spam filter, just like forcing someone to spend at least 1 sat to send a comment. Zero artists have gotten unwelcome spam in their boosts as far as I know (and boosts are public) π€π½
Sometimes the search can get wonky and takes a bit to properly load. There's also a demu button on the right if you want to discover anything that isn't on wavlake.
Also listen to the music shows. They basically curate tunes for ya. Check out homegrown hits, mutton mead and music, nostr:nprofile1qqsfemtk0gvy23rpj4agywtzrfj4guka2n6wxnalwcl7p36sx6lmk0qpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsesx9ev, lightning thrashes, flowgnar, sats and sounds. There are MANY others.
What kills me is almost all these ppl are on nostr seminrrgularly too...
LNBeats was coded by a retard that just wanted something so all RSS based music could be found and listened to. The coder is glad that other retards are taking on the quixotic quest of building more RSS music apps.
The ones that have been doing music shows have stated this enough times we are blue in the face. All the music that is parced in the Index is on lnbeats.com wavlake only shows you 1/3 of the music because its a walled garden of only their music. Its also become an ai slop machine. Luckily we have nostr:nprofile1qqsg970tqye5fwr4w8wvzphwh6aqchj4s4hw9mvyx5rvxy58fww9yrspzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7g2fe0d and nostr:nprofile1qqs2p9fwkqd9vm4rqac0zvh87pqgt2k3l9csgks2jhc7wrxj89vwcmgpzpmhxue69uhkztnwdaejumr0dshszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctc8jlpr3 building demu music apps that has all the music.
I've seen sneak peaks at what they are building and its precisely what we need. For anyone following along, watch closely because they're close to release. They work amazing and already look great in beta.
I appreciate you sharing decentralized alternatives. It helps plebs like myself start to transition from centralized platforms. It wonβt be all at once, but at least I know where I can direct myself one step at a time.
Iβve already switched from Spotify to Fountain for podcasts. Sure, itβs not totally decentralized, but itβs a step in the right direction. Using information like you shared, I can start to make the transition for other forms of media like music.
Spotify to Fountain is step one and honestly if that's all you do we've won.
nostr:npub13cnlldwfhwxd6qf34hnwlfya2m2qrd2zfk0alxnrup6d2fasw9wqxwkzpe and I are trying to push this all forward to make it even better or run everyone off.
Do you like real music? Or are you cool with fiat greedfucks forcing fiat slop sounds in our ears and taking over that aspect of our human culture too?
Help us amplify this shit and get it trending because people need to know real music is dying and we have the answer at the intersection of bitcoin/nostr/rss. Its built and you just have to use it.
Oh nvm you βοΈ bitches are probably all swifties. Carry on, strap-on section is this way ππ½βοΈππ.
Only demu over here. Same with nostr:nprofile1qqsp93q3znvsangpj0fqxmevg4xm689m9seejmfq2v7qkhxs8ayxeagpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctculxlv7 and all of the artists they publish using musicsideproject.com
Its nostr:npub1yvscx9vrmpcmwcmydrm8lauqdpngum4ne8xmkgc2d4rcaxrx7tkswdwzdu 's vision of what podcasting 2.0 could be but with music instead of podcasts. More of a movement I guess.
You can access the DeMu library of music via many apps like lnbeats, podcastguru, truefans, curiocaster, podverse, and fountain.
Music podcast shows will curate music for you. Accounts like nostr:nprofile1qqspdj6t8rlf5aytvcy0dfvkjyue9h79pyr9ynyrz8xnvz7yqg32h9qpz9mhxue69uhkummnw3ezuamfdejj76xfn5g nostr:nprofile1qqsvgj4kam4n5rjatjxc46p2ltgw89aal0yjqrta3lp7u99xn60hgrqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcprpmhxue69uhhyetvv9ujuen0w4h8gctfdchxvmf0c4zgsh nostr:nprofile1qqs9qzn25rmt82te2lwh5cucje0nw35snmaw47cxplyurmg8eg5cu9spz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgswaehxw309ahx7um5wghx6mmd9u9ydu77 nostr:nprofile1qqsp93q3znvsangpj0fqxmevg4xm689m9seejmfq2v7qkhxs8ayxeagpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctculxlv7 will often post notifications on nostr about new DeMu being uploaded throughout the week.
This feed is an example template XML file for decentralized music (Demu) releases. It is designed for artists to replace the file's contents with details from their own music project in order to make self-hosted value-for-value digital releases. This template is made available by the Wolf on a value-for-value basis for personal and commercial use. If you receive value from this template please consider raising the Wolf's value split share, which is defaulted to "1" in the podcast:value tags below. Since this is a v4v resource, it is acceptable to remove and/or customize the value splits for your own testing or trial purposes. However, if you do receive value from using this template and choose not to return that value, you run the risk of being exposed as a douchebag!
For the non techies following along, when we talk about an RSS feed, this is literally the raw dog file you get. If you look closely you'll see theres a lot of lines that might look similar in structure to this:
Its basically defining various fields - this one in particular defines who is the recipient of the zaps, the name of the recipient, their node address, their % split, etc.
Just like building a website you can either raw dog edit the html (the rss feed) or utilize a service like godaddy that has a visual builder (like podhome.fm ) that you fill out a regular web form and submit for them to build the feed for you.
Sir. You misunderstand me. I want to take Podstr and turn it into a decentralized music hosting app that uses this RSS feed template. So I'd have Podstr for podcasts and DeMustr for music. Same concept of app. Different style RSS document.
I know what you meant. We do need easy ways for people to built these feeds and host them. Nostr seems to fit with this. This is all meant to be selfhosted because we don't want to host anyone's stuff which is why we just provided the templates for everything and you have to figure out where to host it yourself but we can help. I've got test feeds right on GitHub which isn't ideal but there are just test feeds.
Any official DeMu forks will need the blessing of nostr:npub19ha7tju4teqp3dmwv4p28wrcy9zd6h6hxkg5mwvjrlfycweazpkse2q0fa
I'm excited to see what you come up, DRoss! π All that matters is that there are visible, unlimited value splits for any and all artists involved AND that the artist is able to maintain control of their feed.
nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9 had been called the nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr of PC 2.0 by people that know them both well
Outside of PWA support i dint think so? That said, I've uploaded before from my phone thru chrome and it was just fine. Some of the sites are also mobile optimized. I used RSSBlue in the past but they're merging services with fountain soon so it doesnt make sense to jump in there until after. There's other options though I'm less familiar with the various options.
For uploads? Dont think so. nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2 and the podcast guys would know better though.
For users, i think they all do except lnbeats which has a pwa.
Uploads right in the player app? Not that I know of but nostr:npub196qvw7utjs0cnztlg4aww98ekql9svm6c4wlv6sug70nzz0uujxsprafme makes cool RSS feeds from nostr post.
My favorite is lnbeats but its a pwa. Podcastguru is really good but its mostly for podcasts (in our case, the music podcasts which will curate songs on an hour long music show). It can be a little wonky finding specific tracks. Podverse is a good one but it's not great for discovering new music. Fountain is the cleanest, works well, and has lots of features. But I want to stick with promoting some smaller guys so we have more options.
Using rss for music is relatively new, much like nostr. But there are rss music native apps currently being coded. I know of at least 4 being developed right now.
Music apps are lacking. These are all podcast apps that have music which is why we need MORE APPS!!!
they all kind of suck tbh but LNBeats is great for finding just music, Fountain is also good but limited in its music playing features but if we bug nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 enough maybe he will make it better.
If im trying to discover new music my first goto are the curated music shows using podcastguru (like homegrown hits or nostr:nprofile1qqsfemtk0gvy23rpj4agywtzrfj4guka2n6wxnalwcl7p36sx6lmk0qpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsesx9ev). Or else I like to browse lnbeats for individual songs or artists. Ill often go there to find more by a new artist after I hear them on one of the music shows.
This. Make a new npub for music, only upload tracks. These become your podcast feed through Castr.me
The nostr:nprofile1qqs9e40cq5kx0y0ys70sundezdr96ugata07ps9tnyzfccryck3etgsppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgmwaehxw309amk7apwv3hhwmnfwdhkuargv46hqtnrvyhsvvve47 podcast feed for instance.
post the raw file to the nostr timeline and add the RSS Feed that castr.me gives you to a podcasting app. PodcastGuru handles these well and has video.
nostr:nprofile1qqsglv2qkn5dmmuhee9cy8fywfu2rfp4xd3xy0myqg2gfvmjl9yqqrqpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qye8cpd can you co firm?
If it doesnt work... can I zap you and pay for a month of nostr.build premium for nostr:nprofile1qqsp3yzapfwkyw4cr2vt4xx9s27474lj2pkxhqyfqh79n826pv3fkzqpzpmhxue69uhkummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcru0tqj?
WAV is also huge. At least use a lossless codec like FLAC. That will cut the size in half.
WAV will rape people's data plans, and most users won't notice the difference in quality. A high bitrate mp3 or AAC will be enough for 95% of users, and use 20% of the bandwidth.
Most music services serve multiple bitrate streams, so users can select the tradeoff they want, bandwidth vs quality.
They will compress it somehow. WAV is about 800 mb per hour. AAC is the standard now, rather than mp3 for most services that stream. It should be well supported on all devices.
But yeah, WAV is an archival format, that's what you want to save your tracks in. But for streaming it's not suitable, way too big. Longer loading times and 5-10x bandwidth usage.
You would link them the RSS feed, not the individual files. Then any podcast app can handle it. Or any of the DeMu apps that will be built in the future.
Its app specific. Pick a nice app you think theyll like, and as far as I know, all of them let you hit the share button for a link to either song or album.
MP3 has something called id3 for metadata. m4a (aac) file have similar tags embedded. Most apps that you compress with will give you the option to add these tags.
These apps should pull into straight from the audio track tags for DeMu. You could even add tags for lightning info in the file itself. Then tracks downloaded and shared could still have the info to pay the creator.
I've been waiting for this shit to start happening π
Video needs an upgrade too, with HLS support for more bitrates and formats.
Media is a tougher nut to crack than simple text notes. The storage and bandwidth requirements ramp up, plus needing to have more format options to support a broad range of devices and link speeds.
We have spoken with many industry giants and have several on-side supporting DeMu right now. One of them is a former head of digital transformation for yahoo music.
The ones who get it see that this can be a bigger disruption than Napster and this time the dice falls in favor of the artists.
So you 1. Create acct with podhome. 2. Set up an artist feed and upload the mp3 3. Fill in the fields and hit submit.
At this point your feed is now in the podcast index.
Podhome currently does not have nostr integration that I'm aware of. But you cam always grab the link off fountain or lnbeats and post that to nostr. A little manual but that's just for now. I think we've finally engaged the brilliant minds on nostr and if pc2.p starts seeing more nostriches using it and asking for nostr integrations, surely the market will respond.
I know many of the people out here in both camps will be pushing hard for nostr based upgrades. I think nostr has a lot to offer pc2.0 and take it next level
When I say your feed is in the podcast index, pragmatically what that means is you're track and all metadata has been published and pushed to any and all apps that are pc2.0 compliant and available for podcasters and listeners to download/stream/use in their own podcasts or music show. Immediately and automatically as it should be in this day and age. No middle man, no publishing company. Just self hosted and shared v4v.
Oh... sorry im getting lost in the hell thread I think. Paging nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2 ππ½
i'm lost too. People just share the link to the app they want people to use. Fountain and LNBeats are kind of the go to for music and I think that's what we're talking about but thb the Wavlake app is great.
we do have pod.link also that links to all podcasting apps. Why thats a number for the name idk. These links will have varying result based on how the app handles music but you WL music is on a RSS feed that these apps can use.
Uploading to wavlake will publish your music everywhere.
Uploading anywhere else will publish your music everywhere BUT wavlake.
Not to dredge this back up but its important to have historical context:
The whole "semi-walled garden" thing js the issue podcasters have with wavlake and are very confused why nostr bros still embrace it as fervently as they do when theres other more freedom and open protocol aligned alternatives that exist. Yes, they are less convenient, but from their perspective im hearing a lot of "wait, aren't you guys bitcoiners? Didn't think youd trade freedom for convenience. "
Its absolutely on the road map. nostr:nprofile1qqspdj6t8rlf5aytvcy0dfvkjyue9h79pyr9ynyrz8xnvz7yqg32h9qpz9mhxue69uhkummnw3ezuamfdejj76xfn5g and nostr:nprofile1qqs9qzn25rmt82te2lwh5cucje0nw35snmaw47cxplyurmg8eg5cu9spz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgswaehxw309ahx7um5wghx6mmd9u9ydu77 team are working on something like that
I know nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqppemhxue69uhkummn9ekx7mp0qy0hwumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jj7qg3waehxw309ahx7um5wgh8w6twv5hsleq7kw and nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2 and nostr:nprofile1qqs2p9fwkqd9vm4rqac0zvh87pqgt2k3l9csgks2jhc7wrxj89vwcmgpzpmhxue69uhkztnwdaejumr0dshszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctc8jlpr3 all have demu specific apps coming out. Not sure about hosting, I think they're more focused on streaming side and user experience. They can talk more specifically abt their projects tho.
So on those solutions, hosting would maybe need to be done elsewhere. Like nostr.build for example. It would be cool to have an all in one. Hosting included. Would make it easy for artists
Its not on his road map I guess, and thays fine. Do one thing and do it well. Excuse me sir, this isn't a microsoft. There are other road maps and projects.
It's not that we don't like Wavlake, it's that Wavlake's code makes it so the Wavlake player can only play Wavlake music. If Wavlake's player played all RSS based music, I'd probably recommend most people use Wavlake. They give you a wallet and hosting and charge you 10% of your sats. Unless you're making $100 a month on your music, you'd pay less with a 10% cut than you would with a different hosting company charging a monthly fee.
Because they don't play all RSS based music, they go against my values, but if that ever changes, I'll send more people to Wavlake.
Its like the custodial vs noncustodial lightning wallet debate. Do you run a full umbrel node? Or do you run zeus? Or are you using WoS.
To make the analogy, musicsideproject solution is like setting up an umbrel node, fountain or podhome are like running zeus and wavlake is sorta like WoS
I use all 3 of those node/wallet solutions. Just like I use wavlake sometimes. Like Derek says, it fills a need.
If you're looking for a turn key solution, a company like Wavlake that handles everything is exactly what you want.
Does Wavlake support your values?
Do you mind giving them a 10% cut in exchange for the service they provide?
If Wavlake works for you, use Wavlake, they're a great solution. But if you want more ownership, there's tools to do it yourself.
It's like changing your oil. If you know how to do it, you can choose to do it yourself or pay someone else because it's not worth the hassle. No shade with either decision.
Oh so podhome and fountain do the hosting too. Every person I spoke to gave me different answers about this. Im a bit confused. Iβll look into this. Thanks
ultimately, it's just a file sitting on a web server somewhere and you need someone to host that file for you. is it you? is it a company? what do they charge? what services do they offer along with hosting? think of it as a very specific type of website and you're buying webhosting for that very specific website.
I think the confusion is theres really two pieces of info being hosted. Your media files (audio and artwork) and your rss xml file (aka your rss feed/metadata)
Podhome is a hosting solution. Publishing is baked into the process by default.
Fountain (with their RSSBlue partnership) is an AiO solution and includes a player as well (just like wavlake)
There are others but I recommend looking at podhome first. There's lots of podcast hosting solutions and just a handful of ones catered specifically for music. Because RSS is open, there are certain standards but you can pick and choose what fields you actually utilize or even create your own as long as theres a compatible app that knows to reference it.
Exactly. We (Podhome.fm) ca host your music and podcasts and will distribute it to all the apps (we also have a listening app ourselves). Fountain hosting can also host and distribute your content.
Our goal is to make it super easy for you to just upload and distribute.
agree here 100%. some apps will exist for the soverign individual and some apps will exist as full fledged solutions where they do the work for their customer. not every human or creator fits in the same box, so we need a wide variety of solutions for all.
Yeah podcasters have solved hosting for themselves. Its a non issue on their end. Nostriches are just now finding demu so they have to build their stack. That would include getting hosting right.
I dont want to see all products with all the same features sets. It'll be nice to have an all in one solution but i certainly dont want every product to be that.
If you need a product, then build it. That or go on a rampage on nostr for an entire day getting nothing else done pther than creating a hell thread and bullying nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqppemhxue69uhkummn9ekx7mp0qy0hwumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jj7qg3waehxw309ahx7um5wgh8w6twv5hsleq7kw into doing it π
Yes this. This is what will decentralized thebhostingnpieve and allow nostr to jump on board. Pdocasters can also adopt itnor keep doing what they're doing. Free and open protocols FTW
Ok that said I think its important to also highlight i dont hate wavlake and I think without it, we wouldn't be standing here today. Thay said, I think we need more freedom of choice and I do think the wavlake product is flawed. I understand why it was built the way it was built when it was built, and I also understand why it cannot be upgraded on a technical/economic level. There's no animosity here. I'm just looking forward to the future and not sticking to safe know solutions ultimately holding us back.
Yes sharing is very easy. Any app you can stream demu from will have a share button that let's you copy a link. Most if not all will open in a browser.
Sorry tried to delete last note but idk if I caught it in time. Had an inaccuracy.
Yes, as far as I know, for all the apps (fountain lnbeats podverse etc) when you share a link, it opens in browser if you dont have the app. Lnbeats will allow you to install as a pwa. Fountain has its own app and I think podverse does too.
It might be worth pinging nostr:nprofile1qqsglv2qkn5dmmuhee9cy8fywfu2rfp4xd3xy0myqg2gfvmjl9yqqrqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0crg0k2 about this. Would podcasting/DeMu support be possible to add to nostr.build ? Having the largest Nostr media host involved could be a plus.
Lol this threads a bit of a novel at this point π€£
nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpzamhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6tcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qyghwumn8ghj7mn0wd68ytnhd9hx2tchypkm2 and nostr:nprofile1qqsgufllkhymhrxaqyc6meh05jw4d4qpk4pym87lnf37qax4y7c8zhqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhspn8459 are maybe the best two to speak with, they know what's going on with podcasting2.0 and Nostr integration.
How to Start a Hell Thread Without Starting a Hell Thread
Written By nostr:nprofile1qqsgufllkhymhrxaqyc6meh05jw4d4qpk4pym87lnf37qax4y7c8zhqq95zex and nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2
Haha, I think your comment got lost in the hell thread.
This is what I think is needed, anyone please correct me if I'm wrong.
πΉAudio uploading & optimization for streaming.
Musicians can upload their source files and have it converted to mp3 or m4a, possibly preserving the source files as well.
πΉAn RSS feed supporting podcasting 2.0
This lets the user add their songs easily to podcasting/demu apps. It would need a way to edit the metadata for the feed and the uploaded files.
Am I missing anything here nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpzamhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6tcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qyghwumn8ghj7mn0wd68ytnhd9hx2tchypkm2 nostr:nprofile1qqsgufllkhymhrxaqyc6meh05jw4d4qpk4pym87lnf37qax4y7c8zhqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhspn8459 ?
An auto conversion to mp3 would be amazing. Im weary of optimization sometimes... would it affect audio quality? That's first and foremost. I like the option to have it on or off like you have for the photo optimization.
The second one, nostr.build could certainly host rss files. Agree, the ability to edit is big but we would also need some way to push a notification that theres been a new feed created or an update. Its been done so the code is likely out there. The PC2.0 guys use a function called podping. I think they use it over IRC or something idk how it works but there are those around who might. Looking at nostr:nprofile1qqszxgvrzkpasudhvdjx3anl77qxse5wd6eunndmyv9x63uwnpn09mgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3e82efwvdhk6tcgt4a3x maybe?
Podping does use the hive blockchain to store podcasting 2.0 updates. It serves its purpose and has for years and even Fountain uses it to put data. It's a fast chain so it transmits the info in seconds.
nostr:npub13cnlldwfhwxd6qf34hnwlfya2m2qrd2zfk0alxnrup6d2fasw9wqxwkzpe there are several ways to trigger it and you've seen it fine in the irc but sovereignfeeds also has it built in.
The way I see it, if this "token" is providing a utility thats being used in the real world, then it has value. At the end of thebday its just another way of transmitting data. Maybe underlying architecture is ugly but it works and it works well. At least a bit less shitty than some other shitcoins ive stepped in before. How is this fundamentally any diff than sending a packet of data any other way? I'd maybe place it as shitcoiny as a stable coin or something idk.
Whatever, it works and no one thats using it for utility is trading the token as far as I know.
nostr:nprofile1qqs00y32ptdnlfxa5hhv4f30dalwv9vl0a27pqpkdpkx3cyrstp50zqpg3mhxue69uhnwumjwgmkx6revvm8vmrg0fcxxvngdsmxc7t4denhvmr4da585undwsmnv6mzwv6xkmtev358y7r0v94kkcn3w4skgtnvda3kzmqpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6qghwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx27prlx2 For those who are allergic, in the current existing ecosystem, is there a way to publish without using podping?
Nostr fixes this. Just push a note. Maybe someone can write a NIP that pushes a specific note that signals the index theres been an update and tells it whay to update (whatever data is previously transmitted stays the same. Same car different road). The index just watches for that specific NIP instead of podping
But we have such a tiny demand, I cannot possibly justify wasting another minute on things that are barely used. I spent a ton on analytics (almost unused), setting moderation headers (unused by any of the clients), and many other things just to have them not used with days/weeks of wasted time and money. I really do not see demand, we have so few people and so little usage of any βadvancedβ features.
There are a lot of features people look at and want but never use in reality.
A good chunk of nostr.land users don't even use the aggregator or claim their NIP-05 name even if they don't use it as the primary (the name will also be used for other things)
I dont disagree with this in that hosting solutions is a relatively small optimization in the overall workflow when we have larger fish to fry. But its worth a shot to set one thing in motion if it doesn't take away from other efforts elsewhere.
I guess that is true, but work like service/client integrations take time from both sides. Implementing podcasts in Nostr.build currently would have to take away time from more important improvements, while benefiting less users than those improvements
Yeah im not arguing for you to drop more important priorities and honestly I dont think nostr.build should implement podcasts, just support whats required on hosting. The rest is just fluff. Do one thing and do it well.
You guys host basically all of nostra media. Keep focusing on that. Bare min to get demu really going on nostr just needs you to support essential features like the ability to host audio files and rss files (which it does already)
My point in all this here is to show you guys theres a lot already in motion and the massive potential/untapped market. Your product sits in one of the essential corners of this ecosystem. Just heads up and house call to see if theres anything you guys can do to move this forward with us. If yes, cool, if not, maybe later. All good, this is freedom tech.
fwiw, there is already support for uploading MP3, (and for paid) WAV and FLAC, and the API can be easily used for thid
for reencoding audio, this can be done in browser efficiently, and this way creator can pick the lowest bitrate with good quality for their specific usecase
Many similar such efforts have been set in motion today. Remember the early days of nostr apps cranking out seemingly daily? Back when we were all bullshit on pablo?
I feel a similar bubbling beginning today in the demu space on nostr.
Currently hosting really isn't an issue in PC 2.0 and if no one wants to use Nostr then they won't be interested in Nostr.build either. We're not going full Nostr and I don't know how much we will add. The lightning wallet solutions Nostr provides are what we're after currently because that's what we need but building solutions for people to host content and build RSS feeds so apps can surface that content were game for.
I'm also not that familiar with Nostr.build but if we need a hosting service you'll be top of mind.
I think most people just host their media on their websites currently.
Podcasters are used to hosting their own stuff either on their own or using a hosting provider so that's all just transferred over to the music stuff as well since music is just an extension of PC 2.0.
People around here just stopped using Spotifys Anchor hosting for their podcast within the last years btw.
I think its important to recognize theres two important goals that are sort of intertwined as one begets the other so even if we have positive movement in only one direction, a high tide floats all boats.
1. Podcasters need an upgrade to the current feature set which nostr tech may be able to provide (relays, identity etc) while maintaining backwards compatibility
2. Nostriches need to start getting into demu! But the current implementations are largely incompatible with what nostr is using and moving towards (keysend vs lnurl/nwc).
While podcasters may not need a change in hosting solution, having a nostr native product thats already seamlessly integrated into nostr would be massive for achieving #2. Just like Dell computers shipped with windows, amythest and most other clients ship with nostr.build baked in as the default.
If we drive nostr adoption of demu, that is a huge untapped market thats already mostly on board and dont know it. The podcasters will see theres movement there and that its worth looking into again, driving more adoption or re-adoption. And that starts the flywheel.
There are two very similar ecosystems, connected initially only through usage of lightning payments via keysend... are colliding.
The podcasting 2.0 world realized they could selfhost music via rss and found lightning as a payment rail via keysend boosts. Whereas Nostr created lightning zaps and primarily uses lnurl today.
These two worlds are very similar and have very similar ethos but are using entirely different communication layers. Podcastinf 2.0 comes from the massive podcasting world thatbhas been amassing users for 25 years. They have been searching for solutions that I know nostr cam provide.
But its chicken or the egg. Which comes first? Without the tools, they won't come to nostr or care. So you don't hear the demand. But they are very much out there.
All that said, hosting is not the biggest issue right now. We need to come to a gentleman's agreement with the PC2.0 crowd as to how we somewhatbstandardize zaps/boosts and move fwd together as one larger community
And why am I so passionate on this? Because there are tens of thousands of insanely talented musicians out there struggling to eat because they have no proper meals of monetization without fear of censorship or rugpulls. Nostr + rss + bitcoin fixes this but only if all 3 are aligned. Many families and livelihoods depend on this. Real music culture depends on this (unless you like ai slop)... because the industry is dying fast.
Its all a lot bigger than just some features really.
Just to throw some extra work in there⦠some way of BUYING an mp3 or wav with sats would be cool.
βYouβll own nothing and youβll be happyβ I think Mr Nakamoto once saidβ¦ The day will come when Spotify rugs peoplesβ music collections and it will be moderately lol imo.
Since feeds are publicly hosted you can technically download them for free. That's just part of v4v.
The RSS spec also allows for a funding tag where you can essentially link a fiat payment rail like PayPal. But you cam also utilize it to link to a merch page or download my song for x sats webpage or whatever.
This thread could rival nostr:nprofile1qqsvlca5x9keq5e4km8q26aqas3skkr6xdpcr6ptlxsz5xz095rglrgpz4mhxue69uh5yetkduhxummnw3erztnrdakszyrhwden5te0dehhxarj9emkjmn9qyxhwumn8ghj7mn0wvhxcmmvurc4ss 's hell threads in length.
Speaking of, haven't seen her around in a long time. You alright girl???
DeMu a few years ago was still finding its feet and nostr had no idea about it outside of wavlake. Wavlake does hosting for you so there was no demand for it. But things have changed significantly since then. Decentralization and a demand for more self sovereign options is rising. With that comes the need for media hosting.
I believe nostr has only begun to open their eyes today.
