Google Reader for wider screens

By Assaf 1 Last update Dec 28, 2008 — Installed 32,439 times.

Archived Comments (locked)

in
Subscribe to Archived Comments 23 posts, 13 voices



Jesse Andrews Admin

The following is an archive of comments made before threaded discussions was implemented (November 16th, 2008)

 
Assaf 1 Script's Author

Hi Vaughan,

The long-list approach actually doesn't sound that bad. The list isn't that long anyway (found this: http://www.google.com/supported_domains ).

 
Vaughan Chan... Scriptwright

Hi Assaf,

Yes the regex would allow your code to run on google.bad.com but given that your script only modifies css rules then there doesn't seem to be any real security risk. There is no personal information being handled by the script and it does not result in any additional files accessed. Using the regex should not increase the risk of visiting google.bad.com.

This is the only way I can think of to get your script to run on all Google sites without adding a huge URL list.

By the way, if you decide to use it you should add the reader/view/ part to the regex.

Vaughan

 
Assaf 1 Script's Author

Dapxin, weird, I had no idea Opera supported greasemonkey.

Vaughan Chandler, the regex you supplied - and please correct me if I'm wrong - would still allow malicious sites to match if they look like this: "http://www.google.bad.com". No?

 
Dapxin User

Google seems to have broken this for Opera. Its not been working in Opera 9.62 for few days now.

 
JP Bourgeois User

Works great! Thank you.

 
Vaughan Chan... Scriptwright

Hi Assaf,

If you want the script to work on other TLDs you could change the @include statements as Zezinho suggested and then use the following code:


if (window.location.href.toLowerCase().match(/^https?:\/\/www\.google\.([a-z]{2,3}|com?\.[a-z]{2,3})\//)) {
// Your code here
}

This way your code should run only if "www.google.", "www.google.co." or "www.google.com." is followed by any 2 or 3 letters and then a slash. This limits it to any 2 or 3 letter TLD, which seems reasonable. The only problem you should run into would be if somebody other than Google registers for a particular TLD.

Disclaimer: I haven't tested the code, but it works in my head :)

 
Assaf 1 Script's Author

Sorry, Zezinho, I'm afraid your suggestion might cause my script to run on unintended websites, like:
http://www.google.some_horrible_mal_site.com/re...

:(

Any idea how to regex/wildcard only TLDs?

 
Zezinho User

please change

// @include        http://www.google.com/reader/*
// @include        https://www.google.com/reader/*

for
http://www.google.*/reader/*
https://www.google.*/reader/*

because google change TLD in others countries.

 
wei User

Thanks! Works great.

 
Alysssa User

Works perfectly!

 
Charnita Fance User

Thank you for this!!! Very helpful.

 
Assaf 1 Script's Author

Thanks for your comment, Alvin.
It works now http/https.

 
Alvin User

Ahh, figured it out. Sorry for the too-quick comment previous.

If you use customizegoogle to use the https version of google reader, it won't work.

 
Alvin User

Doesn't appear to make any difference.

 
Assaf 1 Script's Author

TheIrishGuy, I don't know what you mean, it doesn't happen to me. It's a one-liner script, really, so I doubt it messes with the sidebar.

 
TheIrishGuy User

Great script. Absolutely love it. Question though.
For whatever reason, the sidebar seems to appear and disappear depending on whether or not my mouse is hovering over the sidebar. Is that part of this script?
Thanks.

 
madquark User

Thanks again :)

 
Assaf 1 Script's Author

Updated. Works again.

 
madquark User

Thank you for the update :)

 
Assaf 1 Script's Author

Updated to fit new CSS

 
pleasedelete User

Dito to what Assaf said

 
Assaf 1 Script's Author

I recently bought a wider screen and was annoyed by the fact that Google Reader, my favorite RSS reader, limits the item width to 580 pixels, thereby wasting most of my screen size. With this user-script items will take up the entire available width.

Cross
Presentational HTML allowed.
Use <code> for inline code and <pre> for code blocks. Use &lt; and &gt; for literal < and >.
We help break paragraphs and link your links.
or cancel