arahir:

arahir:

arahir:

i’m reading a very manly 1950s account of a hunt for el dorado but i’m thirty pages in and the narrator has already described his traveling companion as “handsome” 4 times, “extremely handsome” twice, “exceedingly handsome” once, his voice as “quietly husky” and “a husky whisper,” his fingers as long and deft, his body as “tall and cat-like,” and his eyes as some variation of ice-blue at least three times.

just men being dudes. dudes being pals. it’s great. this is great.

“Ever since he had aimed that gun at my throat, I had liked him immensely. And now I liked him even better.”

oh my god

“I awoke when a beam of light fell across my eyes. Jorge had come into my room carrying a lighted candle.

‘I’m going with you,’ he said quietly.

‘I can’t pay you.’

He smiled. ‘I thought I was a partner?’”

OH MY GOD

I am enjoying this continued saga immensely.

cshorrorstories:

by sfsdfd

I witnessed this astounding IT meltdown around 2004 in a large academic organization.

An employee decided to send a broad solicitation about her need for a local apartment. She happened to discover and use an all-employees@org.edu type of email address that included everyone. And by “everyone,” I mean every employee in a 30,000-employee academic institution. Everyone from the CEO on down received this lady’s apartment inquiry.

Of course, this kicked off the usual round of “why am I getting this” and “take me offa list” and “omg everyone stop replying” responses… each reply-all'ed to all-employees@org.edu, so 30,000 new messages. Email started to bog down as a half-million messages apparated into mailboxes.

IT Fail #1: Not necessarily making an all-employees@org.edu email address - that’s quite reasonable - but granting unrestricted access to it (rather than configuring the mail server to check the sender and generate one “not the CEO = not authorized” reply).

That wasn’t the real problem. That incident might’ve simmered down after people stopped responding.

In a 30k organization, lots of people go on vacay, and some of them (let’s say 20) remembered to set their email to auto-respond about their absence. And the auto-responders responded to the same recipients - including all-employees@org.edu. So, every “I don’t care about your apartment” message didn’t just generate 30,000 copies of itself… it also generated 30,000 * 20 = 600,000 new messages. Even the avalanche of apartment messages became drowned out by the volume of “I’ll be gone ‘til November” auto-replies.

That also wasn’t the real problem, which, again, might have died down all by itself.

The REAL problem was that the mail servers were quite diligent. The auto-responders didn’t just send one “I’m away” message: they sent an “I’m away” message in response to every incoming message… including the “I’m away” messages of the other auto-responders.

The auto-response avalanche converted the entire mail system into an Agent-Smith-like replication factory of away messages, as auto-responders incessantly informed not just every employee, but also each other, about employee status.

The email systems melted down. Everything went offline. A 30k-wide enterprise suddenly had no email, for about 24 hours.

That’s not the end of the story.

The IT staff busied themselves with mucking out the mailboxes from these millions of messages and deactivating the auto-responders. They brought the email system back online, and their first order of business was to send out an email explaining the cause of the problem, etc. And they addressed the notification email to all-employees@org.edu.

IT Fail #2: Before they sent their email message, they had disabled most of the auto-responders - but they missed at least one.

More specifically: they missed at least two.

Source: https://redd.it/420oan