Re: Brilliant line.
That's probably the only way to improve this episode. "Say 'Hi' to John Postel when you see him."
371 publicly visible posts • joined 7 Oct 2014
To be fair, the biggest time waster is probably surfing the internet, and Google has had that down for a few years now. I bet they have data showing that including solitaire bloatware actually increases worker productivity.
In other news Google moves to Redmond and releases Search 95.
Can you also imagine the usual suspects not getting the contract for that very reason?
Of course it may not be something that happens all at once. It may be brick by brick as a functional collection of open source libraries are written for smaller projects, which can used as a foundation for the gimungous projects further down the line.
Yeah, that "device plugged into the mains" thing is weird isn't it?
What about when I'm low on battery and want to charge while I watch?
And what about the WiFi router? It's a device I'm using to stream iPlayer and presumably it's plugged into the mains too, so does that count?
There is so much stuff with this that sounds half baked.
I am still unclear on what the benefit of this is.
If this is about opportunistically using WiFi spectrum in areas where cellular spectrum is congested surely it fails because most of those areas will already be congested with WiFi points (population bringing cellular and WiFi devices with them where they go).
Also what would this mean for something like a LTE-U WiFi access point? It could contend itself out of existence.
Marginal gain at the cost of a big increase in complication and frustration.
This seems like a bad idea all round.
Now when they issue a patch to fix this and it doesn't install correctly on machines that only have Firefox so they issue another patch to cover that scenario users could end up with four installations of Flash (because the patch for Firefox-only obviously won't apply smoothly to IE-only scenarios). Which means that they will have to issue another patch to fix it...
That will escalate quickly.
And yet it is strangely reassuring to know that while the number of bugs in Flash is being chipped away at, the total number of Flash-related security holes on machines with it installed is only increasing, exponentially. All is as it should be.
No it's much worse than that. If he did it accidentally then he got the wrong wrong number, which, if two wrongs don't make a right, means he meant to get the right wrong number but didn't, so he was wrong, but it was an accident so that's OK, as long as the person on the receiving end wasn't signed up to TPS, in which case the ISS, or ESA, whichever one's right, could be on the wrong end of a hefty fine. I think that's right.
Mind you, it's better than the mistiling event that Columbia suffered. Coat, ta.
From http://www.oxforddictionaries.com/definition/english/none
"It is sometimes held that none can only take a singular verb, never a plural verb: none of them is coming tonight rather than none of them are coming tonight. There is little justification, historical or grammatical, for this view. None is descended from Old English nān meaning ‘not one’ and has been used for around a thousand years with both a singular and a plural verb, depending on the context and the emphasis needed."
So it turns out that Millennials use it either way. And when I say Millennials I mean those from 1000AD, not 2000AD.
It's like lending records in a library. The books are all published and it's no secret what's in them, but your private use of them and what that reveals about your purpose in using them can still be of interest to someone. HTTPS obscures what you have been reading from your ISP and any other observers on the route to the site you are looking at.
It is often possible to work out which site you have been visiting from the server's IP address (although if it's a multihost site that will only resolve to a list of possibles), but the details of exactly which page on that server are hidden by HTTPS.
Yes indeed. Have NASA got no respect? Don't they know that those letters belong to an organisation with an unimpeachable track record in (nearly) space flight and playmonautical derring do? I should think they might apologise and have a word with the FAA by way of making things right again.
Super-Pressure Balloon, what a waste of three good letters anyway. Next they'll be claiming the rights to Nasaly Aspirated Snot-like Accelerant, or some such tissue fodder.
".... just not very good satire, sadly."
You should read Kieren's comment above. And then ponder why you don't think it's good satire. And then realise that at least one of the sharp ends of the piece is poking you.
I say that having gone through a similar thought process myself.
Tone is difficult to convey in typed text, and Kieren does a great job of exploiting that limitation here. The way the article's style conflicts with the content is devastating and invites the reader to reevaluate their own assumptions and ways of expressing things.
A lot of this information is already available in the headers, (eg SMTPA, DKIM signatures) but email clients don't display it in any easily accessible way (which is your point about the headers), and they are not available for all email systems.
As these new RFCs are developed it would be good to see the IETF keeping an eye on usable indicators or flags that can be quickly displayed in email clients (rather like Gmail does now with indicating an encrypted SMTP channel or otherwise in their web client).
It's not enough to be secure, you've got to show people that you are secure so that they will learn to value it better.
Thunderbird plugin as a proof of concept?
Nmap has been able to make highly educated estimates about platform, version and software stack for decades from simple network scans. The same logic has presumably also been applicable to network streams (except more accurately because there is far more data in a Facebook session than in a few pings) captured legitimately or nefariously. Surely the https info cannot be news?
If they could work out the information about endpoints when examining only encrypted VPN traffic I would be more impressed.
phuzz wrote: "But yesterday was 14/3/16 (or 2016/03/14 if you want to use the more logical Japanese system), what's that got to do with Pi?"
This is the only redeeming feature of the standard American date format that I can see. It is otherwise irredeemably illogical. It also falls foul of equal opportunities legislation, discriminating as it does against other important irrational numbers like e (2.71828182846ish, try to get that regularly into any standard date format!).
Mind you, while I like eating pies on pi day I'm not sure I would want to indulge in the designated fare on an e day.
Nope. DARPA are the red team in this exercise.
War 101: "Know your enemy."
Absolute genius. Douglas Adams couldn't have done it better. "It turned out that the ultimate weapon of global destruction was not the nuclear bomb but the humble toaster. The world ended shortly after 7.30am on a Thursday as the world's toasters burned their owners to a crunchy crisp."
Maybe not, but that doesn't mean he was wrong to say it.
The very act of warning that a bad thing can happen is sometimes sufficient to stop it happening. Someone in a position of influence speaking out about a danger can change policies and strategies across an industry so that the problems they are warned about never come to pass.
When that happens then the bad stuff doesn't. Does that make someone like Gabe Newell wrong? Only in a very limited sense. In fact they have been right, and very effective.
We should applaud those who speak out in this way. If we end up with another PC monopoly then pretty much everyone is worse off.
Most mobile apps report to random IP addresses in AWS or Apple or Google's cloud, and who knows what happens to the data after that? The fact that this watch reports to a Chinese address maybe just indicates that the opsec of this particular company is particularly poor. You don't have to be Chinese to be a dodgy cracker.
I remember installing one well reviewed and popular mail/productivity app on Android and discovering that it sent my email password to a cloud server (AWS in this case) and logged into my account from there. At no point in the "read more" blurb, installation instructions or setup was I told this would be happening. Uninstall, change password, block specific IP address, one star review.