Name changing entitlement?

Posted August 23rd, 2010 at 6:51 pm

Originally when I read this I was going to title this, Google’s CEO is a d-bag.


Original

Eric Schmidt suggested that young people should be entitled to change their identity to escape their misspent youth, which is now recorded in excruciating detail on social networking sites such as Facebook.

Cause god forbid there are actually consequences for being a dumb ass. Not to mention I think the youth of today has a little too much entitlement. Maybe if enough youth and adults alike fail miserably with social networking they might actually learn something for themselves.

Kind of mixed message from this article.

If you have something that you don’t want anyone to know, maybe you shouldn’t be doing it in the first place.

Bet you didn’t expect to see a Huffington Post link did you? I like to see what crazy people read from time to time.

After looking around a little I couldn’t find an article where he actually said it should be an entitlement. Turns out this was just the headlines that was pulled from a Wall Street Journal opinion piece but made all sorts of news as a quote.

Fix .SVN file permissions with BASH

Posted August 12th, 2010 at 3:38 pm

Occasionally I need to checkout a SVN repository as root to get the the correct file structure. I don’t like any of my application files living in /public_html, always one level up. For most enviroments the user account one level up is the user’s /home directory.

A user named bob will log in to /home/bob and the publicly facing directory will be /home/bob/public_html, and the application would live in /home/bob/app with /home/bob/public_html/index.php pointing to the app.

Using the standard SVN file structure the repository would look like http://example-repository.com/bob/trunk/ with the rest of the files inside /trunk.

If you try to checkout from user bob you’ll end up with /home/bob/trunk/app. There are lots of ways around this but I prefer to just checkout as root. We can use chown to fix the file permissions. In some cases you’ll want the group to be nobody. We don’t however want the group nobody to own any svn files.

One liner to fix that.

find -name '.svn' | xargs chown -R bob:bob

This will recursively search for any .svn files and run chown.

A preview to a government regulated Internet

Posted July 21st, 2010 at 10:33 am | Updated: 7/21 at 10:35 am

The irony of this is truly entertaining. At this point you might as well have sense of humour about what is going on. In a previous post I chronicled the origins of Net Neutrality. In a nut shell geeks sharing pirated movies cried “packet equality!”, when their ISP started throttling their traffic. Who will save them from the big greedy ISP fat cats?

I’m from the government and I’m here to help.

Over the weekend, “law enforcement” agencies shut down 73,000 blogs at once. The details are bit sketchy right now but it looks like it was over copyrighted material although there is plenty of speculation since nobody is talking.

A single individual was providing free hosting for wordpress blogs and collecting the revenue from advertisements. He had over 73k blogs a single hosting account. This individual came home to find the following email from his data center.

Due to the history of abuse and on going abuse on this ‘bn.***********’ server.

We have opted to terminate this server, effective immediately. This termination applies to: bn.affiliateplex.com

Abuse Department
BurstNET Technologies, Inc

From this email you could assume several cease and desist orders where sent prior to shutting down the service. Normally this is for some sort of copyright violation. After sending the WTF? response the data center replied with …

[...] Bn.xx*********** was terminated by request of law enforcement officials, due to material hosted on the server.

We are limited as to the details we can provide to you, but note that this was a critical matter and the only available option to us was to immediately deactivate the server.[...]

The data center refunded his money but has refused to provide access to the data. Probably because they no longer have physical possession of the data. This is just a guess but there are probably a couple people out of those 73,000 blogs that would like their data back. Good luck with that.

Once your data leaves your home computer for the cloud its no longer yours no matter what your told. A third party gives you access to your data that is most likely stored on a machine owned by yet another entity. In this case both the means to access and the data itself was removed. I don’t begrudge the data center, they had no choice.

The solution is to never leave your critical data in one place. Natural disasters, equipment failure, big government or a bankrupt company can wipe out your data in a second. I really hate to say I told you so. Ok I’m lying, I actually enjoy it in this case.