Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Booleanize language filtering by feed #1074

Open
skunecuscre1 opened this issue Jul 29, 2023 · 6 comments
Open

Booleanize language filtering by feed #1074

skunecuscre1 opened this issue Jul 29, 2023 · 6 comments
Labels
feature-request A request for a new feature x:on-the-roadmap We're planning to do this but it may be a bit

Comments

@skunecuscre1
Copy link

Currently, language filtering (as far as i can tell) applies to every feed indiscriminately.

The issue with this is that for some feeds (such as fan-art feeds) I would like to see content by users even if its in a language I do not speak, whereas for others (such as what's hot) I'd only like to see content in my languages.

My proposed solution is to have every feed send a boolean which if set to true will tell the client to override language filtering. The default value should be false.

@skunecuscre1 skunecuscre1 added the feature-request A request for a new feature label Jul 29, 2023
@SenpaiSharp
Copy link

This isn't my ideal solution but it would probably be sufficient so I want to second it.

I run a feed that you would expect any language in but specifies English/Japanese/Korean in the title and description. I try to write pinned posts to the feed reminding people to turn off their language filtering, particularly Japanese and Korean users who are most often the ones unaware of the setting. Even if I write an explanation posts that covers all 3 languages and pick all 3 languages in the post options, it almost never gets picked up by all 3. Meaning the people who need to see it the most aren't going to unless I write 3 different posts that I have to clog my feed up with.

Personally, I don't really see what the content language options are really accomplishing to begin with but an option for a feed to opt-out would be at least preferable. Nobody is going into my feed not expecting multiple languages.

@skunecuscre1
Copy link
Author

Personally, I don't really see what the content language options are really accomplishing to begin with but an option for a feed to opt-out would be at least preferable. Nobody is going into my feed not expecting multiple languages.

I think language filtering can be useful for some feeds (most people probably only wanna see languages they understand in what's hot for example) but it's currently far, far too restrictive to the point it's causing more harm than good.

I also keep seeing bilingual artists posting in english but having their posts get hidden because the ML model thinks its their other language for some reason. Not ideal.

@pfrazee pfrazee added the x:on-the-roadmap We're planning to do this but it may be a bit label Aug 2, 2023
@pfrazee
Copy link
Collaborator

pfrazee commented Aug 2, 2023

I'm +1 to this, we'll also want it for moderation settings.

@redsolver
Copy link

I'm getting complaints from SkyFeed users all the time that their published custom feeds are missing some posts. In almost all cases, this is caused by the content language filter settings in the official Bluesky app. In addition to letting custom feeds specify if they should be language-filtered, I would suggest these improvements:

  • When posts are hidden from a feed due to content language filter settings, show a little banner at the top of the feed and an option to show them
  • When setting up a new account, ask users if their content language settings are correct

So overall users should be made more aware that the language filter system exists and how it works

@SenpaiSharp
Copy link

With the deluge of new users from non-English speaking parts of the world, this is about 10-fold more frustrating than it already was. Requesting escalation.

@robpc
Copy link

robpc commented Oct 10, 2024

When I first saw the section on "Language handling" in the Starter Guide, my hope was the Content-Language response header would serve that purpose.

If language filtering is applied, the feed generator should use the the Content-Language response header indicating the parsed language codes.

In my mind, since the presence of the Content-Language response header tells the client that the server had handled the filtering as appropriate for that feed, then the client should not do additional filtering if it is compatible with the request. If it was missing or didn't fit the request, then the client would do it's own filtering. As it is now, I am not sure that the response header serves a purpose. I think this would be fairly backwards-compatible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A request for a new feature x:on-the-roadmap We're planning to do this but it may be a bit
Projects
None yet
Development

No branches or pull requests

5 participants