How should I approach multilingual content here? I sometimes want to share an article that is in Czech or slovak language.

My options are: prefix the post with CZSK or flag emoticons or create a new account.

I don't want to bother people who don't understand the language with content they don't understand, but maintaining two accounts is a bother for me. Most clients don't support switching of accounts and also people who follow my English account don't necessarily know about the other account.

More systematic solutions would be:

A. mark the note language while writing (client can autodetect and suggest) and include it in the note as metadata. Clients could support setting languages I speak and show me only content in those languages

B. Do it on the viewer side. Detect languages of notes and show me only those I understand. Alternatively, attempt machine translation automatically

C. Don't stress too much, occasional weird language in the feed does not matter.

Opinions? nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1plstrz6dhu8q4fq0e4rjpxe2fxe5x87y2w6xpm70gh9qh5tt66kqkgkx8j nostr:npub1eqmj85el4pkg7qdj2jcae24qykev5evnyz2s6pzdytzpkhga4u5sdmhexk nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk

Reply to this note

Please Login to reply.

Discussion

English translation of the title or tldr together with the original link seems elegant to me.

What about accounts that only speak different language and the reposts?

Many posts are not relevant in English. For example new tax law for crypto in Slovakia should be most probably ignored by anyone who does not speak the language.

Who should do the tldr? When i post in czsk, I do it precisely because it is relevant only to the speakers of the language and I don't want to waste my time with writing English tldr, nor the time of my followers by getting irrelevant content.

A translate option like twitter has sure would be good, for reposts at least. But everything else, even the new tax laws news are interresting for wider audinece.

A. might be good to show separate feeds for (preferred) languages.

B. Amethyst does that already (sometimes it's funny when it "detects" languages and translate from original lang to the same one with incorrect assumptions)

For every non-english link you post, you could also add a link to a translated version.

Currently you have to do this manually, but perhaps this process could be automated, so that when you share an article in Slovak, your #nostr client automatically attaches a generated link to the English translation from Google.

So basically a variation of your B idea.

I don't want to do it manually and also the content is usually not relevant to non slovak speakers.

Itโ€™s not about language only. Context (local knowledge) matters too. In other words most of my Czech posts are irrelevant for foreigners

We live in a world with advancing language models, automatic translations are better and better. We don't need to worry about this too much. English of course is the lingua franca, but if I care enough I will happily read an automatic translation provided by the client/app, and If I don't that is my choice /intellectual laziness, not your problem. IMHO :-)

Having the same issue

note1klsnz2840shv5200gn5qvmtu09ma7v0ts9g4lv983jdrz5yhkwqqxacwwe

nostr:note1klsnz2840shv5200gn5qvmtu09ma7v0ts9g4lv983jdrz5yhkwqqxacwwe

Amethyst automatically translates some posts for me. It also has a convenient account switching feature.

Relay-based filtering: send your Czech posts to relays that only do Czech language and vice-versa. It's not easily doable today, but I believe this is the only approach that can work.

Modules, plebs using the modules they need. Segment the fuck out of everything. (Excuse my French)

Yeah, that is one of the main plans we have in Plebstr ๐Ÿ˜ ๐Ÿ‡ฌ๐Ÿ‡ง๐Ÿ‡จ๐Ÿ‡ฟ

This is very good to hear.

Why not include lang as a property in the note?

It's more work and more data for everybody, and no one will trust the property value anyway because it will often be wrong.

Don't overly complicate it. I don't think you have to preface the language. If the person is interested, they will translate it otherwise they will skip.

I go with C and it works just fine.

I think that mastodon is doing option a) at least instance which I am using.

In account configuration I can select multiple prefered languages.

C. Simple.

Most commonly I have seen this solved as separate accounts.

I've had similar thoughts, but seems to be overthinking in the end. If mixed language becomes an issue, nostr clients will implement a solution.

I like the solution B. I think the machine translation is getting more and more cappable and we are coming close to the state where you can see all the posts in you language without knowing itโ€™s been translated.

On device translation is coming to plebstr Btw ๐Ÿ˜Š

Whisper model? ๐Ÿ˜‰