<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Thu, Oct 30, 2014, at 07:23 PM, JoeS wrote:<br></div>
<blockquote type="cite"><div><span style="font-family:Arial" class="font">Hey, I understand there are always "Edge Case" TB
users, whose wants can be pretty much dismissed.</span><br></div>
<div><span style="font-family:Arial" class="font">
But more and more, especially in this age of social media,
communications are expected to be web-like.</span><br></div>
<div> </div>
<div><span style="font-family:Arial" class="font">
We have done little to address this trend.</span><br></div>
<div> </div>
<div><span style="font-family:Arial" class="font">
I urge you all (as painful as it may be) to read through the
following bugs completely:</span><br></div>
<div> </div>
<ul><li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=250539"><span style="font-family:Arial" class="font">250539</span></a><br></li><li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=590640"><span style="font-family:Arial" class="font">590640</span></a><br></li></ul><div><span style="font-family:Arial" class="font">And as you read, ask yourself how we could ask
these users to contribute to TB</span><br></div>
<div> </div>
<div><span style="font-family:Arial" class="font">
JoeS1</span><br></div>
<div> </div>
</blockquote><div> </div>
<div>Totally unrelated (or maybe not), FastMail open-sourced our HTML5 editor a while ago. It is pretty much entirely designed for generating nice HTML emails.<br></div>
<div> </div>
<div><a href="https://github.com/neilj/Squire">https://github.com/neilj/Squire</a><br></div>
<div> </div>
<div>It works very nicely in Firefox (that's what I'm doing now), and it doesn't come with any UI of its own, just good APIs for hooking up your own UI.<br></div>
<div> </div>
<div>....<br></div>
<div> </div>
<div>Back on topic - yes, those bugs - ouch. This isn't a rare problem in open source either - look on any project. But then check this out:<br></div>
<h1 title="" id="v230">Bug ID 18777415: Use RFC6186 for auto discovery of mail server settings<br></h1><div class="" id="v231"><div class="ExistingMessageView" id="v232"><div class="MessageView last" id="v233"><div class="header"><div class="fromAndPreview"><h2 title="devbugs@apple.com" class="from colour2">Apple Developer Bug Reporting<br></h2></div>
Oct 29<span> (23 hours ago)</span><div class="recipients"><span class="to"> to <span title="appledev@fastmail.fm">appledev</span></span><br></div>
<div class="recipients"> </div>
</div>
<div class="body"><div class="message"><pre>Hello Marian,
Engineering has determined that your bug report (18777415) is a duplicate of another issue (7685458) and will be closed.
The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.
An example of the duplicate section from the bug reporter user interface with your bug and the duplicate bug info is included below:
18777415 Use RFC6186 for auto discovery of mail server settings
State: Closed Product:
Rank: No Value
---------------------------------------------------------------
Duplicate of 7685458 (Open/Closed)
---------------------------------------------------------------
If you have any questions or concerns, please update your report directly here: <a target="_blank" href="http://bugreport.apple.com/">http://bugreport.apple.com/</a>.<br></pre><div defang_dir="" class=""> </div>
<div defang_dir="" class="">========<br></div>
<div defang_dir="" class=""> </div>
<div defang_dir="" class="">You don't have a monopoly on shitty responses to bug reports. This is us reporting that fastmail.com autodiscovery in Apple's mail client is broken - with an RFC they bloody well wrote themselves. We will get no more information on this bug, only the original reporter will.<br></div>
<div defang_dir="" class=""> </div>
<div defang_dir="" class="">And we're paying them for the privilege of a developer account, and every one of the users who is being affected by this bug paid them for their software.<br></div>
<div defang_dir="" class=""> </div>
<div defang_dir="" class="">So don't be too hard on yourselves as you read this bug. Certainly resolve to be nicer to bug reporters, and make things not crap - but don't be too ashamed to ask for money so that you _can_ dedicate resources to fixing their issues. I bet a few of those reporters and their big companies would have been willing to pay for a fix if you'd been able to phrase it the right way to the right person. They pay licence fees to other companies for the illusion of being listened to.<br></div>
<div defang_dir="" class=""> </div>
<div defang_dir="" class="">Bron.<br></div>
</div>
</div>
</div>
</div>
</div>
<div> </div>
<div id="sig567075"><div class="signature">--<br></div>
<div class="signature">Bron Gondwana<br></div>
<div class="signature">brong@fastmail.fm<br></div>
<div class="signature"> </div>
</div>
<div> </div>
</body>
</html>