Tuesday, March 23, 2010

List of Riskiest Cities: Seattle #1, Portland #10

The 50 riskiest cities, according to a Norton from Symantec survey:























































































1. Seattle 18. Oakland, Calif. 35. Chicago
2. Boston 19. Nashville-Davidson, Tenn. 36. Baltimore
3. Washington, D.C. 20. San Jose, Calif. 37. Oklahoma City
4. San Francisco 21. Columbus, Ohio 38. Philadelphia
5. Raleigh, N.C. 22. Dallas 39. Jacksonville, FL\la.
6. Atlanta 23. Kansas City, Mo. 40. Tulsa, Okla.
7. Minneapolis 24. New York 41. San Antonio
8. Denver 25. Indianapolis 42. Milwaukee
9. Austin, Texas 26. Albuquerque, N.M. 43. Cleveland
10. Portland, Ore. 27. Miami 44. Tucson, Ariz.
11. Honolulu 28. Omaha, Neb. 45. Long Beach, Calif.
12. Charlotte, N.C. 29. Virginia Beach, Va. 46. Fort Worth, Texas
13. Las Vegas 30. Los Angeles 47. Fresno, Calif.
14. San Diego 31. Cincinnati, Ohio 48. Memphis, Tenn.
15. Colorado Springs, Colo. 32. Houston 49. El Paso, Texas
16. Sacramento, Calif. 33. St. Louis, Mo. 50. Detroit
17. Pittsburgh 34. Phoenix

Monday, March 1, 2010

Google to buy Seattle's own Picnik

Word today is that Google is buying up Seattle-based Picnik.com.

More on the Picnik blog and the Official Google Blog

You may recall we've talked about Picnik on this blog before, first in Fall 2007 when they had announced Premium features. Since then, I've enjoyed meeting CEO Jonathan Sposato at various events around town and have enjoyed watching Picnik grow.

The team has been nominated for a 2010 WTIA Industry Achievement Award-- the awards are this Thursday. Will Picnik win one last award for their online photo editing software as Bitnik, Inc? Certainly the acquisition will be the talk of the town for a few days.

Congratulations to the entire Picnik gang!

Updated 1:00PM: to include additional information, link to Google blog, and a look back at previous posts.

Disclosure: I have a personal relationship with a Google employee. This person didn't contribute to this -or any- report, nor would this employee probably even read this blog. *sigh*