A simple Google search and you’ll find dozens of really good PHP scripts on the Internet to help you create proxy servers in minutes for free. The only limitation with PHP based proxies is that you require a web server to host the proxy scripts and second, you also need a domain name to act as an address for your proxy site.
If you don’t own a domain or server space, you can still create a personal proxy server for free and that too without requiring any technical knowledge.
Create a Free Proxy Server with Google App Engine
Here’s one such proxy site that you can build for your friends in China or even for your personal use (say for accessing blocked sites from office). This is created using Google App Engine and, contrary to what you assume, the process is quite simple.
Create a Free Proxy Server with Google App Engine
Step 1: Go to appengine.google.com and sign-in using your Google Account.
Step 2: Click the “Create an Application” button. Since this is your first time, Google will send a verification code via SMS to your mobile phone number. Type the code and you’re all set to create apps with Google App Engine.
Step 3: Choose a sub-domain* that will host your proxy server. Make sure the domain is available, agree to the Google Terms and click save. The sub-domain is also your App ID that will uniquely identify your proxy application.
For this example, we’ll use blog4info-server as the App ID though you are free to choose any other unique name.
Step 4: OK, now that we have reserved the ID, it’s time to create and upload the proxy server application to Google App Engine. Go to python.org, download the 2.6.4 MSI Installer and install Python.
Step 5: Once Python is installed, go to code.google.com, download the Google App Engine SDK for Python and install it.
Step 6: Download this zip file and extract it to some folder on your desktop. The zip file, for the curious, contains a couple of text files (written in HTML and Python) that you can read with notepad.
Step 7: Start the Google App Engine Launcher program from the desktop and set the right values under Edit –> Preferences (see screenshot above).
Step 8. Click File –> Add Existing Application under the Google App Launcher program and browse to the directory that you created in Step 6. Click the Edit button and replace “YOUR_APP_ID” with the ID (sub-domain) that you reserved in Step 3.
Step 9: Click Deploy and your online proxy server is now ready for use. You can experience it live and if any of the steps don’t make sense, please refer to the following video screencast (available in 720p HD).
You can edit the main.html file to change the appearance of your proxy server and you can even add Analytics and AdSense code to your proxy server in case it gets popular on the web. The application is currently open to all users but you can add a layer of authentication so that only users who are logged-in into their Google Accounts can use your web proxy server.
If you have made any changes to your HTML files, you can upload the latest version to Google App Engine either by clicking the “Deploy” button again or use the following command -- appcfg.py update
Credits: The proxy server uses code from Mirrorr, an open-source web caching project by Brett Slatkin. Thanks Pratham for your help! & Labnol.org
Posted by
123
on
Friday, March 05, 2010
Hi friends,
As you all know there's a new in front of us... It is gonna be 10 years after the millennium threat (the Y2K threat)...the great milestone in computer's history! Let us recall it.
The Year 2000 problem (also known as the Y2K problem, the millennium bug, the Y2K bug, or simply Y2K) was a notable problem for both digital (computer-related) and non-digital documentation and data storage situations which resulted from the practice of abbreviating a four-digit year to two digits.
In computer program design, the practice of representing the year with two digits becomes problematic with logical error(s) arising upon "rollover" from x99 to x00. This has caused some date-related processing to operate incorrectly for dates and times on and after January 1, 2000 and on other critical dates which were billed "event horizons". Without corrective action, it was suggested that long-working systems would break down when the "...97, 98, 99, 00..." ascending numbering assumption suddenly became invalid. Companies and organizations worldwide checked, fixed, and upgraded their computer systems.
While no globally significant computer failures occurred when the clocks rolled over into 2000, preparation for the Y2K bug had a significant effect on the computer industry. Countries that spent very little on tackling the Y2K bug (including Italy and South Korea) experienced as few problems as those that spent much more (such as the United Kingdom and the United States), causing some to question whether the absence of computer failures was the result of the preparation undertaken or whether the significance of the problem had been overstated.
Many banks have responded to the Y2K problem by forcing full 4-digit year entries on cheque forms, which helps to prevent the error from occurring in accounting environments.
Background
Y2K was the common abbreviation for the year 2000 software problem. The abbreviation combines the letter Y for "year", and k for the Greek prefix kilo meaning 1000; hence, 2K signifies 2000. It was also named the Millennium Bug because it was associated with the popular, rather than literal, roll-over of the millennium, despite the fact that the bug could have occurred at the end of any ordinary century.
The Year 2000 problem was the subject of the early book, "Computers in Crisis" by Jerome and Marilyn Murray (Petrocelli, 1984; reissued by McGraw-Hill under the title "The Year 2000 Computing Crisis" in 1996). The first recorded mention of the Year 2000 Problem on a Usenetnewsgroup occurred Saturday, January 19, 1985 by Usenet poster Spencer Bolles.
The acronym Y2K has been attributed to David Eddy, a Massachusetts programmer, in an e-mail sent on June 12, 1995. He later said, "People were calling it CDC (Century Date Change), FADL (Faulty Date Logic) and other names."
Many computer programs stored years with only two digits, for example, 1980 would be stored as 80. Some such programs could not distinguish between the year 2000 and the year 1900. Other programs would try to represent the year 2000 as 19100. This could cause a complete failure and cause date comparisons to produce incorrect results. Some embedded systems, making use of similar date logic, were expected to fail and cause utilities and other crucial infrastructure to fail.
Some warnings of what would happen if nothing were done were particularly dire:
The Y2K problem is the electronic equivalent of the El Niño and there will be nasty surprises around the globe. — John Hamre, Deputy Secretary of Defense
Special committees were set up by governments to monitor remedial work and contingency planning, particularly by crucial infrastructures such as telecommunications, utilities and the like, to ensure that the most critical services had fixed their own problems and were prepared for problems with others. While some commentators and experts argued that the coverage of the bug largely amounted to scaremongering, it was only the safe passing of the main "event horizon" itself, January 1, 2000, that fully quelled public fears. Some experts who argued that scaremongering was occurring, such as Ross Anderson, Professor of Security Engineering at the University of Cambridge Computer Laboratory, have since claimed that despite sending out hundreds of press releases about research results suggesting that the bug was not likely to be as big a problem as some had suggested, they were largely ignored by the media.
Programming problem
The practice of using two-digit dates for convenience predates computers.
However there were no major problems reported due to this bug....... tribute to brilliant programmers who saved us!
To know more : http://en.wikipedia.org/wiki/Year_2000_problem
Posted by
123
on
Tuesday, December 22, 2009
If you were wondering how long will global reserves of some important metals that are used in electronic devices last, here’s a clue.
Tantalum is a rare metal that is used in the manufacture of cell phones and camera lenses but you’ll be surprised to know that if every human on the planet were to consume this metal at the same rate an average US resident today, the metal supplies won’t last for more than 20 years.
Similarly, we won’t be left with any stock of Indium, another rare metal used in LCDs and touch-screen displays, after 4 years if the world consumes this metal at the same rate as US today.
This report, which roughly demonstrates how quickly time is running out for some rare and important metals, was original published in New Scientist in 2007.
Armin Reller, a materials chemist, estimates that we have, at best, 10 years before we run out of Indium. Its impending scarcity could already be reflected in its price: in January 2003 the metal sold for around $60 per kilogram; by August 2006 the price had shot up to over $1000 per kilogram.
Posted by
123
on
Wednesday, October 21, 2009
President Barack Obama warned American teenagers on Tuesday of the dangers of putting too much personal information on internet social networking sites, saying it could come back to haunt them in later life.
The presidential words of advice follow recent studies that suggest US employers are increasingly turning to sites such as Facebook and News Corp's MySpace to conduct background checks on job applicants.
Taking part in a question-and-answer session with a group of 14- and 15-year-old school students, Obama was asked by one pupil for some advice on becoming US president.
"Well, let me give you some very practical tips. First of all, I want everybody here to be careful about what you post on Facebook, because in the YouTube age, whatever you do, it will be pulled up again later somewhere in your life," Obama said.
"And when you're young, you make mistakes and you do some stupid stuff. And I've been hearing a lot about young people who - you know, they're posting stuff on Facebook, and then suddenly they go apply for a job and somebody has done a search."
Obama referred several times to "mistakes" he had made when he was at school but offered no specifics. He has previously admitted to drug use when he was younger.
A survey in June by careerbuilder.com found that 45 per cent of employers used social network sites to research job candidates and that Facebook, which says it has 250 million users worldwide, was their site of choice.
Some 35 per cent of the employers surveyed said they had found content on the sites that had influenced them to reject a candidate. Examples included inappropriate photographs, information about the applicants' drinking or drug use, or bad mouthing of previous employers, co-workers or clients.
Posted by
123
on
Thursday, September 10, 2009
Important warning: VOIP users
Hi Readers,
Posted by
123
on
Monday, April 13, 2009
Hi Step: 1. Click on “Run” and type the following address: C:\heap41a and hit Enter key. You cannot find the “heap41a” file by navigating thru files and folders using mouse in C drive. Inference: You will find the following files in the above path Step: 2. Delete the “svchost.exe” file with the big “H” icon. Step: 3. Then press start button, click run and type regedit and click ok. Your registry will be opened. Then press F3 and find comes. There type heap and search. Wherever it stops and gives any values, corresponding to “Heap”, just press delete button on key board and delete it. Then Press F3 once again and so … on, till you delete all heap folders and values.
The "MUHAHAHA" virus is a highly contagious virus. If this virus is infected in your computer, you must immediately remove it. MUHAHAHA.!!!!!!!!! virus migrates through pen drives or even through CD’s. In CD’s or USBs if you find a file named Microsoftpowerpoint.exe kindly delete it. The virus gets installed to the computer by this executable file.
Symptoms:
When you open some sites (for eg: youtube), a dialog box appears that "this site is blocked for you fool, The admin did not add this dialog and who did? Muhahaha" and a laughing sound.
This virus has already infected millions of computers. This virus cannot be removed with the help of an antivirus.
To remove this virus follow these steps:
a) Offspring (folder), b) 2.mp3 (Muhaha laughing sound that is played while virus closes the window),
c) drivelist (notepad file), d) reproduce (notepad file), e) script1 (notepad file), f) std (notepad file), g) Icon (Icon file)
h) svchost.exe (executable file)
Then restart the computer. Your MUHAHAHA virus is gone for ever !!!!
Note: Some times the access in denied to this file and thus cannot be deleted, in such situations download GIPO FILE UTILITIES to delete it.
Posted by
123
on
Friday, April 03, 2009