Yver

I might be an idiot but... how about automatic doors? (that you don't have to touch)

You want some WiFi app thingie? Ok, link the automatic doors to the nearest gel dispenser and when the ratio of door opening/dispenser use gets too low, the door only opens after the dispenser has been used.

> The fact that this whole charade is over one word "standard"

There are only two words and you picked the wrong one. The issue is about the word (and apparently, trademark) "Markdown". They can call it "Standard Rockdown" if they want.

> I'm sure that Gruber could have politely sent

Come on. Gruber said he didn't want people to use the name and instead they should create their own flavor with their own name.

They floated the name "RockDown" back then. Whatever happened to that?

I think the unregulated market is ripe for some disruption in the form of regulations.

> when it's disclosed that .govs run nmap it's time to patch your TCP stacks?

They don't just nmap the internet, they systematically compromise vulnerable targets as per the article and the slides. And unlike common criminals, there's no hope of them being stopped by any law enforcement agency.

If they're really going after every non 5-Eyes machine they can compromise, people living outside of the 5-Eyes need to protect themselves.

I'll quote the slides: 1. (R)econaissance 2. (I)nfection 3. (C)ommand And Control 4. (E)xfiltration

They're litterally running nmap for the reconnaissance part but I believe the "heinous" qualifier apply to the rest of the plan, which according to figure 18 consists in acquiring "as many new ORBs as possible in as many non 5-Eyes countries as possible". Unless I'm reading it wrong, they describe how they try to pwn as many machines as possible outside of Australia, Canada, New Zealand, the United Kingdom and the United States.

It would have taken you 5 second to verify that no, it's not supposed to be read that way.

> It’s wide angle lens provides 124° of coverage so you can get the big shot.

I expected it to be a new NoSQL, "eventually consistent" database server.

> By that logic, public domain is "ambiguous".

The notion of public domain can vary from country to country. The first time I wanted to release something inconsequential on Google Code I was surprised that it didn't let me choose "Public domain" and forced me to choose a license. Here's their FAQ about it: http://code.google.com/p/support/wiki/FAQ#Can_I_host_code_th...?

> "Why should you lock your door if you don't have anything expensive?"

Locks come standard on every door, they don't expire after a given time and every child knows how to use them. See how your comparison to acquiring, setting up and maintainning an SSL certificate is nonsensical?

> And to think HTTPS could have avoided that.

If the NSA tags people who look for info on TOR as extremists, an hypothetical state might tag people who use HTTPS. And to think that HTTP could have avoided that! I mean, if every argument is an hypothetical, anything is possible.

There's too much confusion, you're right. What Netflix need is some hard numbers. I suggest they take very detailed statistics at the client level and constantly report them back to their servers, in real time. With all that data available, it will surely ~~artificially balance the network usage and solve the legal aspect~~ allow both parties to make informed decisions.

Are you going to elaborate on that?

I think you're misremembering IE's version numbers. ExtJS started up as a YUI extension called YUI-ext circa 2006. IE3-4 were long dead by then. You might be thinking of IE7-6.

http://www.w3counter.com/globalstats.php?date=2007-05-30

I expected something factual.

They could have added a dedication in the acknowledgements rather than change the content of a binding specs for personal reasons.

Oh, that's even weirder. I thought the page changed after you posted the link, not the other way around.

The page currently says "All VODs will be removed after June 8, 2014. We recommend downloading your recorded videos before the date."

Spoiler alert: it doesn't taste like much.

As for the rest, it's the usual Soylent article being rehashed. If you're looking for a bland, cheap alternative to journalism, this is for you.

Most disheartening is the way Zeev Suraski pleaded for votes against the size_t/int64 patch in a mail[1] titled "A call for help (urgent)" because, I quote, it "negates months of hard work". That was only a few days after Zend's secret project had been uncovered.

The size_t/int64 refactor has been going through several iterations and RFCs since 2013.

[1]: http://news.php.net/php.internals/74268

That's what I thought so I did a second take. This is the relevant excerpt:

> This tree of strings is then converted to YAML tokens using the class Psych::ScalarScanner that internally uses regular expressions to identify YAML types. The regular expression used to identity time objects changed in the new version of Psych, which meant our nanosecond precision time was now correctly converted to a YAML Time type rather than being left as a string.

Apparently, the "hurt" mentionned in the title refers to a bug being fixed.

Any example that you could, you know, share?

The part I still don't get because I haven't seen it discussed so far is that their original patch mentionned they had been using a variant of the patch "for a decade" but I never got why they didn't seek to get it merged upstream a decade ago. Or why they released "a variant" of their patch instead of the real thing to begin with.

They think that because it's not part of their job, so they should be paid extra for it. I don't think that OP's $8/hour job's reponsibilities include increasing productivity on a company-wide scale. Management is asking the employees to do something that's not part of their job and for which they are not paid.

So I assume this is an April Fools? Not sure, and I hate expanding efforts on filtering April Fools.

Tried the game, it's nice. Got 1 point on my first try, somehow managed 15 points on the second. I don't think a baby would get any points, so I'll go with April Fools.

What they have in common: they deal in Bitcoins, they're not banks, they have a "o" and an "x" in their name.

Now if you're trying to bash PHP (or Ubuntu?) for banking software that does not take an exclusive lock on rows it reads then modifies and a daemon that does not check balances on withdrawal, try again.

It's bad that the Bell support employee was unwilling or unable to recognize it had to be escalated to a supervisor, but that's not exactly what I'd call a "disclosure" (and obviously not a "responsible" one.)

I don't expect the average help desk employee to know what SQL is, or what "owned" or "sploit" means. Half of their customer interactions consist in asking whether the modem is plugged into a wall socket and there's electricity in the rest of the house.

It's not just about bandwidth, it's also about parsing and executing ~82KB of JavaScript before doing anything on the page.

This would be funny if it wasn't so infuriating. I tried to listen to it but I cringe too easily so I'm waiting for a transcript. Based on the first few sentences of the call, here's how I expect the rest of the speech to go:

"...you no longer have a role in the company. And by role I meant job. You no longer have a job. Unless you had another job, in which case you still have at least one. Point is, you're fired. From this company. It's Patch calling by the way."

I'm always skeptical of claims that "X will never work" that are not backed by solid research or a mathematical proof.

The current 3D may be nauseating to a number of people, but I do note that travelling by car is nauseating to some too, and I've seen older people get similar effects when reading a computer screen that is scrolling too fast.

The attacker obfuscated "base64_decode" part but not "eval". It's not the first time I see base64_decode() being more the focus of attention than eval, I don't know where it originates from.

Also, if cron infected the PHP files I wonder what infected the crontab. :\