With MyElectedRep, I get a view into the people that are representing me. Whether I agree with the votes that they’re making on my behalf or if I would like them to vote another way.
To help me make decisions on votes, I can look at how some trusted organizations recommend I vote and read the analysis that they’ve provided.
With each Representative, I can vote on upcoming legislation, so that they can determine how the district feels. I can also go through their past votes and either agree or disagree with the votes that they’ve made. If I feel strongly about certain votes, I can contact my Representatives directly to let them know how I feel.
Once I’ve gone through the different bills and voted on the ones that I wanted to, I can look at how each Representative scores. They get a district score as well as a personal score. I can then use this score to determine if I should vote for this person to be my Representative again next time or if someone else would do a better job.
With 3 of the 4 Republican candidates for President being heavily sponsored by single donors with $100+M in assets are you feeling more or less confident that after the next election cycle our elected officials will represent us and not the super wealthy that paid for their campaigns?
The only way we can keep our Representatives accountable is if we vote and show them how we want to be represented.
We need a place to point to, where we can show elected officials that they’re not doing their job. A place where we can show that on a certain item a district wants to vote one way. Then we can score our Representatives on whether or not they listened.
By measuring the votes that each Representative makes, it becomes less important to control the money that they receive.
There’s been a lot of discussion over documents coming out about Google’s strategy with Android. Google wants to use a Carrot and Stick strategy with Android to try and maintain control of the platform. This involves giving hardware manufacturers that behave early access to new code. It also meant that the code is developed in private and only released after the fact.
I don’t care what Google or others say, this isn’t open source. This is published source. There is no way to see bugs, contribute a patch, or take part in discussions on development. The only saving grace is that Google is publishing their code with a fairly unrestrictive license.
What this situation is screaming for is to have someone with a desire to actually behave in an open source manner to come along and fork the code. Then allow developers to contribute to that branch and let Google go it on their own. My hope is that Amazon will do exactly that with their fork of the Android code base.
I was seeing an annoying issue with a webapp having trouble shutting down cleanly. I would issue the tomcat stop command and most everything would shutdown, but I’d get this error:
Exception in thread “Multicast Heartbeat Receiver Thread” java.lang.NullPointerException
at org.slf4j.impl.Log4jLoggerAdapter.error(Log4jLoggerAdapter.java:493)
at net.sf.ehcache.distribution.MulticastKeepaliveHeartbeatReceiver$MulticastReceiverThread.run(MulticastKeepaliveHeartbeatReceiver.java:137)
After the error, the Multicast Heartbeat Receiver would not shutdown and would just hang. Eventually you would have to kill off the java process manually.
Doing a quick search found this page. With a small snippet added to the web.xml to add a shutdown listener everything shutdowns cleanly now.
I guess every software engineer should be writing their own competitors to Google and Facebook in their garage (in a future post I’ll include pics of our garage data center). Because of issues I saw with Facebook, I created ReadPath. A social network with more of a focus on privacy and news sharing. It’s currently about 70% done. UI still needs lots of tweaks and there are some features that need to be completed.
One nice bonus of running ReadPath, is that it is constantly spidering content from RSS feeds for the news reader. The other day I realized that I’ve now stored a full billion content items going back several years. So of course having that much content I had to create a search engine to mine it. So, I created MiniSearch to play with different concepts involved in running a general search engine. There are a lot of things that turned out to be a lot harder than expected.
Currently the index is in the process of being built and only includes 20% of available content. There is also a lot of work to be done with ranking still. I’ll post again when I think it’s in a more usable state.
With the release of Firefox 4.0 today, I’ve switched my default browser back to Firefox. Chrome had taken over for awhile because it was cleaner and faster. The latest Firefox seems to be just as fast now and I prefer having access to Firebug when I need it without having to open another browser.
Jaimie has organized a webinar to discuss what it takes to manage a large scale virtualization project.
One of the speakers, Mr. Brodhun, is uniquely qualified on this subject having previously served as Technical Director for Enterprise Standards and Technologies for the United States Marine Corps, where he oversaw the deployment of approximately 2,300 ESX hosts and nearly 7,000 virtual machines across 167 sites.
Regardless of the size of your virtualization project, you’ll learn how to maximize uptime and performance of mission critical applications, while eliminating hidden costs that can decrease virtualization ROI upwards of 50%.
I just stumbled across a little feature on the appleTV that I hadn’t been aware of before. It appears that if you create a playlist in the iTunes library that the appleTV is connected to. Then put streaming urls into that playlist. When you then go the internet tab on the appleTV, there will be a playlist menu item with those items in it. This way you should be able to get whichever streaming media that you want on your appleTV.
Ever since I moved out to California, one of the things that I’ve secretly wanted was to be able to listen to my favorite music while driving. The problem has always been that my favorite channel by far is the Vocal Trance channel off of Digitally Imported Radio. So this meant that I would need to be able to stream internet radio while driving in the car.
Well, today that day has finally arrived. I noticed yesterday that DI has an iPhone app that allows you to stream their premium channels over 3G. I was listening today for about an hour while out running some errands with Caitlin. I only lost the signal once for about 5 sec while driving in some hills, the app does a great job of buffering and keeping the music going. The quality is great and with ~1hr of streaming it only used 25Mb of data according to the built in meter (I’ll have to double check with ATT’s meter).
One of the greatest things about the app is that if it does cut out for any reason it can determine that it’s at the end of a stream and gracefully fades out so that there aren’t any jarring cuts in or out. Every streaming app should copy this.
For Chrome on the mac, it appears that RSS auto discovery is not included by default. This is the feature that puts a little RSS icon in the URL bar when the page that you’re on has an RSS feed available. In order to enable this feature for Chrome on the mac you need to install this extension. This is an extension from Google and seems to work great.
Then if you find a RSS feed that you’d like to add to ReadPath, drag the link below to your bookmark bar.
I’ve turned off comments on this blog for now. While I’ve gotten some great comments in the past, the volume of spam just isn’t worth the hassle. Instead I’ve put a mailto: link at the bottom of each article. This is the best way to get ahold of me anyway. If you send something relevant and worth sharing I’ll add it to the blog post.
Oh, I changed the name of the blog as well. Not as worried about having my real name on the web anymore.
I’ve spent the last several days playing with and configuring CDH3B2 with Hbase. My test cluster is using an ESXi server with 20Gb of ram to boot up a bunch of CentOS5 VMs. Definitely not something that you’d want to run in production, but it works great for testing. Actually helps to expose some bugs due to the slow IO of running a bunch of servers on the same disk.
My production cluster is still running HBase 0.20.3 and has performed flawlessly. It has a table holding half a billion content items, taking up several terabytes of space, and has made it through several disk failures without a hitch. However, I’m looking at the Cloudera distro because I’m not happy with having to repackage everything, test it out, push to the live cluster, and then retest to make sure that everything made it properly every time a new release comes out. I’m hoping that using the Cloudera distro will simplify a lot of this. I’m also hoping that with the patches that they include and testing being done that I’ll have a more stable cluster. I had a real bad experience with the 20.4 update which is why production is still on 20.3.
One major problem that I still have, even with the Cloudera distro, is that the LZO code isn’t included due to licensing problems. I’m really hoping that the new compression options can be packaged up soon so that these libraries don’t need to be maintained separately any more.
A couple quick notes that I found from my testing.
The way that HBase interacts with and manages zookeeper has changed. It’s more like running an unmanaged zookeeper setup. I found that not only did I need to make sure that the zookeeper configs in the hbase-site.xml needed to be correct on all of the servers, but that when I ran map-reduce jobs against HBase that it seemed to be reading from /etc/zookeeper/zoo.cfg and that this needed to be correct on all of the regionservers. I initially had only edited it on the server running my zookeeper instance. I also added the file to the HADOOP_CLASSPATH in hadoop-env.sh but I’m not sure that that’s required.
I wish that there was a better way to manage the HADOOP_CLASSPATH and it’s inclusion of the hbase and zookeeper jar files. I’m trying to find a way so that this doesn’t need to be edited each time I update the software to a new version.
I had to change the value for dfs.datanode.socket.write.timeout. On the live cluster I have it set to 0 which is supposed to mean no timeout, but it appears that there is a bug with this latest version that doesn’t respect that value properly. So I just set it to a high number.
There’s been a lot of discussion over 
