33rd Chaos Communication Congress Livestreams(streaming.media.ccc.de) |
33rd Chaos Communication Congress Livestreams(streaming.media.ccc.de) |
* Schedule: https://fahrplan.events.ccc.de/congress/2016/Fahrplan/
* Media archive: https://media.ccc.de/
Edit: formatting
The error here is assuming that for all technologists "[handing] STASI their wet dream" and "trying to improve the world" are mutually exclusive. I am beginning to think they knew[/know] exactly what they were[/are] doing.
Any idea what it is actually?
[1]: http://grafana.org/
Can you share details here?
Security Nightmares seems to be still going. That's always a good talk.
Do you have a reference for this or personal knowledge?
https://fahrplan.events.ccc.de/congress/2016/Fahrplan/events...
Edit: They still let Rubin talk, so probably no quality control.
So he gave a talk on exploits he found but you call the talk "outright and clear lies", because you disagree with his conclusion that perl is broken?
He has been thanked by CCC orga directly for his contributions as well, thus making it clear that they support such shenanigans.
As far as i am concerned, every talk at CCC is highly suspect, since they either don't give a damn as to whether it is correct, or they actively support talks being given in bad faith to an unsuspecting audience.
info-beamer hosted always stores those files using content based addressing. So every file that enters the system gets hashed and is then addressed by that hash both on the website itself as well as on the devices. On the website this might look like this: https://cdn.infobeamer.com/dynimg/blob/image-c40ba24410fb9ca..., on the device they end up on /space/cache/<hash>. This is great for all kind of reasons: Cache invalidation and offline verification. For the website, all files can be cached indefinitely as the url changes once the content changes. On the device each file required for a visualization must only be downloaded once, as it's trivial to see if the same file was already downloaded earlier by just comparing filenames. So fonts that might be shared by visualizations are only downloaded once. Also the device can trivially verify that all files are still correct by hashing all cached files and comparing the result with the filename. If it matches, the file is correct. If it doesn't, something is wrong and a new sync is started to repair the problem.
Works pretty well. Does that help?
No party should get the chance to defend their position.
That said, there are times it reeks of "aimed for the moon, hit London" style thinking...
We have had a very vocal feedback loop of raising issues ("stupidity", "misunderstandings", "neglect") with OP conference as one type of such feedback.
Nothing has been corrected. Do you happen to know of another aphorism that covers the "willful stupidity", "willful neglect" etc. and what it all means (as I certainly don't desire hitting London.)
Obviously those with their hands on the production pipeline of tech disagree with the feedback. Is that really a controversial observation? Really?
I would be understanding if the CCC orga put him in the entertainment track, but they did not do that for two years in a row despite having received feedback.
He was intentionally spreading misinformation and the CCC orga supported him in that. These are simple facts.
At first, I thought he was going for a darker Brooker-ish humor, but in the end, the lack of research showed. I got the impression that he tried to shoehorn some corner-case examples into the general "Perl is a security nightmare" narrative.
It could have been someone else, but it sure sounds like him. It's a bad thing to do in a talk either way.
Edit 1: I've found a rather angry response[1] to the talk I was thinking of (Perl Jam 2). This is just for reference, I don't necessarily share the blog post's opinions.
Edit 2: Here's the Bugzilla[2] "bug".
[1] - http://blogs.perl.org/users/joel_berger/2015/12/response-to-...
His character and presenting seemed really strange to me. I was honestly totally confused by his presentation and couldn't make out if this was supposed to be funny or if he is serious.
And if it was supposed to be funny, I didn't find it funny at all.
All in all, I was really irritated by his talk and avoided all his talks ever since.
reading your comments, it seems that was the right choice
Maybe this year he'll talk about Perl 6 since 5.x is all old hat. ;)
You're not talking about a small typo, are you?
Can you point to the wrong examples/slides?
print $hash; # he accompanied this by a dump of the hash, when in reality it would print the reference id
print ($a, $b, $c); # same thing as above, pretends it does a dump, when the reality is wildly different
$arg1, $arg2 = @_; # assigns the length of @_ to $arg2, instead of unpacking args. only the newest of newbies would get this wrong
if(ref $arg1 eq 'HASH') print $arg1{'key'}; # perl does not have block-less pre-fixed ifs
else print $arg1; # same with this, entirely nonsense
Thanks for pointing this stuff out!