The analog loophole, using a lego mindstorm and Mac to bypass the DRM on a Kindle

I love the idea of using the analog loophole to bypass copyprotection / DRM. For example filming in the movie in the cinema (usually very bad quality) or...

From allthingsd:

Using Lego’s Mindstorms — a basic robotics kit popular with hobbyists — plus a Kindle and a Mac, he has assembled a way to photograph what’s on the screen, and then submit it to a cloud-based text-recognition service.

To bad I dont have a kindle. Nor really the need to copy a work like this. But still, once the WorlWide cyber police controls us all; we can stull use the analog loophole to get back at them :-)

DIY kindle scanner from peter purgathofer on Vimeo.

Bert Boerland is a volunteer for the DrupalCon

I'm a volunteer at DrupalCon Prague

And I have been doing so since lead organising DrupalCon Amsterdam, co-lead DrupalCon Barcelona and helping out as volunteer in Copenhagen, London, Munich, Syndey, Portland and now Prague as co-global chair for the business sessions. And I am not done yet :-)

Alfred Eisenstaedt, Instagram hate

Alfred Eisenstaedt. One of the best known photographers of the world from the last century. Best know for hist freedom "V J Daykiss photo on timesquare.

And known for his great photos of the beautiful Monroe:
alfred eisenstaedt photos of  monroe

He was lucky enough to meet Einstein as well and made the most well known photo of the genius.
Alfred Eisenstaedt phots of Einstein

He made photos of ms Loren in lingerie, Churchill making the "V"ictory sign and many many great photos. President Kennedy, Dali are just a few of the well know persons. But his work on anonymous people and everyday objects is even better. Be sure to scroll on this page containing most of his work.

Many photos from Alfred Eisenstaedt

By far his best work however is his two photos of Goebbels, the German (pre) WorldWar 2 propaganda minister. Goebbels was known to play the media, be smiling in the papers and always laugh when in public. He knew how to play the camera in an age where most politicians didnt pay attention to the media, most americans didnt even knew their president during that period was in a wheelchair.

Alfred Eisenstaedt was born in Poland within a Jewish family and unfortunately witnessed the rise of the Nazi Party led by Adolf Hitler. He tried to gain ground profesionalment in Berlin, but inevitably had to emigrate to the United States because of his Jewish background.

Alfred Eisenstaedt was perhaps the only man who could portray the face of evil, hypocrisy and hatred that can hold a human. There are two photos, without much time lapse between the one and the other.

It happened in Geneva. He had the opportunity to portray Joseph Goebbels, Hitler's Minister of Propaganda. In the first picture there was no major problem because the atmosphere was relaxed and Goebbels was showing off his smile.


For the next picture, the face of Joseph Goebbels changes radically, it decomposes. We had been warned that one of the accredited photographers (Alfred Eisenstaedt), was Jewish, places him, and gives him a demonic look.


In the 1985 book, Eisenstaedt on Eisenstaedt: A Self-Portrait, the then-87-year-old photographer discussed how the Goebbels picture came about:

In 1933, I traveled to Lausanne and Geneva for the fifteenth session of the League of Nations. There, sitting in the hotel garden, was Dr. Joseph Goebbels, Hitler’s minister of propaganda. He smiles, but not at me. He was looking at someone to my left…. Suddenly he spotted me and I snapped him. His expression changed. Here are the eyes of hate. Was I an enemy? Behind him is his private secretary, Walter Naumann, with the goatee, and Hitler’s interpreter, Dr. Paul Schmidt…. I have been asked how I felt photographing these men. Naturally, not so good, but when I have a camera in my hand I know no fear.

Read more at An instagram filter revelaing the true hate.

Once again: the phoney before


and the evil after:

Never before has anyone shot a fake smile and a horor face within seconds that held so much of things to come. Instagram hate.

Minecraft or Drupal?

SPDY and webperformance

Robert M. White

  1. Performance matter for all websites
  2. Performance is not just (80%) frontend
  3. SPDY kills 80% of your frontend problems

In the Drupal and broader web community, there is a lot of attention towards the performance of websites.

While "performance" is a very complex topic on its' own, let us in this posting define it as the speed of the website and the process to optimize the speed of the website (or better broader, the experience of the speed by the user as performance.

This attention towards speed is for two good reasons. On one hand we have the site that is getting bigger and hence slower. The databases get bigger with more content and the the codebase of the website is added with new modules and features. While on the other hand, more money is being made with websites for business even if you are not selling goods or run ads.

