Re: And this ladies and gentlemen...
And please tell me how the blind drivers are expected to type on this keyboard?
975 posts • joined 26 Jun 2008
HP (IIRC) laptop power supplies had an issue a few (probably 8-10) years ago... the clover-leaf plug that came with them had a manufacturing defect which left an air bubble between live and ground. eventually the plastic deteriorated and it sparked across. Left quite a good flash burn in the socket, along with a very surprised customer!
Thankfully replacing the lead was all that was required, but it made quite an interesting root-cause investigation. Affected a sizeable batch too, but took a while to emerge.
Hospital waiting lists...
They won't identify anyway. Hospitals withhold their number for privacy. Can you imagine the conversation triggered by your phone ringing with the text "Hospital... about your abortion" and the sex-starved husband seeing it?
All you people moaning about google snooping... this is essentially a backhaul service, so do you know who provides all of the backhaul for each cell site that your mobile operator uses? Do you even care?
Hell, a lot of them go over microwave links which are inherently snoopable! (at least as much as this proposal facilitates anyway)
They're looking to automate connecting to WiFi to provide 'WiFi calling' functionality, which is essentially 4G-over-VPN. The "random store owner" doesn't see your traffic, just that a device has connected to a M(V)NO
If the minimum interval possible to configure had been in the order of 5-10 minutes, perhaps people wouldn't have come to expect email to be instant?
I still honour the hierarchy of priorities: telephone call for "urgent, must respond now" stuff; SMS for "ASAP but not necessarily immediate"; email for "FYI" or "sometime in the next 2 days" stuff. Yes, I also introduce unnecessary delays to get the point across.
Do you really think that facebook don't have a Apple-IDFA <> Facebook-ID mapping somewhere? Sure it may take a few impressions for them to confirm the link, but they'll just associate the new ID to your existing records.
This is not rocket science; it's far more lucrative.
The other point is that those costs vary, with some predictability and some unpredictability.
It's worth avoiding a school at pickup time even if it adds minutes to the average journey time, but it's fine to pass it at other times.
If there's an accident on the quickest road, it's better to take a different route early to avoid the whole area.
With local knowledge, these decisions are trivial. When working it out for the whole globe, I can see why they'd outsource the learning to machines.
My 3210 took a LOT of abuse. To the point that the battery clip broke and wouldn't hold the battery in place properly. I wedged a bit of card in between the battery and the cover, which worked fine for another few years.
I still think that if Nokia had embraced android, they could've avoided the whole Microsoft fiasco and would still be the dominant player in the phone industry.
But everything now is surface mounted, double-sided boards or all of the transistors in a single packaged IC. Therefore the tracks (aka antennae) are much shorter and generally routed with some consideration to where the ground plane is, which all reduces the amount of pickup.
(De-)couple that with better understanding and availability of decoupling, twisted pairs, isolating transformers and you have much better immunity.
And if the DoH server hasn't got that domain in its cache, what do you think it does?
It checks its upstream server, which at that level will almost certainly be/require a query to the root.
The problem is not the browser querying root directly, it's that everything it's looking up requires that the DNS provider queries root (because NXDOMAINs aren't cached, as well as being randomly generated).
If they checked it with <randomword>.google.com instead, that'd be absolutely fine regardless of protocol - the google.com NS & glue will be cached at all ISPs already.
They're referring to the time of placement, not the fact that the crockery is there.
Drivers wouldn't normally expect to encounter pedestrians on a roundabout.
I still think they're over-reacting, but at least I can understand what they're concerned about.
Obviously the only safe option is to deposit said china by quadcopter.
My other half works in a clerical role for the NHS. Most of her team are now back in the office, just those few who are shielding remain at home.
During the lockdown, everyone was working remotely at one stage, then they found they needed 1 person in the office, so that person worked alone in the office.
But the manager can't cope with not seeing the staff, so has insisted on getting everyone back. Thankfully the office is not crowded, but it seems daft to have everyone commuting when they've proven that working from home is at least equally efficient. (Difficult to quantify as the hospital has been quieter due to cancelling as many procedures as they could, so case load went down)
Me, I'm working from home about 80% of the time at the moment - just some hardware jobs need to be hands-on.
Amazon employ people whose role is explicitly to make their infrastructure secure (and pay them handsomely for it). Run-of-the-mill companies don't do such things.
OK, they also give their customers the tools to defeat that security if they so choose, but that is not the default setting.
So, AWS comes secure by default. (some) corporate IT drones would hook a windows server up to the internet with all ports open.
A competent in-house tech however can still beat any cloud based setup.
"It is always such fun when users take it upon themselves to diagnose issues, and usually ascribe them to a mystery virus or some other example of miscreancy"
The best I've had: I think it got a virus, so I ran a defrag on it but it made no difference.
The real problem (other than the user) was that the son had spilled coke over the keyboard.
"Hi, this is Barry from the Twitter IT department ( / development team / whatever). We're testing a new system and I'd like to get you to try it out."
"Umm. OK then"
"Yeah, just go to http://phishing.site and log in as normal. If you can test it out for a few days and then send us any feedback, that'd be great"
"Will do. Thanks"
The firewall in your router will behave in the same was as it does for NATed IPv4 connections.
It will reject any unsolicited connection requests from outside (by default; unless you've tinkered with it!)
The way IPv4 NAT works means that an IPv4 address (32bits) + port number (16bits) gets routed to the local device which initiated the connection, so IPv6 is no less secure anyway (32+16=48bits vs 128bits)
Of course there's something wrong in the code. There's no such thing as a perfect program.
But I assume you're looking for debugging technique more than programming language skills... so start with "where's the input validation?", progressing to "what if someone has set this parameter to zero?", then hitting the language issues "surely this print command should be a printf?" and "still allocating memory manually?"
Biting the hand that feeds IT © 1998–2020