<html><body><div><pre style="white-space: pre-wrap;" data-mce-style="white-space: pre-wrap;">on Thu Jan 26 2017, Dave Abrahams <swift-evolution at swift.org> wrote:<br>> on Thu Jan 26 2017, Nate Cook <<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" data-mce-href="https://lists.swift.org/mailman/listinfo/swift-evolution">swift-evolution at swift.org</a>> wrote:
>
>><i> ✋
</i>>><i>
</i>>><i> I forged the mighty, turgid rivers of rubyenv, hand-tweaked gem
</i>>><i> dependencies, and sed-cleaned mbox files to try this out—you can see
</i>>><i> the results of an import (using one or two day old data) at this
</i>>><i> address:
</i>>><i> <a href="http://discourse.natecook.com/" data-mce-href="http://discourse.natecook.com/">http://discourse.natecook.com/</a>
</i>>><i>
</i>>><i> It looks like the threads were handled properly, though they bear some
</i>>><i> obvious marks of their mailing list origins. Users can actually claim
</i>>><i> their accounts if they do a password reset. However:
</i>>><i> - it's hooked up to a trial SendGrid account, which will top out at 100 emails/day
</i>>><i> - I should probably delete this soon so Google doesn't think it's the real deal
</i>>
>It's a shame that it has no facility for hiding long quotations. Trying
>to find the actual content in this thread is pretty awful:
><a href="http://discourse.natecook.com/t/strings-in-swift-4/2980/13" data-mce-href="http://discourse.natecook.com/t/strings-in-swift-4/2980/13">http://discourse.natecook.com/t/strings-in-swift-4/2980/13</a>
<br>A few months ago I wrote a tool in Elixir to better browse the mailing list archives by thread. Demo is here (forgive the frontend dev skills):<br><br>https://swift-archive-staging.herokuapp.com<br><br>As part of that, I added support for converting posts to markdown and clipping long quotations (though sadly that has not yet been deployed to the above link). It's quite a bit of work, but ultimately it probably makes sense to clean up the data before we pull it in to Discourse (prune long quotations, convert to markdown, reparent orphan replies (such as this one), etc). If we do decide to move to Discourse (which I'd strongly support), I'd gladly put in the effort to clean up threads before we import them.
<br>-Tyler</pre></div></body></html>