I remember a few years back when the full weight and realization of Digital Rights Management (DRM) was being openly discussed and vilified. This was the music and video industries attempt to control the content they were producing. We quickly realized that if we cosign the technology, we would be removing all the freedoms that we currently enjoy in the physical world. We subsequently discussed how the Digital Millennium Copyright Act (DMCA) limited our rights at the device by limiting the ability to copy and distribute, though the law, predated and never really accounted for the boom that followed in the wake of internets popularity in the new millennium.

SOPA and PIPA are the latest attempt to shore up that gap, it takes all these concepts to a new high. I am not one for wanton hyperbole, but the enactment of SOPA and PIPA present the greatest threat to the content we enjoy and share everyday on the web. Like DMCA, SOPA targets anyone who "knowingly and willfully provides or offers to provide a product or service designed or marketed by such entity...for the circumvention or bypassing" of a Justice Department-erected blockade. However, where DMCA surgically targeted the offenders, SOPA declares all out nuclear war against the basic tenants of the internet. Mitchel Baker, is Chair of the Mozilla Foundation and I have found his explanation the easiest to bring people up to speed and is a follows:

Assume there's a corner store in your neighborhood that rents movies. But the movie industry believes that some or even all of the videos in that store are unauthorized copies, so that they're not being paid when people watch their movies. What should be done?

 

SOPA/PIPA do not aim at the people trying to get to the store, or even the store itself. The solution under the proposed bills is to make it as difficult as possible to find or interact with the store:

 

1. Maps showing the location of the store must be changed to hide it.
2. The road to the store must be blocked off so that it’s difficult to physically get to there.
3. Directory services must unlist the store’s phone number and address(3). Credit card companies.
4. would have to cease providing services to the store. Local newspapers would no longer be allowed to place ads for the video store.
5. And to make sure it all happens, any person or organization who doesn’t do this is subject to penalties.
6. Even publishing a newsletter that tells people where the store is would be prohibited by this legislation.

Google, Facebook, Twitter, and other Web companies have created a united front against the bill, and sent a letter to key members of the U.S. Senate and House of Representatives, saying that SOPA, "pose[s] a serious risk to our industry's continued track record of innovation and job creation, as well as to our nation's cybersecurity." Additionally you may have seen semi effective protests staged by Wikipedia and Google (to name two).

The most vocal proponents of the act are the MPAA, the Recording Industry Association of America, and the U.S. Chamber of Commerce (ring a bell). These are basically the same guys who treated us like potential thieves during the late 90’s in a vain attempt to protect there intellectual property. It should be noted that Yahoo has reportedly quit the U.S. Chamber of Commerce over the organization's support for SOPA.

The following TED video also spells out the danger along with a great description of the continuous fight we appear to be in as content producers, consumers, and sharers on the web.

The best analogy I can come up with is if you have an infestation of cockroaches in your home you target the infestation, you do no burn down the entire house. We have to come up with a better solution to what is a *very real* problem, I just do not believe that SOPA and PIPA are the correct direction. Ultimately this is a fight for control and I personally encourage everyone to get educated and join in!

Nokia has been going all out to promote the Lumia Windows Phone 7, the pinnacle of which was is in London, UK, back in November as a huge animation projected onto the 120m high Millbank Tower on the banks of the River Thames. Each of the tower's 800 windows were covered with vinyl, while 16 powerful projectors on the other side of the river beamed images onto it. I am really interested in finding the specs of those projectors!

I have really been disappointed with the number of games and apps on the windows phone that attempt to share the status of a game or a link from an article by redirecting the me, the user, to an OAuth page for Twitter or Facebook. My fellow app developers this is unnecessary and quite frankly annoying. There is a preferred alternative, and it is actually one of the differentiating features of Windows Phone OS, you can integrate your social network (Twitter, Facebook, Live, LinkedIn) directly into the OS and you can send status’ directly to it as follow:

    ShareStatusTask sst = new ShareStatusTask();
    sst.Status = "Share Status";
    sst.Show();

…or share links…

    ShareLinkTask slt = new ShareLinkTask();
    slt.LinkUri = new Uri("http://www.poppastring.com");
    slt.Message = "My Site";
    slt.Title = "My blog";

The experience is much better and does not require any passwords or browser navigation. While I do not expect Google+ to be included as a network anytime soon at least the main social networks are covered.

After doing a couple of presentations on the OWASP Top 10 list a couple of years back I *tried* to put together a series of viable demos that would help to illustrate the list in a more practical fashion. Unfortunately I got as far as the first two issues and never completed the exercise.

Recently I stumbled upon a really well written blog by Troy Hunt, a Microsoft MVP, who has a clear passion for  security. Troy has created a series of 10 blog posts that illustrate the OWASP top 10 from the  view of the .NET stack and ultimately makes these topics more accessible to developers like us. If you have a few moments please check out his posts (and his blog in general):

1. Injection
2. Cross-Site Scripting (XSS)
3. Broken Authentication and Session Management
4. Insecure Direct Object References
5. Cross-Site Request Forgery (CSRF)
6. Security Misconfiguration
7. Insecure Cryptographic Storage
8. Failure to Restrict URL Access
9. Insufficient Transport Layer Protection
10. Unvalidated Redirects and Forwards

Back in June Microsoft released a non-commercial Kinect software development kit (SDK) for Windows 7. The SDK includes Windows 7 compatible PC drivers for Kinect device and provides developers the capability to build applications with C++, C#, or Visual Basic by using Microsoft Visual Studio 2010 and includes following features:

• Raw sensor streams: Access to low-level streams from the color camera sensor, depth sensor, and four-element microphone array.
• Skeletal tracking: The capability to track the skeleton image of one or two people moving within the Kinect field of view for gesture-driven applications.
• Advanced audio capabilities: Audio processing capabilities include sophisticated acoustic noise suppression and echo cancellation, beam formation to identify the current sound source, and integration with the Windows speech recognition API.

A commercial version is planned for release in 2012, but I am really fascinated with what the fellow developers in the community are doing. So here are my favorite videos:

Windows 7 desktop multi touch support

Shadow Puppets

You are a super hero!

Minority Report

Coming soon?