Posts by TeeCee 9435 publicly visible posts • joined 5 Oct 2007
Nobody anywhere seems to have ever implemented the right use for this sort of tech.
The ability to look up exactly where your bike currently is[1], courtesy of the electronics embedded in the frame and remotely detonate the 1/2 lb of C4 adjacent to same.
[1] In case the scrote who nicked it is currently using it in a place where there are innocent bystanders of course. Bonus points for finding it's in "Honest Dave's Dodgy Bikes" and claiming the jackpot.
If you have Cortana set to respond to "Hey Cortana", turn it off. That often does it.
Used to work just fine, but broken as of the 1511 update in Win 10. This is probably the most annoying thing about 10, the major updates have a nasty habit of breaking as much, if not more, than they fix.
As even the spanking new Snapdragon 820 ships with HW support for H.264 / H.265 only, according to the specs on the Qualcomm website, I think that one's pretty much over.
Anyone who wants to support mobile has a choice of 264/265, decoding in software, with the attendant overhead and really crappy battery life, or holding everything in all resolutions in both formats(!)
VP9 ain't going anywhere until the mainstream SoCs have been offering HW decode for it for at least a couple of years.
As I see it, he had to get into the S3 bucket he had access to to find that they had (in an act of mind-blowing stupidity) left the keys to the rest of their stuff in there.
You should report problems as you find them, not save 'em all up until you're sure you've reached the bottom of the rabbit hole. The reasons here should be mind-numbingly obvious.
As it's now "wrong" to find and report this, presumably the correct approach is to dump the lot on pastebin anonymously to illustrate how far the fuckup goes?
And if it hadn't been the FBI saying as much, you can imagine that most people would have continued to believe it.
Whereas now only the fuckwits who believe that every statement by a government agency is a lie believe it. IIRC they are usually referred to as "the blogosphere"........ hence the Washington Post's problem.
Fooled one of my colleagues at work. Down having a drag and he came down to impart the news that my PC was in serious trouble and throwing repeated BSODs:
"It's a screensaver. I can't believe you fell for it."
"No it's not, I wiggled the mouse to check that."
"Well it wouldn't be any bloody good if it didn't disable the mouse now, would it?"
She said that it had been a reasonable position for cops to take as the police's priority was to catch the criminals.
No, it's an entirely unreasonable position. Even the dumbest, pigshit-thick woodentop would know that their chances of actually getting their paws on the culprits is somewhere around sod-all.
Rather less if, as is usual, the scrotes are happily ensconced in Russia or anywhere else where law enforcement is deaf, dumb, blind, drunk, stupid and susceptible to bribes just in case a miracle happens.
Caught shagging the secretary[1] has to be favourite. So traditional as a reason for sudden defenestration that you have to wonder why so many senior execs do it.
You'd almost think that our lords and masters were actually a bit thick....
[1] During office hours for bonus "belongings are in the street and you can shove yer golden handshake where the sun shines" value.
And that answer is: bean-counting.
Anyone know what was the incredibly fucking stupid question actually asked?
(Hint: If you're ever in a company "focussing on costs" to "drive up shareholder value", leave. It's already standing on the bankruptcy court's doorstep and hammering on the door.)
Hmm. Much the same approach as a fixed-jet carburettor (when such things were used) and the reason why fixed-jet types stayed in use until the very end, despite being utterly crap by comparison to variable venturi types.
The fixed-jet type allows the fitting of a nice, lean idle jet (for testing at idle) along with a big, fat main jet[1] so yer boy racer's clog produces the desired effect at revolutions where the rules don't give a toss what's coming out of the tailpipe.
[1] and often an accelerator pump to squirt neat fuel directly into the venturi when you clog it. Yes, these things are to accurate fuelling what a 4lb club hammer is to tappet adjustment.
Actually that's an effect of flood defences.
Normally a watercourse will gradually spread out over its flood plain, causing a very shallow and very large lake. By bottling this up behind flood defences, you ensure that when, not if, they fail you get a sudden surge and a rather deeper lake in the place where the failure occurs.
The real answer is not to build houses on "prime building land in a picturesque setting" or "a flood plain" as I like to call it.
Well, that would work, if Google knew what they were doing. Their products positively encourage ignoring security warnings, 'cos they're so bloody anal about everything that the damned things appear all the time.
My favourite piece of arsehattery (which sums up Google's approach in this area) is Chrome's refusal to use SSL when the server's certificate fails to jump through all of Google's hoops, forcing fallback to an open connection. This is more secure how exactly.....?
I think that the slight snag here is that everyone goes for the free shit.
People qualified to verify information don't do it full time for free.
Thus any genuinely accurate and definitive data on the internet is doomed to be ignored in favour of vapid, crowdsourced bullshit.
I have a sneaking suspicion that human civilisation may well be fucked...........
Actually, when you think about it a bit, it makes perfect sense.
9.0, 9.1, 9.2, etc are the planned releases with functional changes. The point releases within those are unplanned patches to that release.
Same way it's always been done, it's just that they've pointed out that it's actually the small points that matter, security-wise. If you think about it this has always been true, as the increments within a release will only exist to patch something that was deemed serious enough that it couldn't wait for the next planned release.
Hello LibreSSL.
And that is why the likes of Microsnot only have to mark time to win, the opposition does the whole "divide and conquer" thing for them. "Fork rather than fix" is bloody stupid at the best of times as it stuffs reputation / goodwill and divides effort, weakening the entire offering.
The big corps already have a very jaundiced eye when it comes to desktop and database software (courtesy of the MySQL and OpenOffice debacles). Guess what? Nobody wants to run the risk of their strategic selection being suddenly obsolete overnight, courtesy of rabid, stick-up-bum arsehattery on the part of those who maintain it, when the people who pay your salary demand and expect n year refresh cycles.
FFS, give that one a rest! It's bollocks.
The pros all say that if you really want to find vulns in Open Source software, techniques such as fuzzing are the way to go[1]. Scrutinising code only serves to give you a headache. It might find a known vuln type squirreled away somewhere that nobody's thought to look for it before, but it won't find that new attack vector[2] that's the holy grail here.
[1] And a consistent detection approach that works on all software is the better way anyway.
[2] 'Cos you don't know what to look for, of course!
I didn't.
But then, having worked somewhere that had an all-Dell policy, I've refused to touch the things with a bargepole ever since.
Horrible, unreliable, slow old bags of shite, with cheap, plastic casings that seem to be made of eggshells and tissue paper and a support service that knows a million ways of saying "fuck off and die".
Well, colour me unsurprised.
Smartphones don't get security upgrade patches, just a full update once in a blue moon if you're lucky and it's not too old, so why would anyone be expecting tellies 'n such to get 'em?
Heavy hint for the very, very thick: If you expect whatever it is to last more than 18 months[1] and it has an internet connection, don't buy it.
[1] I.e. longer than it'll be in production.
Too damned right. When streaming a 2 hour film, who gives a rat's arse whether it took 1ms or 10ms to find the start of it?
The bit where it's sitting on a mere penn'orth of disk or a quid's worth of flash becomes rather important when you consider the whole film library though.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
