21–30 of 77 posts
In chrome I set my default search engine to "Googol" with the search query: http://google.com/search?q=%s . Seemed to fix it for me
[deleted]
But I really want it to stop. I hate not being able to just "copy link address" off of the results page
[1] https://addons.mozilla.org/en-US/firefox/addon/google-search...
CoralCDN link: http://mergy.org.nyud.net/2013/01/what-is-up-with-the-insane... I couldn't get through to the main site. Fortunately someone had fetched the page over coralcdn at some earlier point. I wonder if someone wrote a proactive coralcdn bot for HN links.
Google's search URLs have slowly been creeping up in length over years. Some of the parameters like hl are for user interface control (in this case, langauge). Others like sourceid are for broad tracking of who's using Google how. And lately there are many more nonces mostly related to tracking individual users, Google+, instant search, etc. Many of those change based on who you are logged in as. Google is also respo…
Firefox addon (useful many places):
https://addons.mozilla.org/en-us/firefox/addon/redirect-remo...
Chrome:
https://chrome.google.com/webstore/detail/undirect/dohbiijnj...
Edit: This comment is relevant to search results, not the address bar, my bad!
But I really want it to stop. I hate not being able to just "copy link address" off of the results page
-The home page, after rendering the search box and all that, asynchronously downloads the css, images and html needed to display the chrome around the results listing.
-That way it is cached on the client, and when they perform a query, less data has to be downloaded from Google's servers (just the actual results & ads), making the result page render faster.
-It knows not to download all the chrome due to the presence of the 'fp' GET parameter, the absence of that parameter will cause the entire results page, including chrome, to be downloaded.
I presume the rest of the parameters are useful for similar reasons.
It should also be noted that for non-HTML5 compatible browsers, modifying the hash fragment with JavaScript is the only way to change the url that gets bookmarked without causing a page reload (which would add latency), so if you want a bookmarkable local results page for images with certain preferences, adding a bunch of crap (latitude, longitude, preference hash, query, search type, etc.) to the fragment is the only way.
Google's search URLs have slowly been creeping up in length over years. Some of the parameters like hl are for user interface control (in this case, langauge). Others like sourceid are for broad tracking of who's using Google how. And lately there are many more nonces mostly related to tracking individual users, Google+, instant search, etc. Many of those change based on who you are logged in as. Google is also respo…
Earlier quoted context omitted.
[deleted]
You can now use HTTPS on the www subdomain. Try https://www.google.com/search?q=%s as the URL to use. I consistently get this turned into https://www.google.com/search?q=foo&qscrl=1 which makes it easy enough to cut out the qscrl parameter for linking purposes.