Given that most sites run on the same hardware for years, this results in slower websites, leading to a lower pagerank, less traffic, less pages per visit, lower conversion rates. And in the end, if you a have a business case for your website, lower profits. Bottemline: If you make money online, you are losing this due to a slow website.
When it comes to speed there are many parameters to take in to account, it is not "just" the average pageloading time. First of all the average is a rather useless metric without taking the standard deviation into account. But apart from that, it comes down to what a "page" is.

A page can be just the HTML file (can be done in 50ms)
A page can be the complete webpage with all the elements (for many sites around the 10seconds)
A page can be the complete webpage with all elements including third party content. Hint: did you know that for displaying the Facebook Like button, more Javascript is downloaded then the entire jQuery/backbone/bootstrap app of this website, non cacheable!
And a page can be anything "above the fold"

Moon Retro future
And then there are more interesting metrics then these, the time to first byte from a technologic point of view for example. But not just technical PoV. There is a website one visits every day that optimzes its' rendable HTML to fit within 1500 bytes.
So ranging from "First byte to glass" to "Round trip time", there are many elements to be taken into account when one measures the speed of a website. And that is the main point: webperformance is not just for the frontenders like many think, not just for the backenders like some of them hope, but for all the people who control elements elements in the chain involved in the speed. All the way down to the networking guys (m/f) in the basement (hint sysadmins: INITCWND has a huge performance impact!) Speed should be in your core of your team, not just in those who enable gzip compression, aggregate the Javascript or make the sprites.

Steve Souders (the webperformance guru) once stated in his golden rule that 80-90% of the end-user response time is spent on the frontend.

Speedy to the rescue?
This 80% might be matter of debate in the case of a logged in user in a CMS. But even if it is true. This 80% can be reduced by 80% with SPDY.
SPDY is an open protocol introduced by Google to overcome the problems with HTTP (up to 1.1 including pipeling, defined in 1999!) and the absence of HTTP/2.0. It speeds up HTTP by generating one connection between the client and the server for all the elements in the page served by the server. Orginally only build in chrome, many browsers now support this protocol that will be the base of HTTP/2.0. Think about it and read about it, a complete webpage with all the elements -regardless of minifying and sprites- served in one stream with only once the TCP handshake and one DNS request. Most of the rules of traditional webperf optimalisation (CSS aggregation, preloading, prefetching, offloading elements to different host, cookie free domains), all this wisedom is gone, even false, with one simple install. 80% of the 80% gone with SPDY, now one can focus on the hard part; the database, the codebase. :-)

The downside of SPDY is however that is is hard to troublshoot and not yet avaliable in all browsers. It is hard to troubleshoot since most implementations use SSL, the protocol is multiplexed and zipped by default and not made to be read by humans unlike HTTP/1.0. There are however some tools that make it possible to test SPDY but most if not all tools you use every day like ab, curl, wget will fail to use SPDY and fallback like defined in the protocol to HTTP/1.0

So can we test to see if SPDY is really faster and how much faster?
Yes, see Evaluating the Performance of SPDY-Enabled Web Servers (a Drupal site :-)
SPDY performance

So more users, less errors under load and a lower page load time. What is there not to like about SPDY?

That is why I would love to run with SPDY, see this issue on d.o/2046731. I really do hope that the infra team will find some time to test this and once accepted, install it on the production server.

Performance as a Service
One of the projects I have been active in later is ProjectPAAS, bonus point if you find the easteregg on the site :-) . ProjectPAAS is a startup that will test a Drupal site, measure on 100+ metrics, analyse the data and give the developer an opinionated report on what to change to get a better performance. If you like these images around the retro future theme, be sure to checkout the flickr page, like us on facebook, follow us on twitter but most of all, see the moodboard on pinterest

Pinterest itself is doing some good work when it comes to performance as well. Not just speed but also the perception of speed.

Pinterest lazyloading with color
Pinterest does lazyload images but also displays the prominent color as background in a cell before the image is loaded, giving the user a sense of what to come. For a background on this see webdistortion

Congratulations you just saved 0,4 seconds
If you are lazyloading images to give your user faster results, be sure to checkout this module we made; lazypaas, currently a sandbox project awaiting approval. It does extract the dominant (most used) color of an image and displays the box where the image will be placed with this color. And if you use it and did a code review, be sure to help it to get it to a real Drupal module.

From 80% to 100%
Lazyloading like this leads to better user experience. Because even when 80% of the end-user response time is spent on the frontend, 100% of the time is spend in the client, most ofthen the browser. The only place where performance should be measured and the only page where performance matters. Hence, all elements that deliver this speed should be optimized, including the webserver and the browser.

Now say this fast after me: SPDY FTW. :-)