Re: Missing Obit for Ursula?
Ah it's in the works.
C.
3495 publicly visible posts • joined 21 Sep 2011
>It DOES NOT not prevent your ISP from tracking sites or pages you visit.
It does prevent ISPs from tracking pages. All the ISP sees is an encrypted connection to, say, a Wikipedia server. It has no idea which pages I'm reading.
And I'm not so sure about your other claims, either.
C.
Big publications – from the NYT with its huge army of copy editors to the Grauniad with a sizable editing team - still let through errors. We have 3 region editors (North America, Europe, APAC), 1 news editor (UK) and 1 sub-editor (UK).
It's frankly fucking amazing there aren't more errors slipping through on El Reg given the resources available. The current rate is pretty low. It's hard to find good editors who can do sperlinng, snarky headlines, and are experts in tech and science.
C.
Due to a technical cockup, an old draft of the piece went live instead of the final edit. We keep a history of all article revisions, and an early revision overwrote the latest one.
I just restored the final edit. The piece was edited hours ahead of publication, and set to go live at 8am PT / 4pm UTC. We don't publish stuff straight to the web - it gets edited by at least one editor.
Basically, someone with a browser tab open with an old version of the story clicked on 'save and close', rather than 'close', in our web publishing system, and overwrote the clean version. Oops. But it's fixed.
Don't forget to email corrections@theregister.com if you spot anything wrong.
C.
"Oracle believes that certain versions of Oracle Solaris on SPARCv9 are affected by the Spectre vulnerabilities"
and
"Oracle is working on producing the patches for all affected versions that are under Premier Support or Extended Support."
Pretty clear to us. SPARC v9, running Solaris, is vulnerable to Spectre.
C.
"QUIC is not been deployed yet because it is still not a standard !! IETF is working on it and has recently pushed back the dates (to end of 2018)"
Yeah, so as we said, only Google seems excited by it. Everyone else seems to be taking their sweet time - of course, they're allowed to do whatever they want. But the point is, only Google seems excited by it, mostly.
C.
Eh, I dunno. We called it The Fappening in the past, and it just seemed the name had morphed to Celebgate.
And I'm all about a writing style that's like your mate at the local boozer. Just not so sure about playing into the hands of a bunch of 4chan degenerates jerking off over people's stolen private images, so to speak.
C.
Mate, none of what you said above is cool. If you're delivering stuff to someone, serving them food, any kind of day-to-day thing, taking their phone number and texting them weird flirty stuff is awful. The number was provided for business purposes, not to set up a date.
It's one thing to ask a person for their number in a social setting. It's another to delve into a customer record and pull out a contact detail and pester them.
Now imagine this happening every week - it could be on twitter, uber, just eat, work email. It gets old really quick and it's just creepy and sad. If you want to ask someone out, do it properly.
C.
"The racial makeup of Cupertino"
Cupertino is a small city in California that happens to have Apple HQ next to it. People who work at Apple, by and large, don't live in Cupertino. They live all over the Bay Area and the world.
No idea what point you're trying to make, anonymous coward.
C.
We asked Intel what was going on, twice, and had no response - not even a no comment, or an off-the-record explanation. We were certain with what we had - given the LKML discussions and information from other sources - so, why not warn the world that big changes are coming?
We offered no exploit code. Just a heads up that important alterations were being made to crucial bits of software. It's not our job to do companies' PR. We can't read minds.
And these changes were being done in the open, so any bad people paying attention could have known what we knew or more, and started exploiting it.
A lot of vendors hold us at arm's length, hoping we'll go away. We regularly get the silent treatment from various - but not all - companies. We're not going to sit on stories just because we get a no comment/no reply. Turned out this one was quite a big one. We had no idea it would be this big.
C.
Gaming is pretty much unaffected - it doesn't involve the kernel, you're talking direct to the GPU. Most desktop apps are not IO intensive so you won't see a big hit. It's not great news for stuff that slams the disk and network, or works in real time - however, as we said, if you have PCID supported, the hit is minimized.
C.
"But if even the Reg simply won't be bothered to call out this brazen misuse of the term"
Holy balls, we just published hundreds of words calling out DM's approach - and we're still the bad guys. We use "AI" as shorthand for various related technologies just as "the cloud" covers IaaS, PasS, SaaS, etc. The exact tech is defined, AI is used to avoid repeating the same phrase over and over. We're not a dry technical manual.
You may have noticed we bounce between terms – IBM, Big Blue, Intel, Chipzilla, Microsoft, Redmond, crypto-currency, digi-dosh, etc – because it's more interesting to read, easier on the eye and mind, and still conveys overall the same message.
Trust me, trust us, after decades of writing and publishing, combined as a team, an article with the same terms repeated over and over and over and over stops being engaging – and becomes bland documentation.
C.
it was written by one of our guys. Here's how it works: HPE buys ads, it wants its ads to appear around an article that isn't laying into HPE - and we lay into HPE a lot - so here's an article about HPE-related stuff with HPE ads around it.
It all supports the journalism we do every day.
C.
Headline was:
"Google has but one burning desire: Let them ban access to Fire... Oh move over rover, and let Mountain View take over"
but... some killjoy (cough, me) changed it. Mainly because it's Google pulling access, rather than Amazon banning, and I didn't want the headache of explaining the lyric to either side's PR people.
C.
You can specify whatever name you like. The convention is author/project:tag. if you want to publish your dockerfiles, the author field should be unique AIUI.
Eg, on my personal machine, I have the following Docker images:
diodesign/debian-x11:latest
rust:1.20.0
diodesign/debian-verilog:latest
diodesign/debian-gcc:testing
debian:testing
which are respectively:
My custom Debian-based X11 desktop
Standard Rust 1.20 build environment
My custom Debian-based Verilog dev environment
My custom Debian-based C/C++ dev environment
Standard Debian Testing install
C.
"We don't care about solving Sudokus in and of itself. I tried to make this clear in the paper, but it wasn't really picked up in this story."
Thanks for commenting! But ahem, ahem ;-) It's all over the story that this is more than cracking Sudoku. We wrote:
> it’s an interesting problem for deep-learning software to tackle, as it's an exercise for neural networks to practice complex reasoning.
[...]
> Although the recurrent RN is pretty good at cracking Sudoku puzzles, it’s designed to be a general purpose module that can be added to different types neural network models so that it can perform many-step relational reasoning.
>
> It’s still early stages and the applications have yet to be explored. It’s an important area for machines since logical reasoning is key to making them smarter in the future.
Congrats on the cool research. We made it clear this is more than breaking Sudoku. If you're put off by the sarcastic title, well, them's the breaks around here.
C.