A user script that assists in finding open directories with Google.
@Azazello !!!! This is amazing! Sorry for the late reply. Greasyfork strangely didn't gave me any notifications of this.. I'm afraid it won't do so in the future either (unless I get something like Tapatalk maybe). I'm at work, but I'll give you feedback on all the points you mentioned once I get home. Are you on GitHub? Can we take the discussion to GitHub? If so, paste the whole thing into a new issue there.
Talk to you soon!
Also: what do you mean by 'P...zilla'? Pron? I wouldn't mind if that the case...
Sorry for the late reply.
No problem, no worry, no rush.
I'm not on GitHub because I'm not a developer, haha, or a frequent user of apps from there. Yeah-yeah, I know: everybody and his grandma is on there, but I'll wait til I get more incentive to join.
For general discussion, I hope you don't mind having it here. Plus I hope more people will join in.
(btw-- Everyone, please flag the idiot spammer above, so his/her posts can be deleted from GF.)
Don't mind at all
We can do it here.
Let me go over you points first: (Sorry for the missing markup...)
1. After some experimenting a while back, I noticed that there seems to be character limit, with respect to search options. You're limited to about 75 characters. I think that limit is not set for "normal" queries. If you exceed it, Google rudely trims them to the maximum length allowed. But hey, at least it'll tell you it did!
Google this and you'll see what I mean:
an awesome movie with an incredibly long title (avi|mpg|wmv|mpeg|divx|mp4|mkv|m4v|mov|flv|rmvb|ogv|wmv|3gp) "Parent Directory" -"Trailer" -cdkey -asp -torrent -html -web-shelf -zoozle -jsp -htm -listen77 -idmovies -shexy -eucontest -0x7'
We have to keep our part of the query as short as possible to prevent that.
2. Adding 'cgi' is actually a great idea.
3. Adding '7z|rar|zip' not so much. Various reasons:
- would increase query length (see no 1)
- it would confuse Google
- finding uncompressed videos/music/apps is always better because you can steam them right away (before downloading), and because there's always a chance that a archive is password protected.
Although software is often compressed when you get them (e. g. via torrent). So this may be a good idea with them...
4. I have to thank you. I'm just realizing that I've used the wrong piece for Archive searches.
+(.rar|.tar|.zip|.sit) <--- this on was just a test an destined to be removed. Not sure what gotten into me.
+(rar|zip|tar|tgz|7zip|iso|cso|gz|7z|bz2|gzip) <----- this is the real deal. I'll update once we cover all the other points.
5. Better Google's highlighting feature and 'Google site: Tool's exclude's are amazing and work very well with the script. I may add some of them to the script...
6. What do mean with 'P...zilla'? Tell me! I'm curious.
I just thought of something:
The pattern you suggested earlier +(.rar|.tar|.zip|.sit) maybe also useful for the experimental Google drive Search:
The malicious links inside some Google drive shares are problematic. They are mostly saved in pretty useful file formats (PDF or png), which when excluded in the query, will also exclude the "good ones".
The way to counter them is to check as many as possible of them and look for some kind of pattern. Words or phrases that are repeatedly used by them ("Direct Download" or "free"), even inside of their malicious URL. If we find something, we can start creating queries that explicitly exclude them. Researching this is not a big deal by itself if Google wasn't such a paranoid asshole. You have to make a lot of queries, which Google doesn't like you do. Which means that you have to make involuntary breaks or reboot your Modem every once in a while.
Speaking of exclude: You were absolutely right. The Google exclude user script is der hammer! I don't want to spend another second without it!
btw, pressing Enter in the google search box, on a results page, does not work when your script is active. And I have your script at the very top of my scripts run-list.
What possibly is in the code to do that, and why?
Then again, it might not be your code: I have alot of scripts active. But please take a look and see if anything is in there that might be causing that. If not, I'll do more troubleshooting.
1. After some experimenting a while back, I noticed that there seems to be character limit, with respect to search options. You're limited to about 75 characters. I think that limit is not set for "normal" queries. If you exceed it, Google rudely trims them to the maximum length allowed. But hey, at least it'll tell you it did!
yeah, I wish Google would provide a way to extend queries, even if it's a paid service. Then I would be smashing their servers! (and so would everybody else. :open_mouth: )
The silver lining is, tail-end terms can be manually removed, and the revised query run.
It also means terms should be ordered in terms of precedence: most-relevant terms closer to the left/beginning of the strings. I see that you've structured the queries with that in-mind (I do that on my own queries) - Bravo.
6. What do mean with 'P...zilla'? Tell me! I'm curious.
4. I have to thank you. I'm just realizing that I've used the wrong piece for Archive searches.
Glad to know I've made a contribution. :blush:
5. Better Google's highlighting feature and 'Google site: Tool's exclude's are amazing and work very well with the script. I may add some of them to the script...
Please don't! I like having scripts compartmentalized - it's easier to filter specific sites, and it aids troubleshooting a lot.
You were absolutely right. The Google exclude user script is der hammer! I don't want to spend another second without it!
I made a big mistake, told you about the wrong script! :relieved: The other one is good, but wait til you try this one! Here's the king: 'Google Hit Hider by Domain (Search Filter / Block Sites)'
That has to be the best script I use for G-Search. (No offense, lol)
Please go to the script's page and 'Favorite' it. And leave Scher some praise - I did!
A couple of comments about G-search queries...
I wish Google syntax allowed for
-(a|b|c)
but I'm somewhat sure it does not work.
FYI, just in cast you didn't know, it does work if using an operator, e.g.
-inurl:cdkey|asp|torrent|html
But, supposedly, using parentheses does not work - though I might be wrong!:
-inurl:(cdkey|asp|torrent|html)
Here's a quirk to keep in-mind: if any term has to be in quotes, then ALL of the terms have to be separated by spaces -- and presumably parentheses are mandatory to enclose the relevant terms; e.g.
intitle:(trailer | preview | "double feature" | torrent)
I'm sure you know this, but the plus-sign isn't needed. Still, I like it there, just cause it makes the string easier to read.
I'm no expert on Google. I learned these techniques from reading some Google Groups threads, after Google killed Blog and Discussions searching; so people were trying to find replacement queries for the services Google had killed. It was in those discussions that some true experts revealed G's mysteries -- for example this weird thing:
-intitle:search (inurl:"index.php?topic" | intext:"reading this topic"|"next thread"|"next topic"|"send private message")
I'll try to find the original links about that, will share them here.
oh, I forgot to thank you for this:
(avi|mpg|wmv|mpeg|divx|mp4|mkv|m4v|mov|flv|rmvb|ogv|wmv|3gp)
I'm gonna use that instead of adding in 7z|rar|zip
To be honest, I don't know which formats are used the most, but I'm re-ordering the terms to be this:
(avi|mkv|mp4|mpeg|mpg|wmv|flv|mov|m4v|divx|rmvb|ogv|3gp|webm|asf)
(in case the queries gets truncated by Google, then I can started backspacing the least-used formats)
.
Hey. Sorry for these long delays between replies. I'm caught up with work.
Let me start with the script and the error you mentioned:
The script is set up to always run at end (when EVERYTHING else has finished loading). You can't influence that by changing the script order in your script manager. You can only tell him which scripts (which are set to run first) to run firster ;-)
Thus is determined by the @run-at property in each script.
Running my script by itself doesn't give me the error you mentioned. Try to disable all other script that run on Google and then enable them one after another. This way you'll find the culprit. If you're brave, find the @run-at property in either script (they are at the top) and change them to document-start for my script (although I think that may break betty altogether)or document-end for the other script.
If that doesn't work for you, send me the name of the interfering script and I'll make mine behave!
"That has to be the best script I use for G-Search. (No offense, lol)"
"Here's a quirk to keep in-mind: if any term has to be in quotes, then ALL of the terms have to be separated by spaces -- and presumably parentheses are mandatory to enclose the relevant terms; e.g. intitle:(trailer | preview | "double feature" | torrent)"
That's very interesting. Can you make two queries, one with this and one with mine and see which one give more/better results? Sounds like something important to keep in mind...
I completely left the 3gp format out cus it's awful. The only reason to have it in the query is if you're looking for very rare stuff. The same is probably true for flv, webm, wmv, rmvb and dixv. Put them at the end with 3gp being last.
Hi. thanks for the replies.
I have waaay too many scripts in-play so I can't even begin to do testing to figure out which is the culprit.
I'll have to do some testing with 'Betty' on a fresh profile: I plan to update my browser version "soon", so I'll install Betty first, then add other scripts one-by-one and narrow down the conflict.
For now, I'll just manually turn it on when I want to use it.
That's very interesting. Can you make two queries, one with this and one with mine and see which one give more/better results?
I'm not sure exactly what kind of test you want, so I'll hold off until more details.
btw, I merged the two -inurl and put the whole thing at the end of the strings:
-inurl:(cgi|jsp|pl|php|html|aspx|htm|cf|shtml|listen77|mp3raid|mp3toss|mp3drug|index_of|wallywashis)
I'm sure it doesn't matter that they are separate. I merged so that it would be simpler for me to backspace terms when my string is too big.
I'm experimenting with another button, Videoland:
+(".avi" | ".mkv" | "fanedit" | "BDrip" | "BRrip" | "DVDrip" | ".divx" | "hdtv" | 480p | ".asf")
Reason: In a few of my results, Google is expanding some of the terms, e.g. 'avi' -- if it wasn't in quotes, it would sometimes show up as part of some other word,e.g "avi*xyz*" or whatever.
I know these quirks are rare, but I want cleaner results. So I added quotes.
Adding quotes and spaces should not count against Google's search limit. Need some more time to test, to see if this is true.
Although the periods (".xyz") I think are useless, I'm gonna test & see what happens.
'480p' and 'asf' are throwaway terms, I know; but I'll keep them in for testing purposes.
'fanedit' is a tricky one. First, fanedit.org no longer links to the finished products, so ideally I should add -site:fanedit.org to the string.
But fanedits could potentially expand the results, so for now, the term will stay in.
A few thoughts - Part II
Hi and thanks for the port / revision.
What do you think about the following:
Would adding 'cgi' to the
-inurl:(jsp|...)reduce some of the nonsense sites?Would adding '7z|rar|zip' to all/most
+(...)make much of a difference?I created a button called 'P...zilla' :ahem-cough-cough: and I'm using
+(avi|mkv|mp4|mpeg|mpg|wmv|mov|flv|m4v|rar|zip|7z|webm|asf|gif)which just expands the 'Movie/TV' string. Do you think some of these extra filetypes would be useful in 'Movie/TV'?Does adding a period actually do anything?
+(.rar|.tar|.zip|.sit)I thought Google just threw it away during searching.Check out my script-set 'Google Search' which lists some great scripts focused on G-Search.
I highly recommend:
'Better Google' which highlights the search terms in the search results -- very useful to see if the results actually match what's being searched for.
'Google Hit Hider by Domain (Search Filter / Block Sites)' by Jefferson Scher -- it allows users to blacklist sites and hide them from search results. I can't live without this script.
Also useful is 'Google site: Tool (Site results / Exclude sites)', which can exclude sites from search results. It's best to use when not using Betty script!