Certainly the earliest ones, yes. It's described as "mechanical turk".
There's an Amazon division for it.
2317 publicly visible posts • joined 26 Jun 2008
Am I the only person to read this and think "good"?
I run an email service and I'm sick of clueless users adding a perfectly good account to gmail in that way, then complaining when it doesn't behave properly.
Add the account to the gmail app on your phone if you feel that you have to, but don't get gmail servers to collect directly.
My servers support IMAP(s) and POP3(s) natively and if you can't handle those there's a webmail interface as well. No need to pull anything through a third party.
as "the AC poster above" (not actually AC), I agree with you on that point. They need a table number*, food choice and payment. Anything else is mission creep.
* table number can be omitted if it's a counter collection, in which case they return a token number instead.
No, a lot of the time I prefer to not have to interact with people, so give us the choice.
If I do the order myself, it won't be transcribed badly, nor bits forgotten. Or at least if that does happen I can't blame someone else.
Fine dining is a different matter, but airport dining should be as transactional as possible in my opinion.
Local time includes a defined timezone - which in many places will be different for DST, so the mapping can still be one-to-one.
Weird behaviours around leap-seconds excepted. But anything depending on powershell won't care about the odd second here or there.
In fairness, I've seen a huge number of "x hasn't worked since y was installed" when x and y are completely unrelated pieces of kit... that turns out to be that when the engineer installed y they dislodged a cable that goes to x, or generates RF interference, or blocks a signal.
You can declare it unlikely and it can be technically/logically impossible, but never rule it out until you've confirmed it.
I've learned that people don't react well to being told outright that they're wrong. I've become quite diplomatic with it. I'll often go with: "we have a saying in the IT world: trust, but verify. In the same way as an electrician will trust that you've turned the switch off but will still check that the circuit isn't live, I'd just like to confirm ..."
In the article's case that would probably be followed up with "the connection was loose at the other end, so was probably intermittent. I've re-terminated it so should be OK now" - gives them an element of them being right when we know that they were spewing bullshit.
I can advise that amongst the athletic population it's usually the less well-endowed gender that requires nipple protection. They chafe on the inside of a shirt/vest, particularly in cold/wet conditions. The more well-endowed tend to wear a sports bra to hold everything in place and thus don't experience the same chafing.
And specifically the phone needs to know what constitutes an emergency call, so it needs to know that 000 is the local emergency number.
A very old (think late 90s) hack, that I most certainly did not perform, allowed you to configure what numbers the phone treated that way. It didn't take the networks long to block 'emergency' calls to non-emergency numbers.
Why not on someone else's machine someplace?
As long as it's not your only copy and it's suitably encrypted, it's fine.
Actually it's the easiest way to have an off-site backup - rent a machine somewhere online to use as a backup destination; just don't count on that particular one being available when you need to access a backup. It's not a substitute for a hard disk stored unpowered in your parent/child's safe, but it's still useful.
Basically: backup on RAID - Redundant Array of Inexpensive Destinations ;-)
In some bespoke software I'd written there was a should-never-happen scenario which produced an error message along the lines of "phone Anonymous Coward and tell them this number: 168702342" (there were several such messages each with different numbers) - this was a debug build intended to pinpoint the conditions that led to the should-never-happen happening.
I took such a call, stating "I was using the software and an error popped up saying I should call you and give you a number" "OK, what was the number?" "I don't know, I've closed the window now"
I fully support the idea of giving a bunch of technical experimenters the resources to experiment with, but the scale seems wildly excessive. Are they wanting to assign an IP address to every Hz in the spectrum?
The whole "IPv6 has 340 undecillion addresses" argument is moot if you're dishing them out in blocks of 5 nonillion - we'll run out eventually, and a lot sooner than people think.
The equivalent of switch debouncing: wait until the data is in a stable state before acting on it.
Then someone comes along and "optimises" the code - "why are we waiting here? Delete"
That's my experience anyway... I'll leave it to you to work out whether I was the one who wrote the initial code, or the one who sped it up.
The backup plan is to leave astronauts up there for a bit longer. There's (IIRC) about 6 months of reserve food etc on the ISS, so why rush?
Butch and Suni where fully trained astronauts and happy to stay up there doing useful work, which gave NASA and Boeing a chance to check out the calamity capsule properly before deorbiting it. Doing that meant they couldn't park another dragon, so no point launching one early.
Of course they can't publicly state this while His Orangeness is in power as that would contravene his declarations and therefore lead to massive budget cuts.
There are standards. OBEX - either OBEX Push or OBEX FTP
From phone I can hit share, select bluetooth. From PC right-click on bluetooth and select 'receive file'. Very similar process the other way around.
As the article states, this was a protocol built for InfraRed and ported to bluetooth, which gives you an idea as to how old it is.
> "The free LocalSend app allows me to quickly and easily share files wirelessly between devices running Android, macOS, iOS, Linux, and Windows"
Yes, and basically every bluetooth implementation I've come across in the last 20 years will also do all of that. But using Quick Share or AirDrop will be easier and more secure.
Why apple refuse interoperability is beyond me though.