This week in Tweets
- is not in a good mood this morning. #
- Only a few hours left for @mommasreviews cupcake giveaway: http://tinyurl.com/bydj97 #
- Verizon Wireless wants to sell your technical, billing & location info to 3rd parties. Call 800โ333โ9956 to opt out. http://is.gd/mwsT #
- Interesting. Reading something that states that incandescent bulbs are prohibited on Shabbat due to heating the filament until it gloes. #
- Non-incandescent bulbs (e.g. florescent) aren’t prohibited because you aren’t heating a strip of metal. It’s not considered “creating fire.” #
- RT @PopJudaica: I know it’s Purim, but the moment you’ve all been waiting for is here. The Passover products are in! http://twurl.nl/btd5be #
- Got one section of my Twitter App to run in under 80 seconds. Down from 4 minutes or more. #
- Second part of my app takes about 3 seconds. If I can tie these parts together, I might be able to launch a beta tonight! ๐ #
- Apparently, ASP has a length limit on strings. So a string of more than 65,535 characters is chopped. Need to find a workaround. #
- Not ASP string length limit, but a database problem. DB is returning truncated string instead of full string. This should be easier to fix. #
- Got it fixed. mySQL’s Text field was too limited. Changed to LongText and it can now accommodate strings of up to 4 billion characters. #
- DVRing Heroes. I usually do it anyway, but this time I’m DVRing it so I can watch Wozniak on #DancingWithTheStars. #
- WOZNIAK! #
- RT @wiifitgirl: British ban kissing at train station http://tinyurl.com/cf9rmt #
- RT @HisBoysCanSwim: We did it! Weโre able to pay all pregnancy and baby doctor billsโฆ and we saved our house! http://tinyurl.com/b343sy #
- I squished the last bug in my Twitter App last night & added a “save your report” feature. #
- Going to type up a blog post about it later then will post the link to my new Twitter App (in beta.) #
- Asked why it went down, got “my shift just started” answer. Uh, maybe you could go *ASK* someone? #
- Bug in my Twitter App means I’ll need to delay release. I think. Or maybe bug was 1st signs of my site going down. #
- In either case, I need to wait until the server comes back up before I can test it, fix the bug (if it exists), & release the beta. #
- Arvixe can’t give reason why sites are down or an ETA on when they’ll return. Not good, Arvixe. If not back soon, I might move hosts (again) #
- An hour and a half and my sites are still down. *GRRRRR* What’s going on Arvixe??!!! #
- Contacted Arvixe support. They’ve escalated the problem with their data center. Gave me the server admin’s number. #
- Server admin: it’s likely a hardware issue (data’s fine, server can’t connect to internet). He took my # to call me when sites are back up. #
- Wonder why all of my Tweets say “via Tweet Search” instead of “via Twhirl” #
- … and of course that tweet has to prove me wrong by saying “via Twhirl”! #
- Sites are still down. Arvixe support admin responded to my post at WebHostingTalk.com giving more info. http://is.gd/mNtf #
- Feeling more generous about the downtime since I’ve learned more. Hardware issues happen. Their support’s been as good as can be expected. #
- TechyDad.com and TheAngelForever.com are still down. This is going on 9 hours. #
- TechyDad and TheAngelForever sites still down. Going on 20 hours now. Windows 2003 HD corruption to blame. Arvixe says data is safe. #
- Arvixe said they hoped to get everything back “before the morning light.” They’re in CA, so this is in about 1hr. #
- If sites aren’t back in 2 hours, I’ll ask for another status update. #
- Yay! Sites are back up! Total downtime: 20 hours. #
- RT @LanceUlanoff: Why Girl Scouts Can’t Sell Cookies Online http://bit.ly/lKCvd <= A web site is less safe than knocking on strangers doors? #
- Websites are back up, but my admin panel and FTP don’t seem to work. Time for another Arvixe support contact. #
- Admin control panel is back up (came back as I was on with support rep of course). FTP is still down. #
- Knitted Mythbusters dolls! http://www.paperheroes.net/?p=92 #
- Worked on my Twitter App last night. Got it working, but there’s one “minor” flaw. #
- When dealing w/ a user following 1,000+ people, Windows goes low on Virtual Memory. Going to need to fix that. #
- So much work… so little motivation. #
- RT @BrettTrout: What chu talkin’ ’bout – Sears Tower to be renamed Willis Tower http://tinyurl.com/bafub5 #
- RT @LanceUlanoff: RT @nizzer: The World Wide Web Is 20 Years Old Today http://ow.ly/T0i <= 1 more year & the World Wide Web can buy a drink. #
- First day of spring is next week. This would be a fun way to celebrate: http://is.gd/ndkk (Diet Coke &Mentos Geyser Tube) #
- RT @mike_elgan: Will Twitter replace Monster.com as the best place to find a job? http://bit.ly/C5go0 <= 140 char resumes seems pretty short #
Powered by Twitter Tools.

Security is important in today’s online world. A big part of that security is what password you use for the various websites you frequent. It is not uncommon for a person to have dozens of different sites, each with their own username and password. But how to you manage them all? Setting all of your passwords to be the same (e.g. "12345") isn’t safe. (I have the same combination on my luggage!) After all, if someone guesses *one* of your passwords, *all* of your accounts will be compromised. Writing them on paper and sticking it to your monitor isn’t very safe either. Anyone passing by your office/cubicle could see the list and gain access to your accounts. So what should the security conscious web surfer do? Why, put them in a safe of course! No, not a fire-proof safe (though that might be a good hard-copy backup method), but inside an application called (appropriately enough)