Finally a vibe-coded app that doesn't requests my public key 2-5 times!

I'm working on my @nprofile1q... client, improving the "People" section and I thought about you (saw your profile as I was scrolling), and the meme that vegans will always tell you up-front that you're vegan, came to my mind. I open your profile... and 20 hours ago, you just had to repeat it?

Once I had a colleague, months went by, we had lunch together plenty times... it was not until another colleague mentioned I was vegan, that he became aware.

I'm vegan too btw. 💜🥬🥗

Great! I have not implemented any timestamping yet, so I'll do whatever exists when I get around to add support for it.

I would also want to add waveform to this specification, same as voice messages.

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

It's part of the "imeta" tag though for this, but we could just call it "waveform" as a tag. I'm sure many would appreciate being able to add that.

For AI generated content it should maybe be:

["ai-generated", "true"]

Do this, because the first Music client that was implemented does this, and Nostria does the same now. Please don't do this differently as there is already many tracks like this.

OR... since the syntax on other items is "track_number", "sample_rate", it does not follow that "ai-generated" should be with dash and not underscore. So I guess we need to change this to "ai_generated" as suggested.

Doing "license name or URL" is not optimal. This requires a lot of logic on clients and there is no way to organize this properly.

The most commonly used licenses should be included in the NIP, so that apps use the same identifiers. Some clients might want to show different Creative Commons icons for the licenses and if this is different across clients, it will be trouble.

This is what Nostria has today:

All Rights Reserved, CC0 1.0, CC-BY 4.0, CC BY-SA 4.0, CC BY-ND 4.0, CC BY-NC 4.0, CC BY-NC-SA 4.0, CC BY-NC-ND 4.0

So license should instead of name and URL in same spot, it should be:

["license", "License Name", "URL"]

Maybe I also suggest adding some license regarding lyrics, how lyrics with timestamps should be formatted?

Do we really want to support both plain text and markdown for .content? That's a big difference in logic being applied to the content. I vote for plain text only, with a basic structure like already exists:

"Lyrics:
TEXT

Credits:
TEXT"

But with some additional details on how to do timestamps in the lyrics.

Thanks!

Updated and improve "People" section is incoming soon, with awesome lists management. Makes it easier to make custom lists of accounts, even having encrypted (private) lists so you can keep some privacy of who you "follow".

Amethyst will connect to all the relays the user has. @nprofile1q... will by default connect to 3 of them (and it optimizes selection), can be changed in settings.

I believe that user's should have all their data on all their relays, to help with scaling and distribution (data-safety), but users shouldn't be required to connect to all the relays just to get a "complete set of events".

Yepp, it's a white chapel on the top. Planning on hiking up there one day soon.

Do you see the church up there?

@nevent1qvz...

We need to make a joint decision on the licensing syntax, if to use .content like I did, or use tags for it. I don't have any preferences, just want us to do the same for the sake of our users.

Building high-quality software takes a lot of effort, even with AI. There are minute details and implementation challenges that AI can fix when guided, but it requires constant testing, verification and improvements to get to high quality software.

@nevent1qvz...

GM!