Like many other Web sites, wartrip.blogspot.com makes use of log files. The information inside the log files includes internet protocol ( IP ) addresses, type of browser, Internet Service Provider ( ISP ), date/time stamp, referring/exit pages, and number of clicks to analyze trends, administer the site, track user’s movement around the site, and gather demographic information. IP addresses, and other such information are not linked to any information that is personally identifiable.
Links to other websites
Our website may contain links to other websites of interest. However, once you have used these links to leave our site, you should note that we do not have any control over that other website. Therefore, we cannot be responsible for the protection and privacy of any information which you provide whilst visiting such sites and such sites are not governed by this privacy statement. You should exercise caution and look at the privacy statement applicable to the website in question.
Cookies and Web Beacons
wartrip.blogspot.com has no access to or control over these cookies that are used by third-party advertisers.
If you wish to disable cookies, you may do so through your individual browser options. More detailed information about cookie management with specific web browsers can be found at the browsers' respective websites.
Specifics on Google's DoubleClick DART Cookie:
* Google's use of the DART cookie enables it to serve ads to your users based on their visit to your sites and other sites on the Internet.
Saturday, August 30, 2008
Friday, August 29, 2008
Stealing information - or just reading it without permission - is a lot easier than it used to be. All you have to do is stick a USB thumb drive into a port, copy some files, and put the drive back into your pocket.
You're very careful about encrypting your backup files, and the information that you send over the Internet. But you're probably not protecting your USB ports, which means someone could copy important PC files to a thumb drive. These thumb drives fit easily into pocket or purse. Bad guys can use them to steal your files, your financial information, and your identity.
Without MyUSBOnly, your data can be easily stolen by any of the people who come in and out of your home or office every day. With MyUSBOnly, your information is protected.
Thursday, August 28, 2008
E-mail alerts outlining the dangers of dihydrogen monoxide swept the Internet in the late 1990s and still pop up today. Many ask that you sign and forward a petition to ban the chemical, which contributes to global warming, is a major ingredient in acid rain, causes metals to rust more quickly, and has been found in cancerous tumors. The chemical also contributes to the greenhouse effect and to erosion of our natural landscapes. It's even in food. Sounds pretty dangerous. You're ready to sign right now, aren't you?
Well, let us tell you one more thing about dihydrogen monoxide: It's more commonly known as water. You know, the substance that every single living being relies on to survive? The origins of this item are multifold, from flyers circulated at the University of California at Santa Cruz in 1989 (so 20th century!) to a junior high school student who surveyed 50 classmates in 1997 and got 43 of them to sign his petition to ban the chemical. He then won a prize at his science fair for his project, called "How Gullible Are We?" Several Web pages touting the chemical's dangers are still live. Don't feel too bad if you've ever fallen victim to this hoax; even a government official in New Zealand took the bait last year.
For spams update, visit...OnGuard Online
Sunday, August 3, 2008
10 Worst Web glitches of 2008 (so far)
By Rafe Needleman – August 15, 2008 6:00 AM PDT
We have been reminded several times lately that Web 2.0 is in no way a synonym for "reliable." Major services have crashed. Big product launches have fizzled. Users have raised their collective fists in the air. What's going on? Is the Web crumbling? Well, no, it's not. But users' expectations are rising, and Web companies often get themselves into trouble by promising far more than they can deliver.
Here's the timeline of offline:
Amazon S3 (Also: Google App Engine)
When: February 15 (Amazon); June 17 (Google)
What happened: These massive infrastructure services, Amazon's S3 especially, underpin many Web 2.0 companies. When they go down, big sites go down. When the sites go down, they lose money.
Corporate coping behavior: Amazon CTO Werner Vogels banished to the lecture circuit to explain why S3 is still more reliable than any servers you could run yourself.
The damage: Companies forced to re-consider their reliance on "cloud computing."
When: April, May, June. July too? Who cares?
What happened: Twitter began to get unreliable. It's up, then it's down. Repeat.
Corporate coping behavior: During the bad spells, Twitter turns off key features of the service -- like access from Twitter helper apps, or the "replies" tab on the site -- to decrease the load. Twitter also buys the search engine Summize, which adds a new level of utility to the service.
The damage: Twitter was becoming part of the social fabric of the technology community. When it began to get flakey, marquee users abandoned the service and fled to rivals like Friendfeed. The problems appear to have been resolved, but the damage may never be repaired.
When: June 17
What happened: Mozilla announced the release data of the Firefox 3.0 and its goal to get a million downloads on that day. When the day comes, the download doesn't work. The downloads start up later, and Mozilla goes on not just to meet its download goal but utterly crush it.
Corporate coping behavior: Mozilla changes "Download Day" to "The 24-hour Period that Starts When We Say it Does."
The damage: Temporary embarrassment, which is overshadowed by insane success.
When: June 17
What happened: Amazon went offline for a big part of the U.S. workday. Millions of users had to go back to work.
Corporate coping behavior: Mad scramble to fix. What did you expect?
The damage: Estimated at $16,000 a minute. But long-term damage to the company is negligible (unlike the S3 outage).
When: July 8
What happened: Online productivity apps went offline, stranding users' files in the cloud.
Corporate coping behavior: Apology. Google has offline support (Google Gears) for an increasing number of its online apps. Which is fine, if you remember to set it up before the next outage.
The damage: Credibility. Online apps are being pitched by companies like Google as credible replacements to traditional apps like Microsoft Office. Outages like this shake users' already tenuous faith in the reliability of services that hold their most important data files.
When: July 10
What happened: Apple launched its 3G iPhone with a new data sync service to replace .Mac. Sadly, it didn't work. For many users, key services like e-mail wouldn't update.
Corporate coping behavior: Jobs berates his staff in public; Apple gives subscribers 30 days of free service.
The damage: Poor uptake of the service, many disgruntled users, negative halo effect on the iPhone.
What happened: Google scientist leaves Google, builds competitive search engine. At launch, it sucks. By the time it's working as advertised, nobody's paying attention anymore.
Corporate coping behavior: Company claims millions of users are so anxious to dump Google that they overload the new engine. Begs for time.
The damage: You only get one chance to make a first impression. Cuil's growth will be seriously clipped by its botched launch.
What happened: After finally getting off the stick and suing the much-loved Scrabulous off of Facebook, Hasbro releases its own online Scrabble app on the social platform. It crashes.
Corporate coping behavior: Scrabble owner Hasbro claims that hackers killed the service. No surprise: As Caroline McCarthy reported, "if you just look at the Scrabble application wall, it's pretty clear that there are a few people who are angry enough at Hasbro and EA to want to sabotage the game."
The damage: What's a seven-letter word for "global acrostic withdrawl?"
Gmail (Also: Hotmail)
When: August 12 (Gmail); February 26 (Hotmail)
What happened: OMG, Gmail is down. And unlike with client-based e-mail (Outlook), when your Web mail is offline, you can't even read the old stuff sitting in your inbox.
Corporate coping behavior: Google apologies, knows users will be back.
The damage: In the recent Gmail outage, upset users flocked to Twitter to complain. Miraculously, Twitter stayed up, despite a crushing load of hundreds of tweets a second from disgruntled Gmail users.
When: August 14 and March 24.
What happened: Undisclosed troubles fell all 55 Netflix shipping centers. Twice. Users don't get their discs.
Corporate coping behavior: Netflix plans to refund fees to affected users, and reminds them they can watch streaming Netflix on their PC or Roku box. Although the company refuses to use the word "fallback" to describe this benefit.
The damage: Netflix customers have to watch old DVDs, live TV, Tivo, Unbox, Hulu... Wait a minute, do we really need Netflix?
And don't forget...
It's just August. There's plenty of time left in the year for more Web 2.0 disaster.