Nostr Web Client

nostr:nevent1qqsrs62lxnr84ltkmn9e2frnq3cea45arkja9pjuvylll84hk4ym7hgpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3q3cnlldwfhwxd6qf34hnwlfya2m2qrd2zfk0alxnrup6d2fasw9wqxpqqqqqqz3l8rmf

10k sats for anyone posting their castr.me links. Already paid one out. Wallets burning, hit me with more.

Not a paid shill and I have nothing to do with the project outside of thinking its awesome and wanting ppl to use it more.

Reply to this note

Please Login to reply.

Discussion

Did you just DoS the castr.me thing? It worked fine until, well, now 😅

https://castr.me/npub18ug6hvhzxhdz6nw6t4k7ktcjx9e5w6n5tg7226y458g0vv4y9aqq3r20ex/rss.xml

Anyways, this my nostr:nprofile1qqszaqx80w9eg8uf39l527h8znumq0jcxdav2h0kdgwy08e3p87wfrgpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcke6zfw link... when it works..

in that mess of random media there are casual sketches and rare bangers, but mostly mess. so much leaner to drop an audio file to the blossom via à nostr client than creating the xml with urls from the server. But why not do both?

Everything, everywhere, all at once!

Paid brotha! Keep on doing the thing you do

I want to see a nostr client integrate castr.me or something similar so uploading an audio file via a nostr client like you describe, automatically throws it into an rss. Maybe a special upload button or something so it knows to trigger the magic RSSifyer.

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9u2mk7fe what's it take to do something like this?

First of all, GM and big fanx!

nostr:nprofile1qqsd84stz259v3qu8f7nwd83u5rt5cvth65y08jh8kqzm8k4lfhnfjsprpmhxue69uhhyetvv9ujuem909ek2u3wve6kuep0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmp0swp3m4 handles audiofiles ialrightish and amethyst is good at interpreting ID3 tags: if you add an image to your metadata, it renders it.

I really wish there was a kind for audio, like there is for media posts. But we'll get there I am sure. Something that would encourage entering metadata. Ideally the client would write this metadata to the audio file too, because that's my biggest grief with homegrown audio on internet: you find an absolute gem on some artist profile or feed, you save it, but your forget about it. The file rests in your download folder for a good year. And suddenly you find again. It's an absolute mega hit that's gotten even better by just resting, but the file name is:

"scumpypumpy-version6-final-masterV67-FINAL-thistimeforREAL.mp3"

And the tags are empty, and now I can only cry my eyes dry because there is no way to know where to send all my love, admiration and sats...

Hit me with that scrumpypumpy v67 lolllllllll

https://tortellino.basspistol.org/3ac113bd2e2986b21f88cd4eb7e07c1677928d3caf2d3595bde8cfff76fdf06b.mp3

This is my biggest case, still unresolved. Dates back to myspace circa 2005. At the time i was booking for the local chiptune club. The file is renamed, but still unsure who made it. I suspect it is The 486 kid, who now goes by another name. But they've never answered my queries.

I'm still hoping to find the author some day. This banger's been cheering me up for nearly 20 years.

Got an idea... nostr:nprofile1qqspdj6t8rlf5aytvcy0dfvkjyue9h79pyr9ynyrz8xnvz7yqg32h9qpz9mhxue69uhkummnw3ezuamfdejj76xfn5g will DM u

inpc 3mo ago

Wait until you hear scumpypumpy-version6-final-masterV67-FINAL-thistimeforREAL-V2!

inpc 3mo ago

The additional 0.5dB boost of hi-hats is a total game changer.

Writing the metadata to the audio file id imagine would have to happen at the upload host (really the person uploading neess to so it). So thats something nostr.build or the likes would have to implement. DeMu isn't big enough for them to do that... and at least they do already support audio uploads.

i think it could happen at the blossom level, but more likely to happen at client level. If i was building a client for audio on nostr, i would do it client side to maximize compatibility with existing blossoms. And there are plenty of libraries that handle that.

Ryan 3mo ago

Yeah writing id3 tags is trivial. That's been a standard for 20 years. You could even add custom tags for payment info, so the files could still send zaps to the artist if shared by other people.

Can someone vibe code an audio metadata encoding app thats built for demu specifically? One that writes custom tags that follow PC2.0 spec and whatever else we come up with. Would be cool if there was a bot... write a note with /tags:variables and the file... it then and writes the metadata and uploads the new file. Then it connects with castr.me and loads it all into a feed.

Interesting. Where have been ways of baking chapters into mp3 for ever but I don't know it it really took off. The problem is that one change and you have to rebake the mp3. I think that's similar to what nostr:npub1m64hnkh6rs47fd9x6wk2zdtmdj4qkazt734d22d94ery9zzhne5qw9uaks is talking about.

I think it's over kill and makes it hard to change stuff in the future because you will mess stuff up.

This is why castr just pulling info from the npubs feed is nice. You could just put metadata in those post that castr could pull out when it builds the feed.

One thing that PC 2.0 isn't a fan of with Nostr is that it's hard to change the info after the notes are made.

All the signing stuff is cool until you need to fix something. Is there a way to post a new note or something? Idk

Putting metadata in tags in Nostr post is what fountain is doing btw.

Given by "rebake" you mean reencode, there is no need to reencode the mp3 if you change id3 tags. It's all in the header of the file. A very good one i use since long back and probably the best one at respecting the standard AND allowing custom fields is kid3. IT is cross platform and has a cli-version.

https://kid3.kde.org/

Cool it's different then the chapter stuff the.

What kind of data can be added to them?

Castr.me could read those and if there is an equivalent PC 2.0 it could just stick that info in there and podcasting apps could pick it up.

that script i am working on is supposed to do something like that, basically take all the id3 tag and render an xml from it, through some hoops and hops. So it's very dooable. id3 can contain all sorts of encoding like UTF-8 etc... but also picture data (base64 if recall correctly) I'd venture out and say you can add pretty much anything in custom fields, i have a dusty todo list somewhere with an item that says something like "try put another mp3 inside the id3 of an mp3" :D but i haven't gotten around it yet.

you've got working 2.0 feeds already so you know what it needs to look like to work in apps.

You can cram anything in a feed and you just need an app to know what to do with it.

The feed is the source of truth after all.

what do you mean when it works? Just manually add that to a podcast app and you should be good.

His looks different like the raw rss feed. Compared with the one nostr:nprofile1qqs9e40cq5kx0y0ys70sundezdr96ugata07ps9tnyzfccryck3etgsppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgmwaehxw309amk7apwv3hhwmnfwdhkuargv46hqtnrvyhsvvve47 posted, that link looks like a clean nostr feed. The error at the top seems tmsome style xml is missing?

https://castr.me/npub18ug6hvhzxhdz6nw6t4k7ktcjx9e5w6n5tg7226y458g0vv4y9aqq3r20ex

so this is the link to his castr.me page

This is the RSS feed from that page

https://castr.me/npub18ug6hvhzxhdz6nw6t4k7ktcjx9e5w6n5tg7226y458g0vv4y9aqq3r20ex/rss.xml

The difference is the /rss.xlm.

anything that ends in .xml is a RSS feed