Re: Works for me
FYI - the article is about iOS's face detection, and not Face ID. See the correction. We regret the error.
C.
3493 publicly visible posts • joined 21 Sep 2011
You've had 2 comments rejected this month, and before that way back in 2013. The rejected comments accused someone of fraud and another suggested someone committed homicide. So just take it easy and hold back on the wild accusations - cheers!
Also, we try to write for a big range of people; not every story is going to be your cup of tea. Readership is up ~20% year to date on the same period 2016, so we're obviously doing something right. And what we can't do is please all the people all the time.
But ta for reading. Hope you stick around.
C.
Hiya,
Well, from our end, we haven't stepped up rejections. It's biz as usual. So don't worry about some kind of puritanical crackdown.
You posted on an article where the comments went a bit nah so a mod stepped in to clean it up a bit. We all like cracking jokes, but maybe not about shooting your load in someone's mouth and making light of sexual assault reports. It's the sort of wisecrack that you say a party and it kills the group conversation dead. We've all been there, I think.
So anyway, don't take it personally. You can still comment. Please do comment! And thanks for posting. Just that one, out of your 290-odd other comments, was not great timing.
C.
Software has bugs, stories have typos. We try to catch them all but it isn't always possible. Some days we're pretty good at catching them pre-publication, some days we're not.
Just drop corrections@theregister.co.uk a line if you spot anything wrong. Takes just as long as a comment post.
C.
Mate, we're ahead quite a lot of other titles on news. In some cases - such as IBM canceling remote working - we were months ahead of other titles. It took the WSJ about half a year to notice and follow up our coverage.
We thought this amusing thing about Alexa would tickle Reg readers, and be something fun to talk about. And unlike other bootnote-worthy stuff this week - like the woman who allegedly unlocked her husband's phone on a plane while he was asleep next to her and discovered evidence of an affair - this one is actually provably true.
Lester, god rest his soul, would have been all over this, and even he would bootnote his own bootnotes with:
It happened a few days ago. What of it?
C.
Open the Terminal app (in Applications->Other) to get a command prompt. Use the ls command to list info about the files, eg type:
ls /tmp/Updater.app/
Or rather type 'ls ' and then cut'n'paste the file name. Hit enter, and you should see:
ls: /tmp/Updater.app/: No such file or directory
Which means the directory doesn't exist so you're OK. Repeat this for the other files listed. You can quit Terminal when you're done.
C.
If you apply your patches, you'll be OK. If you're using Windows or iOS, you're pretty much immune anyway. There isn't a tool to check as far as we're aware. If you're using a recent Linux or Android 6+ or macOS or openBSD or an IoT gadget that uses Linux, you're at risk.
But bear in mind no exploit code attacking the flaw is out there, someone has to be in range, and it's right now tricky to do. Grab the latest security updates for your devices so that you're protected in future.
C.
"It is true, however, that there hasn't been the kind of well-informed, detailed explanation of the vulnerability that The Register would normally do."
The flaw is fairly complex but well-explained in the paper, which is public. We've linked to it in previous coverage. You should read it if you're interested in nonces and key installation. If you're aware of WPA2's cryptography, it's an easy read.
Instead, we've focused on the impact - that's what matters most.
C.
Microsoft is giving up on smartphones, but loves the idea of ARM-powered laptops running Windows 10. Microsoft and Intel had a major falling out over PC processor prices, so Redmond turned to a CPU supplier dying to break out of mobile: Qualcomm.
So forget Microsoft in your pocket. Microsoft wants to be on your lap or desktop, with Windows 10, on Qualcomm ARM, or Intel or AMD x86.
C.
Great question, Steve. We cover outages when we can. Some outages are more important than others (ISPs and multi-tenant cloud services, especially) so we jump on those. Facebook going down for a few minutes, not so much. Sometimes we're all working on other stories, and by the time we drop everything, and start writing up the outage, the thing comes back online.
The Verge is about as techie as a bent paperclip. It's a marketing vehicle for Silicon Valley.
C.
I'll let you in on a little secret: we don't really care if the scansion doesn't quite match up - worrying about a syllable here or there, life's too short for that.
In this case, we couldn't fit the 'the' in because then the headline would not fit in its little space on the front page, break over many many lines and just look ugly. And I'd rather have a tidy looking headline than one that fits the 14 syllables perfectly.
Sorry, not sorry. But thanks for appreciating the headline. We couldn't write one anywhere else in the enterprise IT news world.
C.
"This a another faux-outrage created by non-Apple users, as usual."
Apple is being super confusing here.
"In iOS 11 and later, when you toggle the Wi-Fi or Bluetooth buttons in Control Center, your device will immediately disconnect from Wi-Fi and Bluetooth accessories. Both Wi-Fi and Bluetooth will continue to be available"
Will both continue to be available even though disconnected. Huh? Turns out you have to go to the *settings* page:
"To turn off Wi-Fi, go to Settings > Wi-Fi and turn off Wi-Fi.
To turn off Bluetooth, go to Settings > Bluetooth and turn off Bluetooth."
You can see why it's irritating people. Off should always be off, not nearly off until you find the other lever to pull.
C.
Hate to 'actually' you, but ACTUALLY: Our revenue this year is neatly following 2016's record high. As in, 2016 smashed El Reg's all-time ad sales records. The unsung heroes here are our sterling ad sales team, and us news scribes are in their debt.
So yes, we sometimes run vendor-sponsored articles - clearly labelled sponsored or promos - and they make us a decent amount of money. Take 'em as you like: they are written by freelance journos we vet for quality. And the pieces are super interesting. Don't skip over them just because they are biz-sponsored. It's all part of the El Reg mix.
However, a vast chunk of our cash comes from display ads against our top news articles - which are produced well away from any vendor interference.
We strive to provide highly technical and accurate IT news and features independently and ethically.
Ultimately, this all funds the snark, sarcasm, the exclusives, the analyses, the features of The Reg that you love and we'll continue to serve.
Hey Andrew - it's Chris from Drobe. Remember those RISC OS days? Ah yeah. Now I'm at El Reg. Lol!?
Anyway. Thanks for reminding ppl about the extended iOS settings to actually switch off radio comms. We linked to Apple's instructions, so no foul there.
"The continued race to the bottom in El Reg persists"
The fact that we're the most read in the enterprise IT space, and that we're making year-upon-year growth in ad revenue and profit, suggests you're full of shit, Andrew.
C.
This article isn't written for people who have avoided the bug. It's written for people hit by the bug who want to know WTF is going on. And check the link - Apple admits there is a problem.
Also, ppl saying their gear works - are you using the Outlook app? That app is crippled: check out the reviews for it. The UI is mashed beyond repair. That's not a great UX for ppl.
There's no sensationalism going on here. iOS 11 doesn't fully work with Microsoft's software - Apple says as much. If it works for you, great. Judging by the stats on this article, millions disagree that all is ok.
C.
"ranting about the SJWs is poor form"
Ah, come on. Our job is to summarize as best we can complex stuff. In between the usual in-fighting and politics that rage in some open-source projects, the thing for us that stuck out was the CoC side, and so that's the focus here. To us, it's the straw that broke the camel's back.
The ability, or inability, for Node.js to self-govern properly as a FOSS project is best left to another story, and something we can look into. In fact, it should be obvious that, after two splits now, that all is not well in the project.
It's our job as journalists to identify the information that is most interesting to readers. And in our view, a bitter argument over CoCs - which is a rather large policy issue these days in tech - is more significant than people flaming each other on mailing lists.
C.
"the EPO has got nothing to do with the UPC"
Apart from granting them – and, for years, spent a lot of time, money and effort promoting UPC, is a huge cheerleader and advocate of UPC, and stands to gain a lot from the UPC coming into force.
So yeah, nothing to do with UPC, lol.
C.
Couple of observations, my dear fellow:
1. Your comment pointed out a typo in the article. Our standard operating procedure when we see corrections in comments is to fix the typo and reject the comment - because the comment is unlikely to make any sense after the tweak is made. You should email corrections@theregister.co.uk so problems can be addressed ASAP. We don't have time to read every comment but we do like to correct all errors.
2. You need to, as we say in California, chill out.
C.