Posts by diodesign 3261 publicly visible posts • joined 21 Sep 2011
We're not in Shoreditch. We're using WeWork in Sydney, San Francisco and London (Gray's Inn Road, Camden).
In each location, we have our own private walled-off offices with our own desks, phones, Ethernet, etc, adjoining a shared space that has stuff like coffee, tea, biscuits/cookies, beer, cider, wine, kitchen, sofas, etc.
Well, except in California. They took away our alcohol :(
C.
"Wait, so you guys actually earn less on non-IT stories?"
The Bootnotes are a bit of fun. They're not the focus of our ad team. They're not even a traffic driver - stuff like cloud services going wrong, scandals, security cockups, operating system bugs, and so on, bring in the millions of netizens.
"And if you get just a bit too raunchy, those big advertisers will shy away"
That's not how it works. We sell ad space next to IT stories to IT vendors and providers. These companies want to reach technology workers, and show off their wares and solutions to folks in the industry, so that's why they direct their advertising there. Sometimes, advertisers will run their ads across the whole site. It's really up to them.
The Bootnotes are a side channel of amusement. Advertisers know these off-topic stories are part of the site's charm and heritage. If you're flogging an SDN switch, you probably want that to appear next to networking articles for maximum relevant eyeballs. OTOH you might want to run your ad sitewide. Whatever the advertiser and our ad team strike a deal on; us journalists aren't thinking about it.
C.
"Allegedly titillating articles like this one draw in a much larger crowd of eyeballs, enhancing ad revenues greatly"
This is a common misconception. Our main advertising is aimed at people coming to read the enterprise IT tech stuff. Ads that run alongside Bootnotes are mainstream and thus low CPM. We do Bootnotes stories to offer some light amusement, and keep to our tabloid roots.
C.
"Just what has this News got to do with Technology or Science?"
Nothing, which is why it's in Bootnotes. Bootnotes are off-topic fun for writers who need a break from writing about computers, software, bugs, companies, and other tech stuff. There is more to life than IT, and we're happy to provide some light relief for readers who don't want to stare at specifications.
Amusingly, I think you're the same Stuart who ran the Acorn Cybervillage way back in the day, when I ran Acorn news site Drobe, and we clashed even back then.
C.
"Isn't this mostly what you'd expect?"
Yes, but the point is: don't let old stereotypes interfere with your future code's decisions.
Also, it's an interesting way to study how stereotypes have changed over time.
"I'd be more interested in if anything has actually changed over the years."
Oh Jesus. That's like, half the story explaining it has. Does anyone read the articles?
C.
"huh odd how you didn't mention female wearing headscarf. almost as if you were afraid of providing description."
We've been providing updates throughout the afternoon as soon as we were able to confirm them, rather than spread rumor and gossip. We've included details of the suspected shooter.
"also. no fatalities as of this time. odd how that wasn't in article either."
One fatality: the gunwoman. And other injuries were reported accurately.
C.
LOHAN was overseen by long-term El Reg staffer Lester Haines.
As far as I understand/can recall: the device used a rocket motor that couldn't be legally launched in Europe, so it had to go to the United States for firing. It required a permit from the US aviation watchdog, the FAA, however officials couldn't decide how to classify it - whether it was a drone or a rocket.
They were busy rewriting the rules for drones at the time, and seemed hesitant to make a decision before the new regulations were approved, which had all sorts of politics attached to it. So LOHAN was somewhat lost in federal government's bureaucracy.
In 2016, Lester died, dealing us all a blow in more ways than one. The project has been in stasis since, although not forgotten. We've got our hands on the kit again. There may be movement soon.
C.
I absolutely hate this. Absolutely hate it. People are freaking out about Drupal 6, when the security team officially supports 7 and 8. I'm seeing all sorts of links to weird pages claiming they have patches for D6. I absolutely hate the idea of sending people to unofficial security fixes. The damage possible is obvious.
I think I've got the patch link right now. Should be this one https://www.drupal.org/node/2955130
Use entirely at your own risk.
C.
Generally not a great idea to state without caveats that a company has stolen IP from another company when they settled out of court.
99.99% they are not going to sue over an article comment, but it's always the ones you least suspect that end up triggering a legal headache.
C.
The point we were trying to make is that although Vettel was technically in the lead, he had yet to pit so wasn't really 1st. Due to the timing cockup for Hamilton, Vettel was able to unexpectedly secure that lead.
I've tweaked the piece to make it clearer.
Don't forget to email corrections@theregister.com if you spot anything wrong - those go to the top of our todo list, whereas we don't have time to check every comment.
C.
The point we were trying to make is that although Vettel was ahead of Hamilton, the Ferrari driver had yet to pit so wasn't really 1st. However, due to the timing cockup, Vettel was able to maintain pole position anyway.
I've tweaked the article to make it clearer.
Don't forget to email corrections@theregister.com if you spot anything you think is wrong. We see those instantly, whereas we don't have time to read through every comment - there are thousands a month.
C.
From the linked-to statement:
"Equifax was able to identify approximately 2.4 million U.S. consumers whose names and partial driver's license information were stolen, but who were not in the previously identified affected population discussed in the company's prior disclosures about the incident."
HTH
C.
"I feel like this article is not quite up to the Reg's usual bar of quality, what with the copious spelling and grammatical errors and misinformation."
Argh, ok, we'll go back over it. It was a Friday afternoon piece - but that's no excuse.
C.
Just like software written by professionals has bugs, articles written and edited by professionals have errors from time to time. It's fixed.
As for the Intel U/M thing. It's a Kaby Lake R Intel Core M part, but has a U in the part name. Because Intel.
From the official spec sheet, the 8550U is a Kaby Lake R part as opposed to a Kaby Lake U or a Skylake U.
Chipzilla's naming of stuff drives me bonkers.
C.
"The majority of the Russian ad spend happened AFTER the election"
Yeah, something like 56% after, 44% before.
Fact-Checking a Facebook Executive’s Comments on Russian Interference
A Reg reader falling for a SV exec's spin? Oh my days.
C.
All right, GrumpyReaper. I think you're being overly pedantic. Half the article stresses that home hardware can't handle the high-speeds, and that 1Gbps is more than enough let alone 10Gbps.
We assume all Reg readers are smart enough to understand that YMMV when discussing theoretical maximum data transfer speeds. Since you're being so pedantic, consider this: we didn't say anything about _writing_ the data to disk, merely fetching it. So yes, you can download a 25GB game in a few seconds over a 10Gbps line - writing it to storage is another thing entirely, which Reg readers know all too well.
I've tweaked the piece to make it crystal clear.
C.
I dunno man, I spent 80 bucks on an Apple wireless mouse for my work MacBook Pro, and I sure feel like I've been taxed like an idiot. Same goes for the RAM and other accessories I've bought for my home Mac gear over the many many many many
many many many many many
many
many many many many many many many many years.
C.
(Yes, El Reg hacks use Macs. That's part of the joke. We also have a new rule that you have to split your time between macOS / Linux and Windows, so we get the same daily experience of crap technology our readers face.)
"So the fact that it now happens to go a bit further is no problem, and not an error"
Who said it was a problem? We're just pointing out that it's overshot. Musk tweeted the final burn was going to send the thing "to Mars". It was heading to Mars. It's going to miss Mars by a much greater distance than expected.
Christ, it's a flying PR st- car. A flying car in space. It's funny as fuck.
Jeez, tough crowd! ;-)
C.
At the time of writing, it was suspected the engines ran out of fuel. We weren't invited to the press conference. Can't think why. Anyway, it ran out of ignitor, so... close enough, ish. We've tweaked the article and another piece is coming.
C.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
