Airchat on nostr. So cool. Well done @Colby Serpa
Thread
Login to reply
Replies ()
Wouldn’t have been possible without @Siphiwe's effort and your nostrdb codebase!
And @Terry Yiu's SDK. So thank you 🫡
UX is really good!
I’m glad it feels intuitive! We had to completely gut the old Airchat thread view to work with nostr and were inspired a bit by the Damus quote boxes. It’s a nice hybrid where we get all the view options. If you click on a post that has a quote box, it takes you to the connected thread view.
Just replied to you
We need push notifications so badly haha
@Colby Serpa @Siphiwe we’re running back Airchat? LFG! Diana will be so excited to hear that
Haha what’s up grin! Invite coming to your DMs.
I was just thinking about you guys. We’re missing so many of the OGs
Today’s my lucky day! I rarely check nostr but that’s about to change ig
Just explained how replies work, check your notifications. It’s neat
yeah I figured it out. seemed obvious in retrospect lol
Bringing the humanity back to technology. 🫂
View quoted note →
It's a shame that he decided to create a new spec and not be compatible with the other half a dozen apps that already existed. Interoperability would have been nice.
yaks were just audio right? Isn’t this transcribed audio?
What he's doing is something else
audio notes are different from transcriptions of notes.
Audio and transcripts. Which could have been amended to the existing NIP or added as a second event. That's how @fiatjaf and I plan on doing it. That was devs and users have choice. Now we have two audio NIPs that aren't compatible. It's like making a new NIP for pictures with a new tag when we already have kind:20.
Indeed, yaks NIP-A0 included the audio file blossom link in the content without transcriptions.
Kind1 has text in the content…
So we moved the audio file blossom link to the tags and placed the transcribed text in the content. It just makes sense.
The NIP will be released soon.
Yes but that's where he's tricking you. It's not just the transcript. The audio is a completely different NIP and event kind breaking interoperability.
Can’t the yak apps just pull down these ones and interop that way? It would be weird to see no transcriptions from yaks in airchat.
I guess yaks can’t reply to airchats because airchats wouldn’t know about them. hrmm. not sure how to make these compatible.
It’s impossible to make compatible unless yak apps enable transcriptions. Android doesn’t have good native transcriptions yet.
If a post in Airchat appears with no transcription, we will make sure it is blocked client-side.
Nostr is forked. ✌🏼
How you make them compatible is actually be interoperable by using the same event kind and then expanding upon it. But dude hates Nostr.
Who does the transcription on Airchat? It's really weird to make a client requirement to publish the audio together with the transcript.
What if I can't provide a transcription? Maybe I'll just leave it blank then? What if my transcription quality is awful?
i don't think so. it saves from downloading a bunch of unusable notes since airchat is not just an audio-only app. it's audio+text.
Transcriptions are all native on-device. It’s an iOS app.
phones have pretty good transcription apis these days, I would imagine @Colby Serpa is using device translation.
why is it a weird client requirement? it seems practical. having transcriptions that are asyncronously tacked on afterwards by others seems a lot more complicated and not reliable.
I haven't read any nip and I don't know what event type it's using. I don't have an iOS device.
Even for calls, I don't think Voistr and Noscall are interoperable.
How are they unusable? Besides the fact that the event kinds and structures are not compatible? If you're talking pure audio, how would an audio file not be compatible?
iOS 26 native transcriptions are great. iOS 25 and before fall back to whisper, which @franny was using earlier today. Whisper requires a bit slower speaking cadence.
If transcriptions are bad, no one will read your post. Or they will eventually unfollow you.
because audio is optional. you can read the trascribed notes if you have audio playback off.
ideally the transcription is covered by the publishers signature, so they have a chance to edit it.
you could in theory make them compatible by having the device do transcriptions on untranscribed notes that are incoming... but that would use a lot of cpu
Let me get this straight. Earlier this week you said it was bad for clients to do this when I suggested this. Now you're saying you'd do this. So which is it then? Will you change tomorrow?
Derek stop putting words in my mouth. I’m done entertaining your attacks on me. YakBak was a clone of Airchat you told me FFS. You should be happy Airchat is here. How many people are even using YakBak daily?
But the event still contains the audio. It's only optional to the user. I told him this can all be fixed via client kung fu but he didn't want that.
I'm not putting words in your mouth. You can reread our chat history.
you can use interleaving specs. when you add transcriptions you can publish them as airchats.
this is no different than what we have on nostr with interleaved DM and thread specs.
to say he hates nostr is a bit strong, what he is doing is technically the correct way to do it. i don't understand the beef here.
How many people are even using YakBak daily?
I don’t get the beef either. He can easily add the Airchat NIP and support both. It’s a pretty simple JSON. We built this on no funding and really don’t want to be attacked for no reason.
The outside world of centralized charlatans should be our enemy, not each other. What’s truly ironic is the fight broke out on a post where I said “I get in less fights on Airchat” lol.
The beef is not being interoperable with the half a dozen other existing apps.
because its not the same app!
i don't see it that way. i see it as a picture focused apps, all using kind:20. some apps show blurhash and location data. some don't. some just show the image and that's it. they don't all have to show the same tags, but the underlying structure they all use is the same. some decide to omit some tags, some decide to show some tags.
I guess we just have a different way of looking at nostr I guess. if a dev doesn’t want to be interoperable with existing stuff because it makes their app experience worse then that is their right. nostr is anarchy.
i can agree there. my views are to make as many pieces of the nostr puzzle compatible to show how powerful interoperability can be for users when switching apps and using different apps. this showcases the power of a protocol.
sorry man. i tried to work with you on this many, many times. the bridge is burnt.
Ok, so be it. No need to keep attacking the posts then!
Also these "half a dozen other apps", the total number of people that actually use them regularly would fit into a photo booth. All this fuss over interop for apps that don't have users. Who's supposed to be doing the interop-ing?
the solution would just to disconnect it from real world currency, earn it in-game to spend it in-game
We really need a gif for armpit farts.