News for hackers. Stuff that matters.

garby

Re:Why public lands must remain in public hands on Wednesday May 03, 2017 @01:33PM (#14258080)
Yep, that is definitely something I am actively looking into - this was my first year applying for a muzzleloader tag for the Colorado elk season.

P.S. I'm also a BHA member and huge supporter of what they are doing to preserve public land access (http://www.backcountryhunters.org)

Re:Why public lands must remain in public hands on Wednesday May 03, 2017 @10:15AM (#14255816)
As someone who loves to spend weekends in the outdoors hiking, hunting, and fishing, moving to Texas really highlighted the importance of keeping these lands public. As the article mentions, Texas sold nearly all of the federal land it was granted and as a result is currently about 95% privately-owned.

For most hunters, this means that you either have to lease private land, which is becoming increasingly more difficult and expensive (think thousands of dollars annually), or hire an outfitter for exorbitant fees. This has priced many people out of hunting and will continue to do so as populations and land development continue to rise. I, personally, have been looking for a hunting lease within a couple hours drive of Austin for the past three years and have not been able to find one - and that's with a budget of over $3k/year.

Without transfer protections that mandate keeping the land public and accessible perpetually, I don't know how any outdoorsman could be for this "transfer".

Re:Honest status reporting and AWS service status “truth” on Friday February 10, 2017 @02:39PM (#13618208)
In a perfect world, this makes sense. For us, we had an ElastiCache redis multi-AZ replication group whose primary was in the affected AZ. It refused to fail over, even though automatic failover was configured. Apparently there is no way to force this failover, even though people have been asking for such a feature for years. I'm curious what you would do in this situation, besides not using ElastiCache?