<div dir="ltr">Hi Keith,<div><br></div><div>can you give some more details on how to do this? I'd love to use Unison for this, but I have no idea how to set this up. Any help is greatly appreciated.</div><div><br></div><div>--</div><div>Ilya<br><br><div class="gmail_quote"><div dir="ltr">On Wed, Mar 9, 2016 at 1:47 PM Keith Smiley via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For those who are just interested in getting these conversations out of their<br>
email in the meantime, you can use the nntp bridge at<br>
<br>
<a href="http://news.gmane.org/gmane.comp.lang.swift.evolution/" rel="noreferrer" target="_blank">http://news.gmane.org/gmane.comp.lang.swift.evolution/</a><br>
<br>
Along with Panic's retired Unison app<br>
<br>
<a href="https://panic.com/blog/the-future-of-unison/" rel="noreferrer" target="_blank">https://panic.com/blog/the-future-of-unison/</a><br>
<br>
As a pretty good GUI for this.<br>
<br>
--<br>
Keith Smiley<br>
<br>
On 03/09, James Campbell via swift-evolution wrote:<br>
> They are listening but they keep saying they don't have the resources. So I<br>
> would encourage them to let the community give back and set something up !<br>
><br>
> *___________________________________*<br>
><br>
> *James⎥Head of Trolls*<br>
><br>
> *<a href="mailto:james@supmenow.com" target="_blank">james@supmenow.com</a> <<a href="mailto:james@supmenow.com" target="_blank">james@supmenow.com</a>>⎥<a href="http://supmenow.com" rel="noreferrer" target="_blank">supmenow.com</a> <<a href="http://supmenow.com" rel="noreferrer" target="_blank">http://supmenow.com</a>>*<br>
><br>
> *Sup*<br>
><br>
> *Runway East *<br>
><br>
> *10 Finsbury Square*<br>
><br>
> *London*<br>
><br>
> * EC2A 1AF *<br>
><br>
> On Wed, Mar 9, 2016 at 6:28 PM, David Hart via swift-evolution <<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
> > +1000<br>
> ><br>
> > Sent from my iPhone<br>
> ><br>
> > On 09 Mar 2016, at 11:34, Adrian Kashivskyy via swift-evolution <<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
> ><br>
> > I'm a very big supporter of moving the discussions to a Discourse forum<br>
> > installation. Here are my arguments:<br>
> ><br>
> ><br>
> > 1. *Subscribing to interesting threads*<br>
> > In the mailing list, it is not possible to subscribe to a thread<br>
> > unless the mail client supports it. In a forum, you can subscribe to a<br>
> > thread and you may even turn on email notifications.<br>
> > 2. *Muting uninteresting threads*<br>
> > Unless the mail client is supporting it (many don't) – it's not<br>
> > possible to mute a thread – all emails are equally important.<br>
> > 3. *Searching*<br>
> > It is way easier to search an indexed forum like Discourse, than<br>
> > searching through 12k emails<br>
> > 4. *Message formatting*<br>
> > We tend to include many code examples and formatted text in our<br>
> > messages. Some of us tend to create markdown files on the side and then<br>
> > paste the generated HTML into an email body. Discourse supports<br>
> > mix-and-match of Markdown, HTML and BBEdit.<br>
> > 5. *Tags*<br>
> > In the mailing list, most of us tend to include [tags] in the mail<br>
> > subjects, but some folks forget or ignore them. Discourse allows to<br>
> > predefine tags for the threads which improves indexing and searching even<br>
> > more.<br>
> > 6. *Pinned threads*<br>
> > Announcements of e.g. ongoing reviews may take a form of pinned<br>
> > threads so they are immediately visible to forum members.<br>
> > 7. *The problem of replying to a thread with a changed subject*<br>
> > Sometimes users reply to threads but accidentally add a tag or a<br>
> > whitespace to the message subject. Most mail client interpret it as a new<br>
> > thread and such a reply may be lost in the wild. Replies to coherent forum<br>
> > threads are never lost, they're always in the right place.<br>
> > 8. *Accessibility*<br>
> > Even if your mailing client allows all of the above features,<br>
> > sometimes it is needed to access the forums from a phone or on a university<br>
> > computer, where many functionalities are blocked. Although it is possible<br>
> > to access the webmail page in the browser, it is most often painful to<br>
> > navigate through archives (especially on <a href="http://icloud.com" rel="noreferrer" target="_blank">icloud.com</a> ¯\_(ツ)_/¯). When<br>
> > using Discourse, all above features are available everywhere.<br>
> > 9. *Permanent links*<br>
> > To share a link to a Discourse discussion, you just copy it from the<br>
> > browser URL field. To share a link to a mailing list reply, you need to<br>
> > open the web archive, find the topic manually and then copy the URL from<br>
> > the browser field anyway.<br>
> > 10. *Mentioning other users*<br>
> > In mailing list, this is achievable by including the target user in a<br>
> > recipients list. In forum, you just @mention someone, just like in GitHub<br>
> > issues.<br>
> > 11. *Privacy*<br>
> > Some users don't want their private emails to be disclosed in a<br>
> > mailing list. In a forum like Discourse, you can choose whether your email<br>
> > is displayed publicly or not.<br>
> ><br>
> ><br>
> > I can actually go on and on with my points, but I very much hope that the<br>
> > above list is sufficient to start a serious discussion about migrating to a<br>
> > forum, like Discourse.<br>
> ><br>
> ><br>
> > Regards,<br>
> > Adrian Kashivskyy<br>
> ><br>
> > Wiadomość napisana przez Fload via swift-evolution <<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> w dniu 06.03.2016, o godz. 23:46:<br>
> ><br>
> > Using Mail here, it works well for me! :)<br>
> ><br>
> > On Mar 6, 2016, at 9:31 PM, Kevin Lundberg via swift-evolution <<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
> ><br>
> > I wonder if some of the dislike for mailing lists here is due to people<br>
> > using Mail.app on osx/ios to keep up with discussions. I find that<br>
> > Thunderbird's mailing list handling is really nice (much better than<br>
> > Mail.app), since it correctly shows replies as a tree so it's easy to see<br>
> > which messages reply to which at a glance.<br>
> ><br>
> > On 3/6/2016 12:54 PM, Goffredo Marocchi via swift-evolution wrote:<br>
> ><br>
> > Setting up a custom Google Wave service? ... *waits for laughter to die<br>
> > down* it is actually open source and did its job well actually.<br>
> ><br>
> > Sent from my iPhone<br>
> ><br>
> > On 6 Mar 2016, at 17:35, Radosław Pietruszewski via swift-evolution <<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
> ><br>
> > I have to admit that I’ve also gotten used to the current system, however<br>
> > archaic ;)<br>
> ><br>
> > I’d still be happy to move to a more modern system, but it’s not as<br>
> > important to me as in the beginning.<br>
> ><br>
> > The only requirement, I think, for a lot of people, would be for the new<br>
> > system to still allow subscription and posting to go through email.<br>
> ><br>
> > Best,<br>
> > — Radek<br>
> ><br>
> > On 05 Mar 2016, at 00:37, Erica Sadun via swift-evolution <<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
> ><br>
> > Speaking as someone who tries to observe trends in discussions, does a lot<br>
> > of search through her mail archives,<br>
> > and uses gmane to capture permanent links, I've been very satisfied with<br>
> > the existing solution.<br>
> ><br>
> > I suspect that most of us happy users never get heard in this discussion,<br>
> > so I'm just putting this out there.<br>
> ><br>
> > -- Erica<br>
> ><br>
> ><br>
> > On Mar 4, 2016, at 3:34 PM, Jacob Bandes-Storch via swift-evolution <<br>
> > <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
> ><br>
> > Friendly bump:<br>
> ><br>
> > Discourse is now free for open-source projects.<br>
> ><br>
> ><br>
> > <a href="http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/" rel="noreferrer" target="_blank">http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > swift-evolution mailing list<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> > <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > swift-evolution mailing list<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> > <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > swift-evolution mailing listswift-evolution@swift.orghttps://<a href="http://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">lists.swift.org/mailman/listinfo/swift-evolution</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > swift-evolution mailing list<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> > <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > swift-evolution mailing list<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> > <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > swift-evolution mailing list<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> > <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > swift-evolution mailing list<br>
> > <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> > <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
> ><br>
> ><br>
<br>
> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div></div></div>