We made a new spec. People can adopt them, we will help them do that if they want to. You guys are just mad we didn’t use your old spec—which didn’t have transcripts.

I’m done arguing with you. We will continue on just fine.

Reply to this note

Please Login to reply.

Discussion

im absolutely mad but it has nothing to do with me.

i'd be mad if you made a photos app and decided to use event kind 64 instad of 20, just because you wanted to add something that wasn't in the spec.

it's uneeded duplication of work and makes things harder for not only developers, but users too. nostr is confusing enough as it is with 6 different kinds of DMs. why do we need 2 different kinds of photos and 2 different kinds of voice messages?

Airchat is not the same thing as YakBak.

YakBak is a poor clone of Airchat that doesn’t have transcriptions.

you keep making this about you for some reason.

You’re the one who’s making it about you. I’m just trying to build this app in peace.

me: *makes half a dozen suggestions to work together to maintain interopoerabilty and compatability across 6 different apps*

you: *no im doing my own thing*

i am DEFINITELY making this all about me. yep.

These apps don’t have transcriptions. If we used that NIP, all the apps would hear Airchat posts without having transcriptions. That isn’t what Airchat is about, so we made a new NIP.

This about representing what Airchat is about, not me or anyone in particular. You never used Airchat and merely cloned it in a janky app, so you may not understand.

That's why they're different apps, they do things differently. Maybe other apps would have added support for the transcript tag, maybe they wouldn't but that's for them and their communities, no?

Others apps can add the Airchat NIP if they want to. Yes, that’s for them to decide.

Standards are different than apps. If we all make a standard then what's the point of even making it on nostr? Why not just use a private DB on a website and enable API access to your data?

transcripts could have literally been a second event. they don't even need to be included in the audio event. there are so many ways to do this lol

2 JSONs? That is computationally much slower…

i made several suggestions on how i felt that we could remedy this and work together. you told me you didn't want to each and every single time i tried to do so. i was very curteous and kind. i can't extend an olive branch forever. at some point you have to realize some people don't care about the things you care about and move on. good luck Colby!

Tell yourself whatever story you need to buddy 😂