nostr:nevent1qvzqqqqqzspzq9lz3z0m5qgzr5zg5ylapwss3tf3cwpjv225vrppu6wy8750heg4qqsdtadu5384dw4hskny5jxpvf9te9pccfcj8ludr549t0e8px3a9sgmcnlt8

She posted another event with full YouTube video:

nostr:nevent1qvzqqqqqqypzq634npfz8rwfq2hdr8am76s9t7dt7gwpe2y3t5wyufl4phe09yxeqqs2k3xygahfjvn2qfxf3t3fwu2mgqzhjaknq0tuvyddnun7eutxqasnwveeu

Yes, we truly need a native podcast event.

https://youtu.be/D_8Pma1vHmw

nostr:nprofile1qqsdulkdrc5hdf4dktl6taxmsxnasykghdnf32sqmnc7w6km2hhav3g2kyjn9 has been working on DID support for Nostr, which would make any Nostr key pair pluggable into the DID/VC ecosystem.

I just read a blog post regarding the cost of moving social networks, and how Facebook integrated a "backdoor" into MySpace allowing users to migrate more easily back in the day. Mastodon did something similar when people started exit from Twitter, until they stopped it by closing down their APIs.

The bridge with Mastodon that nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhggpt7fy built works fairly well, it does increase the amount of content on Nostr.

You're pointing out a major issue though and there is no good solution to the situation.

Just a heads up, perhaps your two replies won't appear when the "Recovery" account event disappears. It's one of my test accounts that published with default expiration, sorry about that.

Let's give my friend Daniel some love and follows! Happy New Year everyone!

nostr:nevent1qvzqqqqqqypzpz5m055y4vf3g59g5duxec3skyjm3k4m2c36jks52av8qapgsqajqqsrnk669c5njpvx6yr73lfxte9ltw9n28f5yhhr80naxtc0v0axm6gkg9zaj

"Authenticator"

"Nostr Authenticator" would fly well with corporate environment. There is already Google Authenticator and Microsoft Authenticator.

Perhaps we should use imeta? Someone might start spamming music with bad album arts that user's would want to block and support blurring?

https://github.com/nostr-protocol/nips/blob/master/92.md

I implemented license similar to "Lyrics" and "Credits", it's just part of the content, parsed from the text there.

License:

NAME

URL (optional)

Not sure if we should add separate tags for this or not? No matter what we end up deciding as a group, I'll update the implementation.

Example:

License:

CC0 1.0

https://creativecommons.org/publicdomain/zero/1.0/

I think the service is great and its worked well for me. It's an efficient way to get new eyes on your content. Most notes that any of us write just ends up in the "nothingness" and that's fine, few of us say much meaningful anyway.

Thanks for onboarding more people! Unfortunately, remote signers don't have a quick and easy setup method. I would like to implement a way to scan QR code with private key, together with the other details like relays, into for example Amber and have it automatically setup everything. This is not part of the NIP though.

I have done the next best thing, add support for client initiated nostrconnect. Previously it only supported making connection string in remote signer first, now you can scan QR code presented by Nostria, to connect with for example Amber.

If you already have your account on Amber, it's now (when next update is released) super-smooth to login.

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.

https://mibo.eu.nostria.app/66582bebf5542942caf9701ac07a7b12588f012c4110651091189473b3ed39ad.webp

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 nostr:nprofile1qqsr7ydtkt3rtk3dfhd96m0t9ufrzu68df695099dz26r58kx2jz7sqhklsnt 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 nostr:nprofile1qqsdr0fnxvmn8hxyz8cwazfm8zu9yt7qmc38ll69nkvsgn8dnej4sxckxm0xe. 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 🤙

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?

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

nostr:naddr1qvzqqqy9tvpzq9lz3z0m5qgzr5zg5ylapwss3tf3cwpjv225vrppu6wy8750heg4qqwkjmnkd9ekjcnvv5kkxct8v4ej6vfhxcmrsvecxscnwdf4x5c3742s

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.

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.

https://mibo.eu.nostria.app/541c4c51ce85fa7dd774cefc1669c86e1cafa0c5c868abdcdd96cba1b590bb5a.mp4

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?

I can't delete a repost? Made a mistake and reposted something about compiling rust to wasm as alternative to JavaScript. I would never advise such a thing, learn JavaScript and stick to that. WASM was dead on arrival, unfortunately.

Available for testing? Would love to compare compatibility with Nostria.

Also: How does it resolve an inline article/note reference that does not contain a pubkey?

It's such a massive step backwards in user experience. Weird they let it happen, would never have happened with Steve Jobs still with us.

I built this service to discover profiles using the outbox model. It will first find the closest Discovery Relay, then query to find Relay List and finally connect to user relays to get the profile.

Then it links to different Nostr clients and remembers last used.

I will add additional "purple pages" relays later on when sync between them are fully working.

https://find.nostria.app/

The power of a decentralized and open protocol, where apps are built with compatibility in mind. Nostr FTW!

https://blossom.primal.net/a0b460afaaed14aa6eb32c45fa147bfbc241c46cf2e09c18e63e5ff79372d16d.mp4

When you say "global feed", you refer to "root" events?

Replies should be delivered to the OPs relays, so allowing writes by third parties should, in my opinion, be allowed. Yet that opens up for spam attacks on threads, but at least the global OP feed will be better.

Or is it something else you had in mind?

You have 11 relays defined, one of them is localhost. When I reply to you or send a DM, you expect "me" to publish that to all your 10 public available relays?

There is also an following list with 34 relays that you have published.

Where should I publish my events for your to see them? Randomly pick perhaps 3 of the 10 relays?

Does your paid relays allow me to write a reply to them? If I use The Outbox Model will I will be able publish to you?