Some references, JURI is a committee from the European parliament. JURI is about the legal review of potentially new EU law (directives), it's a kind of legal advisor for the European parliament.

They had indeed the 1st March a vote about a draft report concerning "Permitted uses of orphan works".

http://www.europarl.europa.eu/document/activities/cont/20120...

Now if we look in Oeil (the database of all the legal document status in the EU instutions):

http://www.europarl.europa.eu/oeil/popups/ficheprocedure.do?...

The proposal will go in 1st reading at the parliament.

You can find back the final amended version by JURI:

http://www.europarl.europa.eu/sides/getDoc.do?pubRef=-//EP//...

The vote took place the 1st March 2012 at JURI (cf. Oeil) but I can't see the result mentioned in the blog post.

Unrelated to the topic, but my god what a incredibly fucking unusable site. I don't how what kind of javascript bullshit is going on in the background, but it froze firefox for a good 30 seconds. (Core i7, 2 gigs of ram)

Edit: Tried it in Chrome with the network tab open. 267 requests, 2.43 mb transfered, loaded in 23 seconds. Something like 40 of those are javascript files. Then 8 font files.

For a news story! What madman wrote this?

Here's a useful tip - never browse the Web without NoScript (and optionally, AdBlock). It's insane how much useless stuff gets downloaded to our computers (some sites have scripts and files loading from 50+ other services, leading to a terribly slow experience)...

>Core i7, 2 gigs of ram

Completely off-topic and irrelevant but say what? 2GB coupled with the beast that is i7 makes the nerd in me cry a little.

This madman, and Pingdom (tools.pingdom.com) says the page loads in 2.5 seconds, clocking it in at about the median of pages. I load it it in 4-5 seconds even on my _Android_. What rig are you using that could conceivably make it 6 times slower than an Android pad?

Ping don doesn't render the page in a browser. Use webpagetest.org instead :)

Pingdom just measures /response time/, not browser-side parse/render time.

In both Firefox 10 and Konqueror 4.8 there is noticeable lag while scrolling and selecting text. The page also caused my laptop fan to turn on, which only happens when it's doing heavy lifting.

The page works really well in Links, though - loads far more quickly than in the other browsers I tried, no scrolling lag or unusual CPU use.

I was running this on my iPhone 4S. Outside over wireless; waited 30 seconds on a full 5 bars and just gave up.

Not meaning to be offensive at all, maybe it is because of my location (Japan)?

iPhone 4S here; def some cray JS on that page.

In Firebug, I see that just opening that page makes my browser do 281 requests for scripts and what not.

That's insane, users don't like to wait.

If you're referring to lag on initial page load, a couple things I noticed:

It uses ipv6; if your host is ipv6 enabled, there are probably tunnels involved and it'll be slower.

It tries to load dozens of json files from api.sharedcount.com. Try turning on pipelining if it's not already (still off by default in FF), and set max pipeline requests to something a lot more than the default of 4.

Welcome to Russia with love