FTC Do-Not-Track: feasibility is just fine, consumers are smarter than advertisers think, and consumers will win - http://bit.ly/giPfIN
Monday, December 06, 2010
Why Is The WikiLeaks Twitter Account Only Following TweetBackup?
Why Is The WikiLeaks Twitter Account Only Following TweetBackup?
Even though Amazon and Paypal have severed their relationships with the controversial to say the least WikiLeaks, the @WikiLeaks Twitter account is still holding strong. Some are wondering why Twitter has as of yet to cut ties with the service after this week’s leak of 251,287 diplomatic cables, which pissed some high powered people off to put it lightly.
Perhaps WikiLeaks founder Julian Assange is wondering the same thing. Which would explain why only account @WikiLeaks is following at the moment is @TweetBackup, a service that allows you to back up your tweets daily.
Tweetbackup, run by Backupify, requires that you follow it in order to use it, which means that Assange has no other choice but to follow if he wants Tweetbackup to preserve his tweets in case of a takedown.
It’s interesting to note that by some kind of default Assange, who has all eyes on him at the moment, is basically advertising one service and coincidentally one that protects your Twitter data in cases of deletion. I’ve contacted Twitter as to whether they would take down the @WikiLeaks account under any circumstances and have yet to hear back.
In the meantime TweetBackup representative Charlie Ungashick tells TechCrunch that they haven’t tried to DM Assange, despite being the only people in the world who have the power to do so. I’m amazed at their powers of resistance and/or indifference.
Posted by
Augustine
at
8:44 AM
Twitter Goes After Twittersearch.com
Twitter Goes After Twittersearch.com
Twitter late last week filed a UDRP complaint, notably its first ever since the company was founded, in an effort to obtain ownership over the (currently parked) domain name twittersearch.com – as you can see here.
Obviously, Twitter is right to do this, since the domain is likely to cause some confusion, although we should note Twitter hasn’t managed to secure a trademark for the term ‘twitter’ in the United States so far, despite multiple attempts.
Update: my bad, they haven’t had any success in getting a trademark on the word ‘tweet’, but they do own the ‘twitter’ trademark.
Twitter of course has a popular search product that bears the obvious name Twitter Search, so I’d do the exact same thing if I were them.
That said, they took their sweet time to make the move – twittersearch.com was first registered back in March 2007.
A quick WHOIS search reveals that the owner of the contested domain name has opted to hide his or her identity, and the domain name is currently inactive, leading to a placeholder page riddled with ads.
Next up, twitter-search.com?
Update 2: DomainNameWire on ‘Why Twitter Singled Out TwitterSearch.com’. Also, the owner is apparently Popvox, the same company that’s behind TwitterVision.com.
Posted by
Augustine
at
8:43 AM
AVG 2011 Update Crashes 64-bit Windows 7 PCs; Here's a Quick Fix [Fixes]
AVG 2011 Update Crashes 64-bit Windows 7 PCs; Here's a Quick Fix [Fixes]
If you use the popular AVG Free as your anti-malware app of choice, an update to the 2011 version of the application has bricked 64-bit Windows 7 machines. If you're running Windows 7 64-bit and use AVG, you might want to hold off on the update; if you've already updated and are experiencing this problem, AVG offers this quick fix. [Slashdot]
Posted by
Augustine
at
8:31 AM
How to Get the Flash 10.2 Beta Working in Google Chrome [Flash]
How to Get the Flash 10.2 Beta Working in Google Chrome [Flash]
Adobe just released a beta of the newest Flash player, complete with lower CPU usage and full screen dual-monitor playback. Chrome, though still uses its built-in, stable version of Flash. Here's how to get the beta goodies in Chrome.
Even after installing the 10.2 beta, Chrome will default to its built-in version of Flash, even though it detects the 10.2 beta just fine. To use the beta instead of the stable version, open up Chrome and type about:plugins
in the address bar. Hit the "Details" button in the upper-right hand corner, and under "Flash" you should see two different plugins—one in Chrome's folder, and one elsewhere (see above). Hit Disable under the one located in Chrome's folder, and close out of the plugins window. To see if it worked, you can try watching Adobe's Stage Video demo.
If it works, you're using the beta. If it tells you to install the beta, go back to about:plugins
and make sure you've disabled the correct plugin. Once you get the beta working, you should notice Flash hogs less of your CPU, and can play videos in full screen on one monitor while you work on the other!
Note that using the Flash beta likely disables Chrome's new sandboxing abilities in the Dev channel, so you have to choose which is more important to you.
Posted by
Augustine
at
8:31 AM