I was sitting at a coffee shop today I was disappointed I forgot to ask for the wifi key. Now I could totally sit here and crack the WEP key, but that takes precious CPU and battery life and well, I just wasn’t that interested in getting the tools to compile for my Mac. This led me to wax poetic about the days I used to have a tether to my iPhone 3G and I thought … “Man, I would sure like to be able to tether again;” but the last time, that didn’t go over so well. The last time I installed the tethering packages from Cydia, I lost access to voicemail for 2 weeks, couldn’t get them to uninstall, yada-yada-yada, annoying experience. But today, I actually had time to think about how to solve this issue and then it hit me: I’m a moron, I should have seen this last year. Five minutes later, I was on the net.
Continue reading ‘Stupid iPhone and Stupid Tethering’ »
Alright, I goofed and accidentally updated a stable revision that I thought was being tested correctly and well … it wasn’t. So if you’re having issues with Code Snippet, just roll back to version 2.1.5 and life should be better.
Sorry for the screw up, but this has actually brought to light some bugs I never even knew were there so I’ll have those fixed up soon and we’ll be rolling again.
Download for 2.1.5 is here: http://downloads.wordpress.org/plugin/codesnippet-20.2.1.5.zip
It’s been a long time since I’ve actually had to think about using Denyhosts and if you’ve read my post before, you’ll know I’ll swear by it’s functionality.
Recently, we’ve been getting hit by lots of SSH brute force attacks at HTG … and hit hard. The most recent stat was more than 2400 failed login attempts from over 50 unique attackers in a 24 hour period. Most times, I don’t care as long as they don’t get in … but then I sat back and thought, “Man, those fsckers are probably costing on bandwidth somehow.” and that’s where I draw the line.
So once again, Denyhosts is up and running, more than 60 hosts have been banned just today and more are going to get taken down. Now, if only I could come up with a good legal reason to just give my servers the capability to attack back … but that’s not legal … yet.
There’s an updated version of Code Snippet. Fixed some bugs with GeSHi and the WordPress plugin API. Their site is not showing the right information now, so here’s an accurate link:
http://downloads.wordpress.org/plugin/codesnippet-20.2.1.4.zip
Let me know if there are any problems over on the Code Snippet page!
Just because I spent so much time looking for this last night and found so many broken carrier data files, I figured I’d keep this around for me.
Instructions
- Make a backup of your /Library/iTunes/iTunes Carrier Support/ATT_US.ipcc file.
- Quit iTunes
- Open Terminal and type “defaults write com.apple.iTunes carrier-testing -bool TRUE”
- Open iTunes, select your phone and press “check for updates” while holding down the ‘Alt’ key on your keyboard. You will be prompted to select a file. This is the one that worked for me after numerous other failures. (found in gizmodo’s cache somewhere)
- After you load the file, make sure you restart the phone
Instructions for Windows are the same, but you’ll have to use the Windows Paths for stuff (C:\Program Files\iTunes\blah blah blah).
Right, and I’m not responsible for you running up a trillion dollar bill with AT&T or if your spine curves or if your teeth yellow or if you drink rat poison because you fell in love with a rough trick named Jim or anything else as a result of you trying to do something to your bejebus phone
Dear Facebook,
Your iPhone app is great … almost. Please fix the extremely annoying bug that doesn’t allow me to use apostrophes. It’s really annoying to have to type out “does not” or “do not” in place of “doesn’t” or “don’t.” I know, I could override the auto suggest and go with “dont,” but that just pisses me off. I already commit enough infractions against the English language without purposefully littering misspellings all over just because your application has to stupidly provide a server error every time I include an apostrophe in a comment.
Sincerely,
Wyatt
I don’t know why I thought to do this especially since I think taking pictures on a cell phone is relatively stupid; however, I had the parts laying around and figured, “Why don’t I just see what that looks like?”
Supplies
- Disposable Camera: $0.00 (ask your grocery store for an empty one)
- iPhone: $0.00 (fell off truck)
- iPhone Soft-case (mine is an Incipio and it fell off the same truck)
Instructions
- Disassemble the camera and salvage the len(s) without zapping yourself. If you really want, you can zap yourself because some people like that … you freaks.
- Put the lens inside the soft-case
- Put your iPhone in the soft-case
- Take macro pictures at a glorious 2.0 megapixels
Update: After writing this, I actually took the time to see if I was original as I though did a quick search at instructables.com. Turns out, I’m not that creative: Cheap iphone macro lens for barcode scanning
I don’t normally re-link to other blogs unless I really think it’s worth mentioning; however, there is currently a debate between boxee and what I can only assume is a content provider over here.
To me, it’s enlightening to the the other side of the arugument for a change. Generally, the only thing on the Internet is how the people on the Internet are always right and how other media/content providers are crazy.
I’ve read through both sides and, well, I just can’t agree with the content providers. I’m all for a la carte and I personally find the arguments made by the content provider to just be frustrating. One in particular about how “consumers think they want a choice” really got me annoyed. The plays into my hatred of how media really helps control the way the brainless masses think; however, freeing up that thinking and allowing real choice and hopefully removing the brainless from the masses.
Last night we got to check the beer and it’s done!
Pre-bottling taste test seems to show that it has a very smooth amber-styled ale flavor with the essential hoppie notes. I hope it will taste as good if not better after fermented in the bottles for a few weeks!

One style of bottle

Test and Filter

Some of the final product
======
That’s it! Success has been had and I’m definitely going to do this again with everything that I’ve learned from this experience (a.k.a., no candy thermometers).
Some how, I got this crazy idea in my head that I should try making my own beer. I’ve just finished sterilizing everything in the kit and now I’m moving on to the fun part … actually trying to brew beer.
1. Steeping the Grains
The hard part about this is trying to get the steel pot up to 170F without making it insanely hot to deal with later when I have to make sure that I don’t over boil the silly thing.
And the waiting…. We finally got to the appropriate steeping temperature so now there’s 20 minutes of waiting before we can bring it to a boil
2. Adding in Malt & Extract
Finally finished steeping. Have to let the grains drain and then add in the malt and extract
Added the ingredients and now we wait till it boils
Boil dammit!!!
Just broke the candy thermometer. It is now officially a fiasco.
Finally got to add the hops. Hope I don’t make it over boil.
My stove is having trouble keeping the heat up…moving to the lid.
Brand frickin new stock pot lid started snapping and developing hairline cracks…moving to a beefier lid and walmart is going to get a nasty-gram.
3. Beginning Fermentation
Starting the rapid cooling of the boiled sticky mess.
Adding in the yeast and the cool little air lock thingy.
And the beer has a new home for the next week
=======
That’s all for now!!! Tomorrow, we’ll have to see if the yeast is actually working the way that it’s supposed to and that will be the tell-tale sign of whether or not we have a chance at success. Stay tuned!















