3 ms·
I'm going to start submitting stories like "${trendy_website} breaks ${random_official_sounding_standard} with ${what_can_break[random_official_sounding_standar
by justin_vanw 17y ago
I'm going to start submitting stories like "${trendy_website} breaks ${random_official_sounding_standard} with ${what_can_break[random_official_sounding_standard]}" and link it to a post on some newsgroup. My karma will go through the roof.
- wmf 17y agoDespite the sarcasm, there is a kernel of truth here. It is difficult to be fully compliant with every standard at all times. Bugs happen. Support people deny that bugs exist. If Facebook is sending some improperly formatted mail, that's hardly news.
- justin_vanw 17y agoIt's mundane, very very mundane. I don't think you can be, like, super-mundane, because being surprising in any way, even if it is for how mundane you are, would make you in fact not mundane at all. So although I don't know how to say it, this is as mundane as you could possibly get before you cause some kind rip in the mundane-exciting continuum.
- ramidarigaz 17y agoI'm not sure what you're trying to say, but it's funny.
- drewr 17y agoMy purpose in posting the message was actually to try and get Markus's issue in front of someone other than a first-tier support person. I'm fairly certain that facebook developers frequent HN. I wanted them to at least know that they were violating a standard and someone feels the pain of their decision. I've been a mail admin. Dealing with the traffic that facebook generates is not trivial. It's akin to the hoops I would have to jump through for AOL and Hotmail five years ago. Quoted-printable breakage is not a major problem in the long run, but if there isn't a good reason for the violation, then why not fix it? It may have just been oversight. I used a provocative title because I wanted people to read it, mod it up, and allow fb engineers the chance to speak for themselves. If no one found it compelling then it wouldn't have garnered any karma and you wouldn't have seen it.