This post is kind of a stub, I’m sitting in the Fox Theatre ready to live-blog.
The event started awhile ago, and I’ve been blogging it as it happens. As always, you can always hit the live video feed instead of reading my transcripts & witty commentary as well.
A special thanks to WeatherFlow Inc. for flying me out to the tour.
Well, it’s been over a year since I released my Wordpress MyBlogLog plugin, and I’m still getting emails about it. Honestly, I’m very surprised that this thing still works. If you’re using the plugin now, or want to, let me know! I think it is time for a big code overhaul, and perhaps some new features but there is no sense in developing this plugin if there’s no demand. If you’ve got an idea, post it up and I’ll do my best to get it out there in the wild with the next release. I did notice the guys over at MyBlogLog have been hard at work improving the JavaScript and their own feature set as well which means I should probably update the plugin pretty soon. Also, I am aware of the missing readme file! Please, I know about it, and I’ve posted about it. I promise, next release, you all will get an extensive readme!
Anyways, it amazes me how far MyBlogLog has come since the day I registered and alpha tested it. Really, you have no idea how simple the idea was at the time. Todd, Eric, Steve, John and the rest of the crew over there at Cloudspace and Yahoo, my hats off to you guys.
The chumby is a compact device that displays useful and entertaining information from the web: news, photos, music, celebrity gossip, weather, box scores, blogs — using your wireless internet connection. Always on, it shows — nonstop — what’s online that matters to you.
I just got an email from the guys over at Chumby.com and they’re about to run a 50 person beta run of sorts. I’ve applied to get on the team, and I’m looking forward to it. The work I’ve been doing recently really would look amazing on one of these, as I’ve been working on a flash version of our companies’ wind graph. Basically, it’s a real-time, on site wind graph of our weather stations. So, the Chumby is really the perfect vessel for this thing, albeit a strange one.
10:45:15 AM yarak_hasan31@hotmail.com: hello
10:45:24 AM abyssknight@hotmail.com: Hello there.
10:45:37 AM yarak_hasan31@hotmail.com: ip adresin ne
10:45:48 AM abyssknight@hotmail.com: hmm?
10:45:59 AM yarak_hasan31@hotmail.com: ip
10:45:59 AM yarak_hasan31@hotmail.com: ıp
10:46:12 AM abyssknight@hotmail.com: What about my IP?
10:46:23 AM yarak_hasan31@hotmail.com: pc ıp
10:46:31 AM yarak_hasan31@hotmail.com: computer ıp
10:46:41 AM abyssknight@hotmail.com: Any particular reason you want my IP?
10:46:48 AM yarak_hasan31@hotmail.com: yes
10:46:53 AM abyssknight@hotmail.com: And that is?
10:46:57 AM yarak_hasan31@hotmail.com: ok
Changed status to Away (10:47:17 AM)
10:47:22 AM abyssknight@hotmail.com: You’re bad at this.
10:47:31 AM yarak_hasan31@hotmail.com:
Well, I am almost finished moving all my data onto my brand new MacBook Pro 15″ when I realized I needed to move my Subversion repositories. I’m not an expert on Subversion, nor will I ever claim to be but this might just help a few people out. When I made the backups of my repository I went with the trusty ’svnadmin hotcopy old_repos new_repos’ option and had a plug and play backup to restore when the time came. Now, I couldn’t find a single reference on how to restore from a hotcopy, and it certainly wasn’t obvious to me so… Here’s what I did:
Make a .profile file in your home directory and paste the following into it: export PATH=$PATH:/usr/local/bin
Issue a ’svnadmin recover repo_hotcopy’ to start the BDB again.
Ta da, it’s done!
Strangely, that seemed to have fixed everything! Now, that might’ve been the most obvious thing in the entire world to a SVN guru, but it wasn’t to me. I did issue a ‘killall svnserve’ and then a ’svnserve -d -r repo_hotcopy’ before testing it, but it checked out with SVNx and everything looks good.
Today in my CIS4361 Secure Operating Systems class I was drifting off as the professor was doing a quick review of filesystem attacks when I heard the strangest phrase since the BouncyCastle provider for JCE: Smurfing. Apparently this smurfing, as it were, is when an ICMP echo packet is spoofed from the target’s IP address to a router, called the smurf amplifier, which then sends the request to all of the nodes attached to it who then send ICMP echo reply packets to the target. Essentially, this inundates the router and target with echo reply packets and should lead to all out network outages. Pretty neat, and with a name like smurfing, it has to be good.
Here are a few links relating to a project I am working on for my Vision class. Basically, I’m building an automated facial expression classification system. Sounds nifty? Well, that’s because it is: