oreilly

The judge has also: Ordered details on any other subjects caught in the illegal surveillance, allowed for Dotcom and his co-accused to sue the New Zealand police and spy agency for damages and allowed for those damages to include a copy of all data seized during the raid

(Echelon is an intelligence network of five countries: New Zealand, The United States, Australia, Canada and Britain)

Current politics in New Zealand are unlikely to see this a terror or hacking issue. This is the agency responsible for the jobless, and they are a very low priority mainly used for political diversion.

Keeping in mind governments can screw up this badly.. the security errors some startup's launch with don't seem so bad.

A lot more information on this can be found in the NZ Herald (Major newspaper) here: http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&obj...

Working out the licensing for this is quite the challenge.

It uses a duel licensing (AGPLv3 / Commercial) setup. How AGPLv3 applies to web applications is a significant grey area, and could imply an expectation that all javascript code of the application needs be AGPL also.

Answers in the forum are vague and no clear indication has been given to when a commercial license is is not required.

TL;DR: Want to use this in a web app? Pay for a commercial license or consult a lawyer

As opposed to removing the hard drive and reading the data directly...

This can be very useful http://freelanceswitch.com/rates/

It'll let you know what you can charge based on your circumstances - consider it a bottom line figure. Markets are such that supply and demand will alter this (if your skills are short supply, like being one of the few developers in the area, it's likely you can charge more)

It wasn't done in the same bills related to Christchurch. Rather, during the 'overtime' to deal with the aftermath of the Christchurch quake, this bill was promoted quickly also.

Doing this speeds up the process and avoids a huge amount of oversight, consideration and public input, and has very much caught the NZ public by surprise.

It's unlikely we (NZ public) will get organised enough to change this, and past laws with significant public outcry (which this doesn't have yet) have stayed without review, as referendum's are not binding in NZ.

NZ does have a major point of difference from the US - the courts will often "award" the costs of the case from a successful defendant to the originator.

This tends to discourage abuse of the legal system for intimidation, as there is a risk it will backfire on you and you will end up paying for all lawyers involved.

If we lack discussion, it is only because there are not enough good questions, or those questions are too hard to detect.

Maybe we could get better results by identifying unanswered questions.

Change the ratio - rather then 1:1, give less points for an article submission and more for meaningful comments.

Jasonkeste's idea for tying reputation to comments could be done with an icon. Our (New Zealand's) equivalent of ebay does this quite well.

Anyone got this to work? My attempt ended up with an encrypted packet size over the 1500 byte limit.

To log in via SSH, you (should) have a key, and a password for that key. To sudo on the server should require a different, complex password for the paranoid admin. (So 2 long passwords and a key to gain sudo priv's)

For platforms where an older version of python is standard, can that not be worked around by using virtualenv?

Use the same system that decays a post's weight on the front page to decay a comments weight on a thread.

This will balance out the uneven distribution of karma that is talked about above, as new comments will be seen and given a chance to voted on even well into a conversation.

Having done this, comments that stop being relevant to the conversation should drop to the bottom and naturally attract less attention. Ideally, this will leave trolling posts ignored. (This can be helped further by having user selected timeout apply. If comment / responses are mapped as a tree, hide all branches that have no new activity for the past x hours, allowing users to change x as they choose. Give visual feedback to a comments age by fading old comments)

This solves the 'income' end of the system, as karma should now be distributed a little more evenly over time.