Step 2: What Have We Accomplished?

Of course we didn't really seem to accomplish anything  by asking a translation service to not translate a webpage.  But in truth, some of the content was proxied through Google's Translate service.  Using the Firebug Extension for Firefox, I was able to see that the request to see the front page of Instructables.com through Google Translate resulted in 26 HTTP requests, and only 3 of them were sent directly to instructables.com (2 for JS, 1 for CSS).  So, this isn't a bulletproof method of avoiding ALL requests to the "translated" domain, but most of the content did indeed go through Google's translation services.

But can we make it a bit easier to automate the usage of this tool?  Maybe a little bookmarklet?
<p>Nice That was working If You Have Any Problem So <a href="http://hidemeproxy.xyz" rel="nofollow">Visit Here</a> To get understand easily</p>
My workplace must have it blacklisted as well. Didn't work for me.
Thanks for the tip!
Interesting instructable here.<br>Unfortunately my workplace's filter already includes Google Translate into it's blacklist. It even clearly states its use as a proxy as a reason for avoidance.<br><br>Now, I don't know if this is a tailored list for my employer, or if they get their list from their filter client.<br>But your mileage may vary depending on which software they use.

About This Instructable




Bio: A programmer ever since I laid my hands on a TRS-80 writing BASIC programs like mad-libs in 1990. Goes back to 1984 if you count ... More »
More by Kozz:Use Google as a Proxy Repair a Window Screen on the cheap Improve your DishDVR UHF Remote Control Reception 
Add instructable to: