81–83 of 83 posts
> Blackberry at the time was kindof of an “everything goes, whatever it takes” free for all. And this damn the torpedoes full steam ahead attitude was pervasive everywhere. Red tape and beuaracracy was loathed by everyone. Ironic as RIM became known for its cripplingly dense beuaracracy and red tape.
Earlier quoted context omitted.
> bottom-posting Immediate and indefinite suspension of email license.
A: Because it messes up the order of things. Q: Why is top posting bad?
In reality it's:
Q: Why is bottom posting bad?
Q: Why is bottom posting bad?
A: Because it repeats itself.
Q: Why is bottom posting bad?
A: Because it repeats itself.
Q: Isn't this also a problem with top posting?
Q: Why is bottom posting bad?
A: Because it repeats itself.
Q: Isn't this also a problem with top posting?
A: No, because the reader skips to the next message when they get to the quoted part.
The story of Bedlam3: https://rodneymbliss.com/2013/10/17/i-survived-bedlam3/ >
> it’s estimated that over 15 million emails were generated in the space of about an hour. wtaf?
If 1% of emails are blind replies from people out of the office, but are tracked by the originating sender (not the DL) since OOO messages in Exchange get sent to the DL (as well as the originating sender) and soon enough you have Exchange sending a new OOO email per reply from a new reply-er. Your typical company the size of Microsoft is going to have probably... 3-5k people out of the office at any one given time (the lingo is "OOF", or "out of facility")
OOOs can also trigger another OOO, which can in turn cause a new OOO to spawn.
Soon, you've got OOOs reply-all'ing to OOOs and drenching a DL... and an exchange forest.