April 06, 2014

Books and Music in 2013

Another year gone. Just like in years before, here's a recommendation of music and books, from what has been released during the year (in the case of music), and what I've read in 2013 (for books). Note that there are other, great 2013 music releases, that I only got my hands on in 2014, and those aren't on this list. Without further ado:
Books:

* Neal Stephenson - The Mongoliad (Books 2 and 3)
* Iain M. Banks - The Hydrogen Sonata
* Cory Doctorow's fiction - The Rapture of Nerds and Pirate Cinema
* Music - Looking For Europe
* Tech - Videojogos em Portugal
Music:

* Kokori - Release Candid Hate (Vinyl)
* Gvar - Vraii (Cass)
* Charanga - Borda Tu! (CD)
* Dismal - Giostra Di Vapori (CD)
* Mindless Self Indulgence - How I Learned To Stop Giving A Shit And Love Mindless Self Indulgence (CD)


June 19, 2013

DRM hopefully to be fixed in Portugal

DRM bills being discussed, with a physical DRM'd book
sent by
ANSOL serving as an argument
2001's European Directive 2001/29/EC says that member states must legally protect DRM measures, making it illegal to circunvent them. But it also states that they must ensure that it doesn't prevent uses permitted thanks to copyright exceptions (for instance private copy).

The transposition of that directive to the Portuguese Law (CDADC) was made in 2004, but the way that CDADC ensures that copyright exceptions is protected doesn't work. CDADC states that you can't circunvent DRM, but since you must be able to exercise the copyright exceptions, it states that in those cases you have to request the means to achieve your objective to IGAC (a state administration service). The problem is that if you request those means to IGAC, they won't hand them over to you because they don't have it.

Well, that is now going to change. Two Portuguese parties submitted to the Parliament a couple of bills with the same basic objective: to change CDADC, changing the way the law ensures the right to copyright exceptions by simply stating that if the DRM in question prevents any of those exceptions from being exercised, then you can circunvent them in order to exercise them. Simple and effective, right?
These two bills were debated in the parliament, and then approved in generality. Now they follow it's natural path, to a comission that will merge both bills and do amendments (amendments that will not change the essence of the bills, I hope), and the final text will be again voted in the Parliament, who can turn it into Law, finally giving back users the rights that were taken from them nine years ago.

Timeline:



  • 2001 - 2011/29/EC EU directive is published
  • 2004 - EU directive is transposed to Portuguese Law
  • 2013-06-12 - general discussion about two bills aiming to fix the Law
  • 2013-06-14 - both bills approved in general
  • 2013-06-26 (10:00) - Comission meeting scheduled to discussion and vote of both bills in speciality
  • March 21, 2013

    DRM in HTML5

    Stop the Hollyweb! No DRM in HTML5.

    Many people have doubts regarding how can possibly be an issue of having DRM on HTML, the foundation language of the entire web. One person in particular had the doubt of "how can it be possible that DRM (closed by its nature) is inserted into a standard?"

    I have replied to her about it (in Portuguese), but I think that, with some adaptations and a translation, this text might also have a wider use for those of you trying to understand HTML, standards and DRM. Oh, and don't forget, click on the image in the right to sign a petition against DRM on HTML.

    The "short answer"

    You should attend to the Document Freedom Day 2013 celebration event nearer to you: they're happening starting today until April all around the world. There, I'm sure, there will be people knowing and willing to explain to you any questions regarding open standards in general and the "DRM in HTML" issue in particular.

    The "long answer"

    A standard should be considered open if it complies with a number of requisites. Here's the list (taken from this page, that explains each point better):

    An Open Standard refers to a format or protocol that is:

    • Subject to full public assessment and use without constraints in a manner equally available to all parties;
    • Without any components or extensions that have dependencies on formats or protocols that do not meet the definition of an Open Standard themselves;
    • Free from legal or technical clauses that limit its utilisation by any party or in any business model;
    • Managed and further developed independently of any single supplier in a process open to the equal participation of competitors and third parties;
    • Available in multiple complete implementations by competing suppliers, or as a complete implementation equally available to all parties.
    Unfortunately not every format is an open standard, or, in other words, doesn't comply with the previous points. If the proposal to have DRM on HTML5 is accepted, HTML will stop being an open standard, since it will stop complying with the second requirement of the list.

    In more detail: the proposal on the table is called EME (Encrypted Media Extensions). An HTML document can include EMEs, and the specification of EME enables the website to require a certain "Content Decryption Module" (CDM). And here lies the problem: CDMs aren't standards (much less open standards!) and the EME specification doesn't include or refer to any specification of any CDM. In other words: the definition of open standard we just saw isn't complied, because to implement HTML5 we have to implement EME, which has to accept any CDM, which isn't a standard and so we cannot implement.

    In other words, with an example: I make a website, and put there a media object (video, for instance) using EME, and I specify in the HTML document that the EME object needs the CDM module (which is a form of DRM) called "OneTwoThree". Now, if you want to see that website, you need a web browser that knows how to undertand HTML5 and EME (both possible since there's the specification), and the browser then needs to get the CDM called "OneTwoThree" (imagine it as being a browser plugin, not unlike Flash) and use it to play the video. The problems are obvious now: what if the CDM only exists for one specific Operating System? What if the CDM isn't free? You know... the thypical problems of a non-open standard format.