prove it!
Discussion
I use it more than anyone I know
& yes Iโm biased
all caps Iโm convinced ๐ธ 
wait what client r u using
bc it says I posted that 8 days ago
feeling like a time traveler rn
lol itโs because of the language, d is for minute๐ client is damus, I would prefer using in english but it automatically uses phone language. I couldnโt change it. cc: nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
Ohhhhhhhh maybe nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 can help with that!!
I think nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf localized these ๐ค that is confusing
not necessary but would be cool to choose app language different than device language. interestingly my settings page is half english 
Itโs working as expected. The half translations issue is likely due to either the Turkish translations being incomplete, or that we havenโt pulled them into the app build. Using a different language in Damus from your general iOS language preference is already supported out of the box by Apple.
iOS Settings > General > Language & Region. Ensure that English is also a preferred language, but it doesnโt necessarily have to be listed as the first one.
Then,
iOS Settings > Damus > Preferred Language > English.
is there an open-source github for all nostr translations?
new client gets developed -> can instantly use the existing translation library as a baseline
github repo*
that would also allow nostriches around the world to help with translations too
yep, and not just translate things client by client
exactly, I remember Turkish translations were completed few months ago by volunteers for another client. It saves effort and helps ecosystem to grow
In theory, that sounds nice, but in practice, itโs difficult to pull off. Most in-app strings are highly contextual. Client needs for user-facing strings can differ greatly. You canโt just piece different words together because languages have different grammatical rules. Depending on the clientโs platform or framework, the string format also differs. At best, we could have a glossary of common Nostr terms that translators can refer to, but itโll still have to be very manual to integrate them into the app and require handholding by translators who know the language.
English is already a preferred language but I didnโt realize app language preference would be in ios settings, thought it would be inside the app. Thank you so much, I was able to change it๐ nostr:npub1jk9h2jsa8hjmtm9qlcca942473gnyhuynz5rmgve0dlu6hpeazxqc3lqz7 is not a time traveler anymore