Re: There is another option
"Well, software has a rather larger state space than a toaster, so good luck with that."
One option would be to stop cramming junk in. Make the state space smaller, spend more time testing.
16427 posts • joined 16 Jun 2014
'Isn't that in the account settings, "Manage identities?". If you have an alias set for an account there, TB will automatically use the matching reply-to when you respond. If you don't set it, you get the core email address for the account. I use it for generic incoming addresses like "info@".'
Yup. That works for me. Plus if you have the identities set up you get a drop down list to select the identity to use when sending a new email.
'I prefer clunky and brutally functional over flashy and useless any day.'
Agree again. Actually I prefer non-flashy and functional over flashy and functional.
"S/MIME and PGP don't exist in your universe?"
And you're telling me the mail protocols make provision for a PKI? And do it all invisibly so that Joe Soap would be sending & receiving encrypted & signed emails without even being aware of the fact? Until then encrypted email is more of a monoverse than a universe.
If you've got PGP & nobody you know doesn't & doesn't know how to set it up then it's no use to you. It has to be the built-in default to be anything more than a fringe interest.
" With the right tweaks over time and encryption baked in... there is an opportunity to alter the basics of email with a user base that has the potential to make things stick."
It would need a new RFC to extend the protocol if you want end-to-end encryption. You'd also need to bring servers or some other means of providing a PK framework and other clients into the fold. I don't see how a new T-bird could achieve that on its own. I'm not saying it's a bad idea; far from it because it's something we need.
"There are additional security features. E5 "Advanced Security" includes Advanced Threat Protection (ATP) for Exchange Online, with behavioral malware analysis and blocking and tracing of malicious links in emails. ATP is also available as an add-on for other plans."
This wonderful offer brought to you by the company whose Hotmail/Live/Outlook/NameOfTheWeek service leaks spam pretending to be from themselves. This really is something they should be on top of if for no other reason that they're tolerating infringement of their own trademarks.
The whole system seems remarkably ill-thought out. The plaintiffs may well have good cause but if anything spawns notifications at that rate is completely automatic and Cox's point that they're simply allegations is a reasonable point. Far better to have taken a sample and been able to show that they've been carefully checked and are verifiable. If Cox then refuses, take those to court and ask for the remainder to be taken into consideration.
"Compiling for 32 bit isn't a problem. Doubling the amount of time they have to devote to testing is."
To quote the post you were replying to:
"We can have entire operating systems (NetBSD) that can be compiled on any architecture, for any architecture, with every single piece of the OS compiling and running just fine on a plethora of CPUs"
NetBSD can do this and, I'm sure, test. Maybe they use these new-fangles computers to automate testing.
"Does anyone outside of the control space use 32 bit x86 Linux for serious computing *in the past decade?"
Yes. I have some non-free 32-bit S/W I use frequently, maybe not quite daily but often enough. Ay a pinch I could convert.
There's a fundamental problem with the human mind, an overwhelming tendency to generalise:
I don't use 32-bit Linux therefore nobody does.
I don't use the desktop to store WIP therefore nobody does (UX-designers I'm looking at you).
I can't make Linux or Libreoffice work for me therefore nobody does (more likely they couldn't 15 years ago & haven't tried since).
And on it goes.
"As a European public organisation the EPO fully respects freedom of the press as a core value of an open society"
Or "your privacy".
Or "your phone call is important to us"
Don't they realise we all cottoned on to that years ago? Now it's a flag drawing attention to what they're trying to hide.
If some aspect of your job makes you a witness to something that ends up in court you could end up being summoned. For most people this is an unlikely event does affect forensic scientists. After I quit that job the summonses went on for a year or so including one for a civil case stemming from a fatal accident I investigated years before I quit. And then a year or too ago an old colleague emailed me to tell me of an arrest in a case which would have been over 20 years old at that time; fortunately nothing came of that one.
Actually both the examples I gave in another post were coded in 4GL. But that wasn't the problem - exactly the same mistakes could have been made in C. The problem was failing to understand how to use the database engine (which was, of course, written in C). An efficient language is no obstacle to writing inefficient code.
"Mind you developers can be very inefficient too."
Mmmm. I remember the program that was going to take over 24 hours to load a day's data into the replenishment system. And that was the second effort of that vendor's I had to debug for them. The first just asked the database engine to spawn more & more objects without freeing any or re-using them until it burst.
"Access is (was) supposed to be a straightforward way to build apps for data without needing to know code"
But as it was built on an RDBMS unless its users needed to know how to design a database. If they couldn't get that right no amount of code knowledge avoidance was going to help.
"the Wikipedia article seems to suggest only protons are involved"
It's only the protons that are charged so it's those on which the accelerator works. The neutrons are just along for the ride.
A car analogy - it's only the tyre contact patch that touches the road so it's that that gets accelerated and the rest of the car is just along for the ride.
I wonder why they didn't remind us of their previous predictions.
When these firms trot out their press releases I wish the media would ask them for their previous predictions for now. And if they don't provide them, just dig out a few from the archives.
"And whats more, is that the data the OS collects is because it requires it for services to work as has been stated my many others and not just in this forum."
Some people simply don't seem to realise that what's documented by omission is as important as what's documented explicitly. Consequently quite amazing stuff can be hidden in plain view.
Go back and read those T&Cs again.
It looks friendly and reasonable. It adopts the tone of voice that the nice policeman uses when he's trying to talk the loony off the bridge. It seems persuasive. When it talks about collecting login IDs and details of transactions that seems reasonable. And so it is if you start off assuming that they're talking about login IDs for Microsoft services and transactions with Microsoft. But nowhere does it say that such a limitation applies. Do you really believe that there isn't as much as a space, let alone a comma or full stop in those documents that hasn't been carefully considered for its legal implications. Learning to read specs & contracts & notice what's missing really should be a skill everyone in IT learns.
And, of course, once they've got you persuaded then they drop in all the other stuff they've absolutely no business in finding out. What is essential to providing Microsoft services about their knowing your gender, the sports you follow or all the other crap that gets listed there?
Are they collecting this stuff now? Maybe, maybe not, but if the don't collect it now they've given themselves carte blanche in their T&Cs to turn on such collection any time they wish and through the unavaiodable updates have provided themselves the means to do so.
That's the problem right there. As far as possible you turn up when you feel like it and don't turn up at all when you don't want to. As for the rest there's either a mechanism (e.g. 2nd Tuesday in the month) or a scribbled note on the kitchen calendar.
Biting the hand that feeds IT © 1998–2019