Skip to main content

How To Defeat Piracy and Conquer The Movie Industry With One Box

Some weeks ago, a friend of mine was tweeting about the crappiness of DRM and the movie industry. Well, actually I think all my friends have complained about this at one point or another. You know what the problem is (read anything by Cory Doctorow if you need more material).

Instead of chiming along as usual, I decided to counter with:
"Why don't you as a programmer come up with something better yourself?"
The discussion that ensued gave me an idea for a business/product that I'll share here. Feel free to steal the idea and build the "BetaBox"!
Imagine we built a solution for buying movies & series with all the problems of today's services removed. Imagine Hulu or Netflix, only with *all* movies and series, not just crappy old ones. It's not like Spotify is dominated by music from the 80-90's, and the newest songs are from two year's back, right?

Additionally, all content can be streamed or downloaded onto all your various devices. 

Now, the argument against building this service is that it won't float with the movie industry. They'll never allow downloading DRM-free files, and they won't release movies as early as they would hit the cinema, all in fear of losing revenue due to less people paying for cinema tickets, and broader piracy due to ease of ripping/copying.

However, I suggest that the movie industry hasn't moved to support downloading movies, for the simple reason that they can't be bothered. The majority of consumers don't want to deal with the collection of big movie files along with meta-data. Maybe you can be bothered, but my mom can not.

But what if you had a box with software that would just handle that for you, accompanied by apps for mobile devices and consoles?

Download once, and it would organize everything for you, and make it available for streaming to every device in your household. A bit like XBMC, only it is backed by a Netflix-like professional service, or rather several of them. You could also transfer files or cache for off-line viewing (bring the tablet in the car for kids watching a movie).

The BetaBox is portable, can run on car- or embedded battery power and doubles as a WiFi-router. So you bring it with you in your hotel-room, cabin in the woods, and so on.

The next challenge is to make this device useful before the movie industry agrees on supporting it. My solution for this is for the box to take in the movies you've already own. Rip them off CD's, DVD's and BlueRays. The industry has done what they can to make it illegal to rip DVD's and BlueRays, but this protection doesn't really make sense, and several countries (at least in Norway, I believe) it is allowed to rip DVDs and BlueRays for private use. In countries where ripping is not allowed, the feature would have to be disabled, but hopefully the public would rise to change these (rather nonsensical) laws over time. Maybe one could do something like iCloud's Match thing, where the BetaBox would recognize that you're rightfully own a movie (by inserting your disk), and after that you could just download it whenever.

Now, there are some open-ended questions like how to handle synchronization between multiple boxes, clustering, whether it should support copying movies from one box to another. The answers here should try to compromise for the happiness of the movie industry, I suppose. Should the concept of "renting" movies be implemented? Maybe.

Eventually, hopefully, the movie industry would have to buckle for the market, and would move to support it in order to maintain revenue, similar to what happened in regards to iPods/iTunes and Spotify. 

Of course, the concepts here are simplified, and the idea is rather utopian. But my point is that if we as engineers were able to build a concept that was so valuable and usable to all consumers that it would easily out-compete everything else on the market, the movie industry would eventually have to go along with it. And seeing how crappy the products out there are today, I think this is actually doable. 

Someone, please think this through properly, get it funded on Kickstarter and build me a BetaBox!

Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

    -> ~/.atom/*

    -> ~/.mrconfig
    -> ~/.config/mr/*

    -> ~/.tmuxinator/*

    -> ~/.vimrc
    -> ~/.vim/*

    -> ~/bin/*

    -> ~/.gitconfig

    -> ~/.tmux.conf    

    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s

You'll get this .git/config:

[svn-remote "svn"]
        url =
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):

(Compared to regular remote branches, they look very odd because there is no remote name i…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…