Are you sure you want to go to an external site to donate a monetary value?
WARNING: Some countries laws may supersede the payment processors policy such as the GDPR and PayPal. While it is highly appreciated to donate, please check with your countries privacy and identity laws regarding privacy of information first. Use at your utmost discretion.
This seems to be mostly working.
There are three unusual features of Baidu:
(1) The domain is not coded into the title link. Instead, the script needs to read the green text below the excerpt. Sometimes this text is incomplete and ends with "...". Since there is no convenient way for the script to learn the full domain, the script records the ... and will use that in matching the green text. Sometimes, you end up needing to block two different domains:
(2) Baidu removes the MutationObserver object, which is how scripts normally detect changes to the page, such as new results when you click page 2+. So the script needs to use an older technology that can slow down the site called a DOM mutation listener. There might be a better way to work around this, but this seems to work for now.
(3) When loading new results, Baidu removes the style rules and forms added by the script, so those need to be reinjected. This is why you currently cannot move the Manage Hiding button to the top or bottom on pages 2+ of your results. I will try to fix that later.
Please post feedback on how it works for you.
To monitor for changes in a page after loading, you can create a MutationObserver.
https://developer.mozilla.org/docs/Web/API/MutationObserver
If you need an example: https://greasyfork.org/en/scripts/17459-google-images-un-target-to-open-in-same-tab/code
Sorry, I just realized you were talking about a different script, so never mind on the link in my previous reply.
I haven't tested the script in any mobile browser. Is there a way to extract script error information, an error console of some kind?
You could try rolling the version back to 1.8.3 (before using asynchronous functions). This site doesn't keep old versions but you could try this link:
https://greasyfork.org/en/scripts/1682-google-hit-hider-by-domain-search-filter-block-sites?version=233081
If you are using Google image search, I have that features in a different script:
https://openuserjs.org/scripts/jscher2000/Google_Hit_Hider_by_Domain_(Search_Filter_Block_Sites)
Thanks. I don't know how I missed that. I found it easier to stop using GM_addStyle() across the board than to figure out function hoisting. New version posted.
Hi Marti, I think having it right there on the script edit page is a good idea, more convenient.
Your block list is stored in a SQLite database. Here's how you can extract it.
(1) Open an online SQLite database viewer such as: https://inloop.github.io/sqlite-viewer/
Keep this tab open because we are going to drag and drop a file onto it
(2) Open your currently active Firefox profile folder. This article has the steps: https://support.mozilla.org/kb/profiles-where-firefox-stores-user-data
Size this window so you can see the SQLite site behind it
(3) Double-click into the gm_scripts folder, then scroll down to the Google_Hit_Hider_by_Domain_(Search_Filter_Block_Sites).db file (sometimes the .db extension is not visible, but it will have a different icon from the folder of a similar name)
(4) Drag the database file onto the SQLite viewer page and it should immediately extract five data fields. The one you want is hideyhosts -- you can paste it into the Import panel of GHHbD running in Tampermonkey or Violentmonkey.
Oops, never mind. The left side has the info from the script; the Author Tools defaults to MIT regardless.
Hmm, script's page shows MIT despite:
// @license BSD-3-Clause
??
Hi Marti, the reason for the restriction was people stealing script metadata blocks on userscripts.org and replacing the script contents with FB account hijackers. Without a license violation, it wasn't obvious how to get those taken down. That kind of behavior hopefully is not occurring on this site.
Hi Marti, I saw the general announcement, thanks.
Hi Alain, I've got some of it built (web results, news results), but I keep discovering more little glitches as I go. Therefore, I don't think I'll finish it for a while. If you want to try the test version as it stands, I've posted it here: https://www.jeffersonscher.com/gm/beta/GHHbD_v1821_beta.user.js
It looks like someone has posted an issue on the script with similar symptoms: https://openuserjs.org/scripts/K-mikZ/%7BRocketPages%7D/issues/Rocketpages_no_Work
If there are no responses from issues posted on the script, you could try sending the author a message.
You could look at these (I haven't tried them myself):
https://openuserjs.org/scripts/RIC0H/RGL_Linkify_Main
https://greasyfork.org/en/scripts/2709-linkify-plus
For what it's worth, I use the copy/paste method. For the kind of changes I make, Github would be overkill. (Also, I'm hosting nearly all of the same scripts on Greasyfork, which has version comparison so I can use that for reference.)
One thing that might make this script more convenient for use on FB is a MutationObserver to watch for and modify new newsfeed content as it automatically loads into the page (usually triggered by scrolling). Or perhaps it could be on a timer with setInterval() if the performance is acceptable.
By the way, in case your URL has different parameters, this is the one I got:
http://www.nigma.ru/?s=tampermonkey+user+scripts&t=web&rg=t%3D0_c%3D%D0%A0%D0%BE%D1%81%D1%81%D0%B8%D1%8F_&rg_view=&yn=1&gl=1&rm=1&ms=1&yh=1&av=1&nm=1&lang=all&srt=0&sf=1
In order to extract your query terms, the script is looking for the first parameter: s=tampermonkey+user+scripts
Oh, you use it with www? That's an important detail because line 62 did not allow for that. Please see the updated version, 0.7.1.
Sure, look for a new version 0.7.
Okay, please try version 0.6 for yandex.ru
You could try this script:
https://openuserjs.org/scripts/jscher2000/Google_SERP_Keyword_Highlighter
It's a bit rough due to various things Google does with its matching (singular/plural, synonyms, etc.).
If you don't actually want all your matches yellow, edit line 20 to
var yellowonly = false;
I didn't build a whole array of colors, so if you have a lot of query terms, a lot of them will be yellow anyway.
It's a start. Someone can take it over and improve on it.
By the way, the matches in the cite (green URL) and in the snippet below it are bolded by Google, so it's easy to inject a style rule into the page to highlight those bolded terms.
If you use Stylish / userContent.css:
div.g cite b, div.g span.st em { background-color: #ff0 !important; }
If you prefer a userscript:
var r = "div.g cite b, div.g span.st em {background-color: #ff0 !important;}"; var s = document.createElement("style"); s.appendChild(document.createTextNode(r)); document.body.appendChild(s);
But real code would be required to highlight the matching words in the large headline, since Google does not mark those in any way.
Do you think you installed it from this site, or from the old userscripts.org?
I don't think these old scripts were necessarily compatible with Chrome/Tampermonkey but could be a starting point for someone wanting to write a new script for you:
Search Terms Highlighter
http://userscripts-mirror.org/scripts/show/53098
Google Keyword Highlight
http://userscripts-mirror.org/scripts/show/52033
How did you generate the screen shot? Is that what you have now? Add-on?