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?
Discussion
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
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.
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.
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.
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 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.