Trump’s twitch. No not that one, the tweet about certain congresspeople “going home” (despite the fact that of the four women targeted, three were born in the USA).
Quite rightly it has been labelled as “racist” but without meaning to minimise that criticism, that is a personal insult to the four women (and we can get outraged on their behalf). But something that has been less pronounced: it’s also an insult to every single voter who elected those four women.
Trump was criticising those four women because they are criticising US government policy; as duly elected representatives and part of the US government, they are doing what they were elected to do. Criticising those women for doing their job is essentially saying they are not entitled to do their job and in turn those who voted for them are not entitled to their say.
And this attack on democracy is as important to highlight as the racism.
This question popped on Twitter just now; I’m not sure the question was a serious one, but as it happens I can answer the question as if it were serious. I’ve been running relatively small mail servers for nearly 30 years, so do know a litle bit about it.
This of course does not cover lots of “bolt ons” to email such as SPF, DKIM, DMARC, and that’s just the simple stuff.
To keep things relatively sane, I’m going to gloss over an awful lot of details – for example, there are all sorts of ways of composing and sending emails, but I will assume you’re using some sort of web interface such as Google Mail.
So you compose an email with an interesting picture or two, and click “Send”.
Hang on a bit! You also did some technical stuff when you entered an email address into the “To” field (if you just enter someone’s name, something somewhere is changing that to an email address) and possibly something summarising the email (or trying to get attention) into the “Subject” field.
Those two headers you have filled in – ‘To’ and ‘Subject’ – are just two of a whole collection of headers that are usually invisible. They are invisible because your mail client is hiding them from you; for good reasons as they’re almost always an unnecessary distraction.
But when you have to diagnose an email problem, seeing the full set of raw headers is kind of essential even if it is dead simple (for the relatively technically sophisticated) to forge headers.
For example, if you set up a dedicated mail client rather than use your mail provider’s web-based mail client, you will have to fill out your own email address (to go into the “From” field). You can fill anything you like into that field although you are unlikely to get a reply
If you fiddle with your mail client enough, you will realise that the “To” field can be changed to a “Cc” field or a “BCc” field. All three take email addresses, and can be used to send an email to someone but they operate in very slightly different ways.
The “To” header is for the main audience of a message.
The “Cc” header is for an audience who should also see the message, but perhaps don’t need to take any action based on the email.
The “Bcc” header is a bit special because it isn’t added to the raw mail message as a header, but is instead used to compose the envelope listing who should receive the email. If you need (or should) keep the list of people receiving an email secret, or just want to avoid an inconveniently long header for people to read then use the “Bcc” header.
Although your mail client may hide the details, email addresses look like :-
firstname.lastname@example.org (a “pure” email address)
“Some Name <email@example.com” (as normally formatted)
The Message Submission Server
So you click on “send”. What happens then?
The first thing that happens is that your mail client converts your email (attachments, rich formatting, etc.) into plain text which is why a file attachment just under your ISP’s limit on mail sizes can exceed that maximum.
To the top of that plain text version of your message, your mail client attaches some headers (again in plain text). In addition your mail client will prepare an “invisible” envelope independent of the headers – it contains just the address(es) you want to send to, and your own address.
Finally the mail client is ready to talk to the “mail submission server”. It will login (usually) with your credentials, and sends the message to the server using the “Simple Mail Transport Protocol” (SMTP).
The mail server adds your message to a queue and before it says to your mail client “Okay, I have it”, it will make sure that the message is safe on disk. Mail servers go to a lot of effort to make sure your messages don’t get “dropped on the floor” even when the operating system they are running on crashes.
After you have submitted a mail message to the message submission server, the message is held in a queue. This is significant because email is a store and forward messaging solution, so every server your message journeys through will make sure it is stored on disk before saying to the server sending the message “Yep. Got it.”.
In theory this should mean that messages never get lost “in the system” (although practice is often different to theory). The store and forward style of architecture suits the era that email is from – back in the 1970s when email could (and did) traverse many different kinds of network rather than “the Internet” that we have today.
What does that mean today? Amongst other things, it means that whilst you may think that your message only visits two mail servers – the one belonging to your ISP and the one belonging to the recipient’s ISP – and that is certainly a valid architecture for very small organisations.
But it does not work so well for larger organisations that may handle millions, or hundreds of millions of message a day. Summing up a large architecture without actually seeing an architecture diagram for every single ISP and large organisation on the Internet is going to be a bit hit and miss, but I’ll give it a go.
Your message submission server will probably simply hand your message off to a server responsible for sending email messages across the Internet. If it cannot send to the recipient’s receiving mail server on the first run through the queue, it may well just hand the message off to a “slow message server” (processing large queues is a bit of a drag).
In either case, the recipient’s server will accept the message and then hand it over to a “mailbox server” that the recipient will connect to.
And the journey is over. At every stage, reliability is favoured over speed.
How do servers send your message to each other? Using that SMTP standard I mentioned earlier.
The speed of email is a good topic to cover here. Speed is not what email is about in the same way that the postal service for physical letters is not about speed. It’s about reliability
Your messages may be readable by the recipient within 5 minutes 99 times out of 100, but that 1 time may take a day or two. That’s just the way that email works – if you want instant messaging, use an instant messaging client.
At no point have I mentioned encryption, and that is intentional. At no point is encryption required; email was designed in an era when computers were far slower and encryption was expensive (even though it was far weaker).
At every point, servers are trusting that the senders are not lying and the original sender is trusting that nobody is snooping on their emails.
To correct that there are a whole bunch of optional add-ons to the email standard to deal with that. But that is a story for another day.
Some of the reaction to Apple’s recent product announcements has been amusing to say the least.
First of all, let’s get the monitor out of the way first. If you think that monitor is ridiculously expensive, you’ve not looked at the specifications closely enough. Mid-range content creation monitors do cost that much – a quick look on B&H shows two monitors in the same price ballpark as the new Apple monitor, and the Apple monitor has higher specifications.
Not including the stand may seem a bit cheap, but frankly if you’ve already paid for a VESA stand that suits your working environment why pay for a stand that you will just throw away?
But yes, $1,000 for a metal stand is a little pricey. Given the negative reaction of the Apple fans at the show, I wouldn’t be surprised to see Apple drop that price (I also wouldn’t be surprised if they don’t).
Now onto the Mac Pro.
First of all, I should say that I’m not buying one – I don’t have the money, and whilst I run a somewhat underpowered workstation at work and a somewhat overpowered workstation at home, the strong points of the Mac Pro aren’t what I’m interested in and its weak points are where I’m interested in strength.
Is this expensive? Of course it is, but so is any high-end workstation – this isn’t your standard desktop PC! You can get a very roughly equivalently specced out Dell Precision 5820 for very roughly 2/3 the cost. But that comes with slower ECC memory and is much less expandable. You can also configure a Dell 7920 to a point that a Mac Pro looks cheap (it goes well above $100,000).
And you don’t buy such a system without expanding it beyond the base configuration.
This kind of machine is bought by professionals where the cost is less important than the return on investment. If it makes a professional just a little bit more productive, it can pay for itself within a year. Of the photographic (and video) professionals I watch on the tube, at least one is planning on buying three as soon as he can.
Could you get a better specification ‘DIY’ machine with a budget of say $15,000? Probably although it may not be as expandable.
Could you run macOS on it? Probably but it wouldn’t be supported by Apple (and that sort of thing is important in a corporate environment).
Could you get next day fix or replace support for your ‘DIY’ machine? Almost certainly not; and again, when any downtime costs you money, that sort of thing is important.
There are however two criticisms I would make of Apple :-
Storage. The new Mac Pro is severely limited in terms of storage expansion. In some ways that it is understandable; the sort of customer this is aimed for is likely to have a big fast NAS box somewhere. But I think they missed a trick by not offering a disk expansion chassis; perhaps an accessory tower that clips to the main tower doubling the width.
No “Mac Pro Mini”. There is still an empty spot in Apple’s product line-up covering the mid-range tower territory – in fact exactly what those who criticise the Mac Pro are effectively asking for.
@AOC seems to have poured a dramatic amount of petrol onto the fiery discussion regarding Trump’s border concentration camps by simply calling them concentration camps.
No matter how many people assume that ‘concentration camp’ means a Nazi extermination camp, that is not what ‘concentration camp’ means. As one dictionary states :-
A campwherepersonsareconfined,usuallywithouthearingsand typicallyunderharshconditions,often as a result of theirmembership in a groupthegovernmenthasidentified as suspect.
Although that is not from the full Oxford English Dictionary, I have checked with that definitive work and it’s definition agrees with the above.
The relevant Twitter threads are filled with agreements and disagreements, and it is the later I’ll take a closer look at.
At least in some instances; more than a few consist of approximately “Well they’re illegal immigrants so they deserve it” which is so repulsively disgusting that the only appropriate response is a good slap.
The next objection is along the lines of: “You can’t call them concentration camps; that would be disrespectful to the 6 million Jews that the Nazis murdered”.
Funnily enough, it’s rarely mentioned that the Nazis also killed 11 million other people as well as the 6 million Jews. Almost as if there is a politically acceptable “holocaust denial” (strictly speaking the Holocaust is only the Jews; there isn’t an acceptable ‘cool’ name for the entirety of the Nazi crimes against humanity).
Let’s correct a few misconceptions about Nazi concentration camps (and there have been plenty of other concentration camps around the world) :-
The concentration camps were first created in 1933 to hold political prisoners and union organisers. Those targeted for starvation rations, brutal treatment, and slave labour rapidly grew to include homosexuals, Romani, communists, socialists, the disabled, Poles, Slavs, Soviet POWs, and just about anyone who could be labelled “undesirable”.
Jews were also targeted as soon as the Nazis came to power but weren’t sent en-mass to concentration camps until 1939 when they were forced to live in Jewish “ghettos” (effectively concentration camps).
The extermination camps were set up in 1942 to speed up the “final solution”; approximately 90% of those killed at these extermination camps were Jewish.
There is also “But Obama did it first” (these camps were first instantiated in 2014 under the previous administration). This is distinctly reminiscent of the wailing child that gets caught with his or her hand in the cookie jar “But someone else did it first”. As I understand it, the scale of the previous administration’s camps was far less than now, but give me a time machine and I’ll still go back and tell off Obama.
Now back to our original topic. Is it fair to call the border camps ‘concentration camps’? They certainly meet the dictionary definition, and there are genuine reasons why the comparison with the Nazi concentration camps is entirely appropriate.
That is not to say that the border concentration camps are comparable to the Nazi concentration camps in 1944, but there are many disturbing parallels to the Nazi concentration camps in 1934. The time to stop these camps potentially evolving into something similar to the Nazi concentration camps of 1944 is now.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.