Delicious

There has been a lot of buzz going around about delicious being phased out as a yahoo product. Well, we can’t say for sure that it will go away, but you can pretty much guarantee they are not going to focus any more development time into the product. And quite frankly, that may not be a bad thing.

Competition has popped up in PinBoard. But I would argue that bookmark competition has been around for a long time. I used to work for a bookmark company called Murl.com which was working on making more of a personal information manager before they ran out of cash. Bookmarks are where Murl got its start.

The thing that I use delicious for is not to discover new sites. I rarely actually log into the web UI. What I use it for is keeping track of sites that I may need later. Now that I have been using Instapaper, I don’t have the need to keep tabs open for days / weeks on end until I have time to read an article. I simply tag it and come back to it when I have time. Delicious used to fill this role for me but now it is purely a depot for me to dump web pages that I may need sometime in the future. And even then, I’m relying on it less and less.

While its sad to see it go, I can’t say that I’m overly surprised that yahoo has killed it. They have a history of buying properties and not doing a whole lot with them. I’m still shocked they haven’t found a way to screw up flickr.

So whether Yahoo decides to sell it or shut it down, it won’t affect me too much. However, I do recommend that you backup your links daily.

Backup Code:

curl -k --user username:password -o backup.xml -O https://api.del.icio.us/v1/posts/all'

The convenience of the internet

I recently ordered tickets online for a Broadway show that’s coming into town this fall. I was expecting the price to be fairly pricey seeing as this is a pretty hot show and its the first time that it is coming to our town.

There are some fees that I don’t really care about. Restoration Fees to keep the facility looking nice and operating well is fine by me. However, $4.75 for the convenience of ordering via the internet?!?! PER TICKET!!!! Are you freaking kidding me! If anything, it should be EASIER for me to order via online. Sure I get that there are costs for hosting, bandwidth and software. But c’mon, that has to be cheaper than additional phone lines, personnel, benefits, overtime, etc.

picture-10

Behold the convenience of the internet. If it was going to somewhere other than the Civic Center which I know can always use the cash to bring in great shows (and Wicked is GREAT from what I hear!!!), I might be a little more upset. But seeing as this is supporting the performing arts at its highest caliber, I’ll let it slide this time. But good grief!

Is there really that much money in it?

Disclaimer: I’m not a Comcast subscriber, but I play one on TV

Comcast has me scratching my head. A friend of mine pointed out the following post on the Comcast goofiness. For a long time now they have been messing with DNS and if you happen to screw up and look up a site that does not exist in DNS, you get the Comcast ad page. Many of the tech savvy folks out there simply got around that by putting up their own caching server or using opendns. I know I did when I found out that Mediacom started messing with DNS like this.

Apparently they have upped their game by routing all DNS traffic, no matter what, to their servers. You have no way around this, you WILL use their servers.

I disagree with the first practice of just having a * domain that has everything mis-spelled go to a certain site of yours. Now that they have taken this to a new level, I think it is quickly climbing up the all time ranks of dangerous and stupid.

Really, dangerous? Well, say I’m a person that has highly questionable morals and decides that the best way to attack a competative ISP is to go after their DNS servers. I could try and do some sort of DDoS. Or, the better, more devious approach is to attempt a DNS cache poisoning on their servers. Not always the easiest, but when done properly can have some pretty devastating effects. Now, I trust that Comcast has employed some top notch admins over there so I highly doubt that they are going to let their guard down here, but we’re all humans. We still make mistakes.

Why is this stupid? Honestly, do you click on the ads on one of these pages? Or do you swear to yourself, type it in correctly or load up google and search for what you really want? It just seems like a lot of hassle to implement and all they are really doing is pissing off their customers. They’re trying to milk every last cent out of them and the customers are not stupid. They know what comcast is trying to do. They’re pissed off and eventually they will leave.

The sad part is, other ISPs have already taken up the first goofy solution that Comcast put in place. Its only a matter of time until more people adopt this new tactic. For me personally, I’m going to smack the crap out of the first person that mentions this as a solution that we should deploy. I set up our DNS servers and I refuse to break the internet. I also have a higher respect for my customers. They’re all intelligent, reasonable, and good looking right?

40 never looked better

Happy Birthday to the RFCs. The RFCs (Request For Comment) are the a documents published by the IETF (Internet Engineering Task Force) describing the behaviors to the various internet protocols. Basically, these documents make up how the internet should work. Should being a very important word here. Many programmers are either too lazy to properly implement them or there are some companies that like to embrace, extend and often break the RFCs.

40 years ago today, the first one was published. The NYTimes has a nice article on the background of how the RFCs were started. Pretty cool stuff.

XCode Errors

By trade, I’m a PHP/C programmer and rarely have time to really work on some fun stuff at home. But recently, I have been trying to spend some more time working on some fun projects and getting my hands dirty with XCode and the iPhone SDK.

I recently downloaded the latest and greatest version of XCode and overwrote the beta versions I had been running with before. The installation went fine and I decided I would load up one of the demo apps to make sure that everything was indeed still working as I expected.

Unfortunately, I was greeted with this:
XCode Error

I know, pretty clear what that error is right?

If you’re new to XCode as I am, you were probably scratching your head thinking this is really messed up. The console logs didn’t make it much clearer so I figured that something got messed up during the installation. Since I had been running the beta version before, I must have missed something in the instructions or a check box in the installation that is not causing an issue.

I tried un-installing the iPhone SDK and re-installing to see if that fixed the problem…no luck there.

I tried removing the /Developer directory and re-installing. Still no luck.

I re-applied the 10.5.5. update as I had a few issues with it when I originally installed it. Then I removed the /Developer directory again and re-installed the iPhone SDK. STILL no luck.

At this point I was starting to think that I had some library that was b0rked beyond reason and the only easy way to take care of the issue was to blow away the machine and re-install.

Luckily, I happned to find this post.

Simply removing the Info.plist from my root folder on the hard drive solved the issue.

What a freaking pain in the ass it was to find that simple solution. Thanks to Google and some helpful coders on the internet, I’m happily playing around with iPhone development.

Hopefully this blog post will return the favor or at least get their page a higher rank so others can resolve this issue if they run into it.