Chapters? Nostria implements the Voice Message NIP, allowing you to record 60 second voice messages. When these are made, they include waveforms. Could potentially extend the music NIP to use the exact same tags for music waveforms?

Should turn that into a wallpaper 🤙

Blossom Servers are very basic binary file storage endpoints. The protocol allows you to mirror your files across multiple servers. Then when you create any event on Nostr, depending on which client you use, the client will include URL to all your mirrored copies of your files. So, let's say someone comes across your 2-year-old Nostr event, and they first Blossom server is long dead, it might still work if the second or third Blossom server is still running. Great for uploading and storing podcasts, music, etc. They can also transcode uploaded videos to smaller sizes, or photographs.

The content needs to integrate with Nostr somehow and rely on Nostr-native mechanisms for zapping. That will at least set content creators up for a good start, then what is left is getting exposure. Creators can pay for exposure and the more content we got on Nostr, the more people will come. We got a lot of content, but it's still not enough.

I have thought about "Podcast Studio" type of functionality earlier, main issue is that the "podcast protocol" for Nostr is not really decided. There are many different ideas, but I don't know if anything is ready yet. I just made a YouTube viewer, which uses Bookmark Sets, there is also a Playlist editor built into Nostria, which could be used for podcasts, but it's not a fully featured thing.

Need a way to discover the content that exists on Wavlake, using Nostr event. Does that exists? There could perhaps be an Nostr account that would publish events, perhaps a replaceable event, that has external link to the RSS feeds. Then Nostr clients could discover this content and allow consumption within the apps. I see in the Wavlake RSS feed there is lightning splits there, I might add some kind of support for that sometime later.

It will be same codebase on mobile and desktop yes. There is still a bunch of tweaks to be done to optimize the mobile experience. Thanks for trying it out and giving feedback! I'll get Zapstore done tonight!

Each individual event, you want to be able to collapse it down to much smaller size and just show the beginning of the text? That would be pretty neat, right? Or do you want to collapse the indentation in the thread so it's all flat?

Which Nostr client? It loads in Nostria if I just open in inkognito mode.

These are the playlists that appear to me, all of them have "public" set to true. Perhaps you have more playlists that this, some that is not public? Even if they are set to "private", they will be public on relays. The music NIP doesn't say anything about encrypted playlists.

Web apps are just as "real nostr clients" as any other app. They all requires servers one way or another, and if a relay doesn't update their certificate, no data will flow, no matter if your app is deployed from a centralized corporate approval system (Play Store/App Store), that can wipe your app off the earth by will, or if your app is downloaded from a git repo or web server to be installable, or if it's retrieved using web technology. There is also a big difference between a client web app and server web app. Any server web app has an online dependency. Any client web app is just like any other native app, just using web tech for rendering.

Thanks! As also mentions, it's more for podcasts and I don't think this music NIP should be extended too much, especially not into the podcasting realm. There are multiple threads on GitHub regarding podcasting and I would love to extend the podcasting features on . You can paste any podcast RSS URL into the search input and it will queue up everything. It has features such as remembering location, so you'll be able to jump back where you last stopped. Some people want to replace RSS feeds, other's believe it's an unwinnable battle. I'll experiment and see where the future takes us.

URL's with ' in the value didn't render properly, fixed it so now it works 🤙

I made my first music album, Invisible Cages! I might extend it with a tune or two more, please enjoy!

I would like to get some feedback on how you as artists, would like to have the license shown and displayed through the music section. Do you want it visible in listing on a playlist? Is it OK to just display on track details? When clicking "Download" on the file, do you want an informational dialog regarding the license, which I've seen on other sites? Maybe share some links for inspiration? I'm not a musician, but I do know CC and licensing in general pretty well.

Here is my suggested format of content field, it's how I've implemented it in Nostria:

Might I suggest we follow the pattern of text structure in .content field for license and don't add another tag? There are no existent concept of license in tags in any Nostra event and we already have clients that does "Credits:" and "Lyrics:". So I suggest we parse license from the text content: "License: Creative Commons CC0" It means you can't query for a license with the relay. Also if we wanted to do indexing, license names would need to be standardized.