Greasy Fork

Cool script, pretty extensive too. However it removes the click function on tweets to go to an individual tweet. Is it a bug? I tried disabling "enableContentClickEvent" in options, this did not work.

Sorry it took so long to reply. I barely check this due to an ongoing issue with my login that the admins are unable to figure out.

But that sounds like a bug not being able to disable the feature. What browser are you using? You should still be able to open the content by middle-clicking the post or clicking the timestamp.

Anyway, I have a huge update coming later today after I finish testing that could address any bugs that I've since fixed. It will also probably reset some of your custom settings.

also, open dev console while you're clicking the post to see if any errors are reported

well, found a bug. too late in the day to push the new version, so will push it out tomorrow barring no new issues

I am on Brave/Tampermonkey. Yes the timestamp still works. I found the part in the code where the settings variable is being read, and if I put a return there the click works again.

I have another question, I would like to use the language feature to hide non-english posts but it is a bit unclear to me how it all works. If I enable language score there are quite a bit of false flags, I assume that's what the score threshold is for. But if I enable hiding and check dev console, some tweets seem to be removed just based on user location? And other tweets which are clearly non-english are not hidden.

The language info with the color rating on tweets also seems kind of random whether it will or will not appear. I understand that the system is not perfect but atm it seems kinda random and I don't know if I can trust the hide feature. Is that just how it is right now or how can I set it up better?

The language feature is bugged on Twatter's end, and you can read about it in this script's details under the "Hide Non-English Content" section. However, the update I am hopefully pushing today will have a ton of new features, one of which will allow you to auto-inject 'lang:en' (or any language code) into every trend/search so that foreign languages are filtered out on the backend before they reach the client. As for how the posts are removed, the script checks the language code that comes from the API. If it's not 'en', it runs their usernames, bio, and post text through a language check for that language code and computes a confidence score. Also with this next update will be the ability to set your preferred language.

The color-coding was something I built for myself initially to remind me of when a post is too old to reply to (red background means it's very old). I plan on making color-coding user configurable in the future. For now, it's probably best to leave it disabled as the logic is largely hardcoded and arbitrary and the colors are probably considered aesthetically displeasing by most standards. Basically, if a post is > 8 hours old (oldPostHideAge), it gets bright red background, > 4 a darker red (oldPostAge).

I am on Brave/Tampermonkey. Yes the timestamp still works. I found the part in the code where the settings variable is being read, and if I put a return there the click works again.

Can you post a code block where you had to put this return? I've tested this extensively with Brave/Tampermonkey and haven't had any problems, but will fix any potential issues with this next release.

I figured out the content click event bug. It used to work, but then I moved the enableContentClickEvent property and never tested it with it re-enabled. I don't use TypeScript, just raw JS, so the old reference was just returning a nullish value. I will have this fixed in the upcoming update.

Thanks for the info and the update. Will check it out.

Click is fixed! For the other stuff, I'll have to play around with it a bit. It's pretty weird that Twitter doesn't have "show tweets in my languages" already, anyway. I understand this is tricky to for a script like this to just fix.

Yeah, they really need better language filtering options. Also, did your extension manager notify you of this update? I am trying to decide if I need to move away from the yyyy-mm-dd convention and switch to semantic versioning instead.

I'm not sure, sorry. Tampermonkey never gives me popups, I think everything auto-updates and I only check it if there is a problem. This time I installed your update via this site.