Today we talked about search note15djknj3kh6szcj82pp6sm98vk3pw40fg8ajsx8mrpfg3zadyeqhqfmsl2n, what about language filtering (that can be a search params, too)? Nostr now is english centric, but with the progressive expansion a language filter will help newcomers to discover new content and raise the signal-noise ratio.

I found this PR about the matter https://github.com/nostr-protocol/nips/pull/182 by #[0] and I think the tag is the right approach, because can be used on other kind types, if needed.

Ideas?

Reply to this note

Please Login to reply.

Discussion

Anyone want to hire all the people that Elon fired and start building this stuff?

nah. just bc elon fired them doesn't make them valuable.

but they could build this stuff, no?

sure if you pay them cushy twitter salary

Also need wine on tap

perk hate is strong today

are you made at them or something?

no just being realistic

do you honestly think that because they lost their job at Twitter they can’t or won’t code anymore?

of course they will continue code. I just don't think their values align with nostr.

and what are everyone’s values that got laid off?

i mean we all agree twitter is broken right? not functionally, but incentives are broken. and I can't say i trust the people that built those broken incentives.

obviously I am generalizing and there are exceptions. but would trust someone who quit more than someone elon fired.

so if they weren’t principled enough to leave their job because of financial obligations they have been compromised?

maybe those people would be happy to work on nostr clients and be thankful that they don’t have to choose between a paycheck and a mission

as someone who has had to choose between paycheck and mission I might be super cynical at this point. my views are what they are.

just to be clear, i don't think ex twitter employees are bad people or 'compromised'. but they def put stability over values. as did I at one point.

principles are expensive

lots of gray areas in life

but for those that got let go from Twitter, the ones that supported more voices being heard and were against the censorship and government influence that was taking place, we should be reaching out to them to come work on nostr, existing clients, micro apps, and bounties.

i agree with you here. I just don't think the majority of fired twitter employees are in this camp. if they were the majority twitter wouldn't be where it is today.

I also think anyone that has shown this propensity should be recruited. not just fired twitter employees.

I think it would be better to focus on translation rather than filtering when it comes to language

what if people who speak a language other than english don't want garbage translations dominating their feed?

I think only english speakers would prefer what you are suggesting.

*los

**Estados Unidos

***!! (Do not have that keyboard)

Americanos necesitan practicar su Español...está terrible!

Actualmente, las personas en Estados Unidos necesitan practicar, en general.

de acuerdo. mi espanol esta terrible 😂😭

Well first of all, you only get translated notes if you connect to a translated relay

Second, relays that reject other languages are possible

Third, "Only English speakers would prefer what you are suggesting" is very ironic. I'm much more used to Americans complaining about Spanish.

first, relays wouldn't do translation clients would

second, yes and the language query parameter would help with that

third, I agree americans complain about spanish which is why they would prefer to just have it translated for them. but don't totally understand your point here

That clients would translate rather than relays is not a technical limitation and is rather entirely your assertion. I don't recommend it because memorization really does help with performance.

And my point on the third was that your assertion that only English speakers would prefer translated notes rather than language filtered notes was merely that it seemed to me to be a strange assertion to make.

That clients would translate rather than relays is not a technical limitation and is rather entirely your assertion. I don't recommend it because memorization really does help with performance.

And my point on the third was that your assertion that only English speakers would prefer translated notes rather than language filtered notes was merely that it seemed to me to be a strange assertion to make.

its less an assertion about english speakers and more an assertion about people who speak a dominant language.

if you speak a dominant language (and have a mono lingual culture) you are likely more ok with not being able to filter by language (and solely rely on translation)

Why? Your observation is not something I've seen. I've rather seen a dominant language get angry and yell at other language speakers to learn the dominant language and shoo away translation efforts.

sure this is definitely a thing, I agree. but not what i'm talking about.

rn on nostr most conversation is in english. who do you think would prioritize language query filters more, those speaking english or those speaking something else?

I’ve been playing around with creating a nostr client focus on Latin American users and would welcome the language filter. Any way to increase the signal to noise ratio for users is a welcomed improvements in my eyes. 🤙

You really don't have to do this at the client level. I mean sure, a client with relay defaults that reject other languages or something, but you don't have to use the users processing power and battery life to do sorting.

In any case at least we all agree on a language parameter for both of our use cases and the protocol level is all we really have to agree on.

having a languages query parameter would mean clients can query for only one language of notes and don't need any processing power for sorting notes by language....

yes at least it seems like we all agree on that point which is promising!

LOVE this tag.l and potential to use it as query param. I’d like to browse English, German, and Spanish nostr separately as I am less than fluent and have a hard time switching back and forth rapidly.

You still have to do

if lang == english

return note

else

#implicitely drop the note

But I guess the argument is supposed to be that this check for every single note relayed to the user isn't significant enough to have noticeable performance issues for the user....

no the argument is that every note relayed to the user would already have lang === english. bc the client uses '["#l","en"]' query filter which means relays only send back posts with language tag of english.

ugh filter would actually be '{"#l":["en"]}' or something

You're still performing a check.

yes but its less checks bc client receives less notes

Oh so we're still talking about relay filtering then and not actually client side filtering. Yeah alright memorization can help there then.

i'm talking about the same query filters that search for hashtag or event thread. relays would still hold all languages (unless they want to be a specialized relay). standard query filters from clients would query the posts the user wants.

I think it makes the most economic sense for there to be specialized relays specifically language specific relays, but there's nothing keeping both from existing (except that maybe nonspecialized relays might go broke or switch to being paid services but I think we're moving towards paid relays or friend hosted relays either way)

yes, hard to know what the future relay landscape will look like. I do agree that languages specific relays will be a thing. I also agree that people would likely want translation relays and such.

all i'm saying is language query filter is first step and good short term solution to jump start language specific feeds.

yeah i think it would be nice for users to have specific language feeds as well. or if multi lingual, have the ability to push one language to one relay for broadcasting, and another language to another relay

When you go to the internet to find things, do you really search for "italian things" or for the things that interest you?

I think this (mine) was a bad argument, but I have a better one now: why hasn't this language stuff ever been a problem on Twitter?

in twitter there is a tweet translation option which can be very helpful (it uses google services though)

It also has options for you preferred language, with the option to add multiple languages

What do these do?

I guess I assumed twitter has a lot of fancy algorithms for their curated content

Contents powered by algorithms + click to translate?

Contents are not powered by algorithms. They literally show stuff from people you follow. My timeline has most posts in English about Bitcoin, some posts in Portuguese from Brazilians, and sometimes Turkish, Italian and Russian from Bitcoin people that decided to interact with their fellow countrymen. I just skip these weird languages. Twitter does nothing to prevent me from seeing them.

it doesn't prevent it from your follows. it does prevent it from the twitter general content it seems. like if you sign up for new account and have no follows you will only see your own language.

I guess i think its higher signal if you can filter which language you see from your follows (especially if you normally skip those weird languages)

No usually. But if I enter a "space" with a lot of content I would like the option to filter by the languages I understand or because a specific lang is related to some contents/culture I'm interested in.

Metadata can be useful.

you've never used the google search feature that allows filtering by language?

No, I didn't know that existed, but I barely use Google these days. When I search in English I get results in English, when I search in Portuguese I get results in Portuguese.

#[0]