Live data from Hacker News

Rim/Blackberry tales – reply all

awadwatt.com

41–50 of 83 posts

Re: Rim/Blackberry tales – reply all

#41
post #20
post #5

Earlier quoted context omitted.

I don't understand why this isn't configurable. Why can't the basic data structures (of one email after another in serial) be displayed in either order depending on mail client settings? Admittedly I haven't looked into it because I'm perfectly fine with top posted emails. But I routinely sort files in my directory. Why not emails in a displayed thread?

As the other comment mentioned, the email body contains the entire quote chain. The way clients accomplish threaded display is a combination of: - parsing the unstructured email body and looking for quote levels, html formatting and printed email heads - parsing certain headers like message-id, in-reply-to, dkim sig - looking for sections of the message body in the inbox This is done because there is nothing in the p…

This is true. OTOH, I do think the problem is solvable.

I came up with a routine to parse and translate about 2-3GB of saved emails into MBox format once.

The official delimiter is unbelievable, IMHO.

« the exact character sequence of "From", followed by a single Space character (0x20), an email address of some kind, another Space character, a timestamp sequence of some kind, and an end-of-line marker. »

https://datatracker.ietf.org/doc/html/rfc4155

https://en.wikipedia.org/wiki/Mbox

That's it. An email is a section of text beginning with

From $something

That's the spec.

Re: Rim/Blackberry tales – reply all

#42
post #3

The world needs a driving licence for email. It would mandatorily include use of plain-text and bottom-posting.

A local technical college has a dedicated course on "Slack at workplace" (or a paraphrase of the title).

Hopefully they’re discouraging students from sending lots of fragmentary messages interspersed with superfluous nonsense like “hey” “i mean” etc

Re: Rim/Blackberry tales – reply all

#43
post #3

The world needs a driving licence for email. It would mandatorily include use of plain-text and bottom-posting.

I hate both of those things. I guess this means war, please look for my envoy bearing the formal declaration of war.

You are wrong.

https://useplaintext.email/

The biggest and most successfull FOSS project of all time is coordinated entirely by email. These are the rules:

https://subspace.kernel.org/etiquette.html

Again: you are wrong.

Re: Rim/Blackberry tales – reply all

#44
post #7

That random “J” at the end of the messages brings me back to mail circa 2010. As I recall, iOS also didn’t render Outlook’s smileys right, leaving a bunch of Js in mail from my Mom. (For the ones who ‘missed’ it: https://devblogs.microsoft.com/oldnewthing/20060523-10/?p=31... )

same here J

Re: Rim/Blackberry tales – reply all

#45
post #2

Some nice nostalgia for me -In high school we walked to that exact KFC for lunch and would discuss the previous nights antics playing StarCraft broodwar. -I used to fix computers (professionally) at a store on the same street as that gas station as an after high school job -In Dec/jan 2010 I worked 18 hours a day laying floors in the new RIM buildings at Philip/Colombia. A friend’s dad did a lot of the furniture movi…

>-Waterloo has seen serious decline since the death of RIM

>-Not sure it will ever come back, most people including myself left years ago.

I think you overestimate Waterloo's decline just a tad, perhaps your perception being coloured by leaving it. I assure you, it's thriving and in many ways better than the early 2000s when I went to UW. Including the condo boom you mention, though I'm puzzled why you think this somehow hurts walkability.

But yes, Lester street is unrecognizable and every single house I lived in between 2002 and 2007 is gone.

Re: Rim/Blackberry tales – reply all

#47

This happens often enough (even MS itself broke their internal Exchange servers). And every story seems to end with admins having to improvise. Am curious: (why) isn’t there a “kill reply-all chain” button as a feature? (The article explains that this didn’t work for RIM because of BB’s architecture, but for Exchange?)

The search term for MS for is bedlam 3.

I worked at MS in 2012 and we had another email storm that shut down almost everything. I remember not being able to do any work at all because the network was so slow I couldn't even edit files (the internal source control system required getting a lock on the file to be able to edit them).

Re: Rim/Blackberry tales – reply all

#49

I don't know why these articles (and many comments here) always make it sound as if the people replying were idiots. For many, or I'd rather say most in this case, it's clear that they know exactly what they're doing - having some fun given the opportunity that presented itself.

Reply all storms are some of the most amusing things to witness and joke about with your colleagues. Sadly I haven’t seen a good one in a very long time :-(

Re: Rim/Blackberry tales – reply all

#50
I vividly remember this incident and more like it. I was coached by my manager to never reply all to an email addressed to a larger distribution group because of this exact reason. Not only were you annoying people, but everyone's email ended up getting delayed for an hour or two.

Can someone explain to me why the backlog would happen? Why they didn't have systems to protect from such a basic DOS attack?

Post reply on HN