Nostr Web Client

#devstr question

Why should I not change all publishing of Picture/Olas events in Nostur from kind 20 to kind 1 with k-tag 20. And same question with Yak/Voice Messages from 1222 to kind 1 with k-tag 1222

Seems better for network effect and backwards compatibility, what am I missing?

Niel Liesmons 4mo ago 💬 1

For Voice/Audio it comes down more to what you think should be part of Nostr short form text stuff.

Imo, any short form text, and thus all of these, can have audio files in them:

- Kind 1

- Kind 1111

- Kind 9

Reply to this note

Please Login to reply.

Discussion

Gigi 4mo ago 💬 1

Are there any clients that focus on audio only? Like: display only audio posts and ignore everything else?

Niel Liesmons 4mo ago

Like only get the the audio from kind 1s, kind 1111s, etc... ?

👉 I don't get the use case for this.

Or apps build around the Audio track events (31337 and 31338) ?

Or apps like YakBak ?

👉 I again don't see the use case. Especially if you then promote new kinds like that to be included in text based Twitter clones.

Organizing everything per content type is silly to me anyway, so I don't get the question I think.

The audio app I do need is a long form one that can take in Articles, Pods, YouTube, ... and let me handle one queue for all of them combined. Let's me highlight in text when I open up my phone, let's me comment in text or voice, etc...