Google Translate webpage translation borking because of weird on-spot generated domains
Posted: Thu Jan 14, 2021 2:44 am
You used to be able to open up a website link through google translate just fine with just allowing the base domain of translate.google.com, but for some time now whenever attempting to load a webpage, it gives a string-of-characters domain name, like the most recent one I've tried to load, "tbshb7dpq5ofwiys2oa44caota--www-nintendo-town-fr.translate.goog", that has to be manually and separately whitelisted every time that page is visited in google translate, as the gibberish code at the start changes every iteration. Unfortunately, it's not linked to any other domains, not even translate.google.com, so it doesn't read my whitelist preferences at all, and ever since the 2017 NoScript 10 update, there's no way to manually add an item to the whitelist only search for a reference in the per-site permissions as far I can see, so I can't just add "*.translate.goog" as an item to allow it. I tried searching for anyone else posting about this but found nothing, so I'm wondering if just no one uses that functionality or something like that.
So, with all that said... how can I fix this so it works properly like it used to? How can I add "*translate.goog" to my whitelist so that I stop having to whitelist it EVERY time I want it to translate a webpage for me?
So, with all that said... how can I fix this so it works properly like it used to? How can I add "*translate.goog" to my whitelist so that I stop having to whitelist it EVERY time I want it to translate a webpage for me?