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.

Reply to this note

Please Login to reply.

Discussion

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.