Posts
DRM in cinemas
[…]
Unlike 35mm film prints that are tangible, come on spools, and run through a mechanical projector, DCPs are files that are ingested into the digital projector which is in many ways simply a very high-tech computer system. Because the physical file is ingested into a projector it can – if the cinema has enough space on its server – be kept there indefinitely and so, having created this situation themselves, the studios and distributors lock the files so that they can only be screened at the times scheduled, booked and paid for by the cinema. This means each DCP comes with what is called a KDM (Key Delivery Message). The KDM unlocks the content of the file and allows the cinema to play the film. It is time sensitive and often is only valid from around 10 minutes prior to the screening time and expiring as close to 5 minutes after the scheduled time. Aside from the obvious fact that this means screenings really do need to run according to scheduled time, it is also means the projectionist can’t test to see if the KDM works or that the quality of the film is right before show time. This isn’t always a problem. But when it is…
[…]
Munin & Bind9_rndc
2012/06/18-16:30:03 [28214] Error output from bind9_rndc: 2012/06/18-16:30:03 [28214] rndc: error: none:0: open: /etc/bind/rndc.key: permission denied 2012/06/18-16:30:03 [28214] rndc: could not load rndc configuration
However, via command line (and user root) it works:
/etc/munin/plugins # ./bind9_rndc query_recursion.value 0 query_success.value 80 query_nxrrset.value 17 query_requests.value 104 query_failure.value 0 query_duplicates.value 0 query_nonauth_answer.value 0 query_nxdomain.value 4 query_auth_answer.value 101 query_responses.value 104
Solution:
add this to /etc/munin/plugin-conf.d/munin-node:
[bind_rndc] user bind
and be sure the key has the right ownership:
Use Google.com instead of .be in Chrome
Why?
- Google.be lags on new features
- no +1 in .be
- no social integration
- no instant search
- probably a million other experiments that run on .com but not on .be
- The black-bar is entirely different on .be, don't know why
- Better G+ integration, not that I would ever use it
- .be lagged on https as well, and I'm a https fan.
In Chrome: surf to settings > Manage search engines.
Then either delete the default one:
The Silencing of Maya
[…]
The fact that my daughter’s ability to speak is becoming a casualty of a patent battle between two businesses is beyond my comprehension. This is a patent issue, a monetary issue, a legal issue, a business issue. This should be handled in a business vs. business way, within the court system. PRC’s decision to fight for the removal of this app from the iTunes store isn’t just an aggressive move against Speak for Yourself, it’s an attack on my child, the other children using this app, and the children who are ready to begin using this app but now cannot.[...]
I know someone whose 2-factor phone authentication was hacked…
[…]
Attacker finally says to friend “I know all your details, I know all about you; if you let me get away with a little bit of money, I will leave you alone.” And then a negotiation on how much is a little bit proceeds. Friend says “I’ll think about it” and hangs up.[...]

