...Ending with some Good News! [US and Net Neutrality]

The last time I was on a political-roll, it was a Trilogy. Now is no different. To end off the Political Control of Digital Media Trilogy on a high note.

FCC to Enforce Net Neutrality

The number one issue of the critically minded Web-Generation is the issue of Net Neutrality. The just and responsible freedom of the internet.

One thing I would say so that there is no confusion out there is that this FCC will support net neutrality and will enforce any violation of net neutrality principles.
---Julius Genachowski, FCC Chairman

This is a very reassuring statement. I usually condemn when a political group copies off a law or model from another country when that model or law is broken. But this is one of those things that needs to be copied off everywhere. Finally a high up victory for Net Neutrality.

Now, Neil Berkett can suck it!!!

Speak Out On Copyright [Canada]

Following up on my latest post, I highly encourage all the Canadian readers of my blog to check out...



SpeakOutOnCopyright.ca is a free public service web site provided by Michael Geist. Dr. Michael Geist is a law professor at the University of Ottawa. He's someone I highly look up to for everything he's doing on the legal and technology front of various issues.

Also, thank you Jack Zhang for the extra exposure on my last post.

Why Politics and Creative Media Should Not Mix...

An issue that is dear to me is any effort by the government (any - US, Canada, UK... there's no difference) to poison the creative process and creative media with ridiculous control. I strongly believe in Copyright, Intellectual Property, and Creative Licencing. However, without exception, all the current political efforts are all harmful to everyone. For example, if Bill C-61 [Canada] passes, every single Canadian citizen, regardless of where they stand (artist/designer/media or consumers), will feel the repercussion of a Bill that is harmful to the very issue it's supposed to support or protect.

Here are some links to make you sick about the current reality.

• The Death of Analog
• The MPAA's Disingenuous Argument Against Fair Use
• 10 Years of the DMCA
• The Truth Behind [Canadian] Bill C-61
• Aggressive Corporate Rights Holders

Wherever you are in the world, speak out to your government about your concern. Help them understand the reality.

Knowledge Review 7 Poll Result

Well, it was a perfect score for the Technical display option.


Time to code it in. I had the pseudo-code down for all the options, so it's not that much work.

Knowledge Review 7 Node Display

I got on this Blog this morning to get something for work when something hit me. You see, prior to this post, the screenshot of the Knowledge Review 7 DAG preview was on top of the page. The designer in me likes to make stuff look pretty and functional. Now, with my changes, why does everything look like it's a child of NodeA even though the spacing is correct?


The addition of the vertical bars (aka the broken bar character) at the beginning of any line that's not at the root created what I consider a problem. It can be very misleading, especially if you're checking the DAG for the first time. It's bothering me to the point where I feel I have to change it. There are three options.

The original 3DBuzz design

This is the way it's done in the videos. There are no vertical bars at all, so the only visual queue of the depth of a child to its parent are the dashes. It's simple, but on the down side I feel it's not good looking enough.

Option #1 - Simple Design

A simple layout of the Nodes similar to the original design, but without any dashes going through the full line until it's child. They're just below the parent. Another very simple design, but there's not a lot of vertical depth. By that I mean that if Parent1 has a lot of childs, there's not a lot of visual vertical reference between Parent1 and Parent2.

Option #2 - Technical Design

This layout is much more complex visually. It looks very technical, but everything is represented. You can follow each parent and child visually. However, it can be extremely busy on screen.

((EDIT: I just found out how to use Extended ASCII and Unicode in a console application in C#, so imagine the above screenshot but with much smoother lines))

Don't change anything
Stick with the current design even though it can be very misleading.

Essentially, it's a battle between visual simplicity, great aesthetics, and functionality.

There's a Poll on the right. Go vote now!