This argument make sense to you nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzemhxue69uhhyetvv9ujumn0wvh8xmmrd9skchd02dz?
I’m saying clients should start adding language tags to notes when they get published so clients could just request posts with a specific language from relays without having to do that parsing client side. I don’t buy the language bubble thing, right now we’re not cultivating users beyond English because we make it hard for people to find non-English language content.
Uso o Damus e ele traduz tudo automaticamente, mesmo assim vejo muitas postagens em português… está tão natural que não percebo mais a diferença, tenho que puxar da memória se quem estou respondendo é de meu país ou não! Está muito bom assim… o mundo já tem fronteiras demais!
A questão não é sobre barreiras mas sim sobre filtro. Achar usuários locais da mesma região, com a mesma cultura.
Não sei se isso é uma boa
I wish the translated notes didn’t show the original above it. It’s distracting and unnecessary.
Por outro lado é bom para identificar a origem
Language is more than just letter written differently. They also convey a culture, shared knowledge and very often they also connect people shared problems. For example what is happening in Brazil is quite a problem, people outside that region would be likely to care less or nothing, whereas the people around would try to help each other and +95% brazilians just speak portuguese, so they'd be bound to only want topics tagged with PT language. The tag doesn't even need to be added manually. Nowadays is fairly trivial to automatically recognize the language and add the tag.
I think a better option would be to be able to chose to separate posts for region, and an option in the clients that would automatically translate all foreign language posts to a chosen language.
I agree. And I have said so from the beginning. It was thought that language-specific relays might help, but that seems impractical in the short term. And we really need good onboarding and experience to create momentum.
Io mi sono rassegnato a scrivere in inglese da molto tempo. Addirittura ieri un italiano per chiedermi info in DM mi ha scritto in inglese pensando che fosse più appropriato. Fortunatamente su Amethyst c'è il traduttore (pessimo) di Google che mi aiuta, ma io per postare in inglese sono "costretto" ad usare esternamente DeepL per farmi capire.
Anche io scrivo solo in inglese, ma questo purtroppo porta un appiattimento linguistico e crea anche una barriera d'accesso non indifferente.
Però presumo che tu sappia comunque parlare e scrivere in inglese, io per mia ignoranza, non ne sono capace... Per fortuna ho santo DeepL
Penso che sia brutto comunicare in più lingue, ma sarebbe anche utile filtrare per lingua in quanto puoi filtrare in molti altri modi per scegliere cosa vuoi vedere e con chi vuoi parlare.
Che bello leggerti in italiano! 😍🫂 Sì sono d'accordo, sarebbe molto interessante filtrare i contenuti del proprio paese, secondo me aumenterebbe l'adozione di Nostr.
Nothing that requires the writing client and writing user to change works in nostr. You might as well just run a content tagger using NIP32 and make a client that filters by language code from the tagger.
Yeah, I’ve thought about standing up one for that, which is fine, and useful. But when we need cloud bots for Nostr to work, it’s a form of centralization. So while I’m happy to stand up a language labeling bot, hopefully it’s not so controversial as @Tagr-bot, it’s something I’d prefer clients did themselves. Similarly i’ve got notes for an update for NIP-02 so we can easily add tag differences in the list, making ‘new follows’ something clients can get without having to have a network bot crawling the nostrverse the way Nos and Primal do. I’m hoping to also update it so we have version history of the profile and lists events similar to how you’ve got edit history on other events @Vitor Pamplona.
They should just learn English