What if when your Nostr client translated a note it would also publish the translated version? Other users would benefit and we wouldn’t need to spend as much on translation services. Translated notes could include meta data like the language pair, provider, etc. cc @Vitor Pamplona @Fabian
It’d be great if clients tagged the language the post was in to start with. Would reduce overhead on a lot of translation requests.
We translate all notes. We also identify the language of each paragraph inside the note. We could publish those, but it's going to be a lot.
would it if the client checks if a translation already exists for that language?
We could. Maybe we could even get the user to vote if it is a good translation before sending out. 🤔
It would be handy if I could just block all posts not written in English. And a maybe a togglable Canadian filter.
Would the Canadian filter allow First Nations languages?
Damus offers a button to automatically translate
That's the point of dvms
Although don't have translation data, there are language classification data for kind1 notes in wss://nfrelay.app Can be fetched with filter: {"kinds":[9978],"#t":["nostr-language-classification"]} Currently it is in custom kind. It will be migrated into NIP-32 format in the future. Maybe, others can use that.
Seems like this would bloat relays no? I could be wrong but this seems better left to clients. How would the new translated note be verified correct? I’m not sure about other platforms, but apple platforms have built in on device translation api which costs nothing.
I think it would be better to use the local translation of the device, in iOS you can now select and request to translate with downloaded languages. Maybe use a button that activates this option if the user requires it, or also leave it on automatic.
Glad to hear iOS has offline translation support. But there's web clients and Android clients too.
Android has Google ML Kit for offline translations. https://developers.google.com/ml-kit/language/translation/android