Best practices document

[the8472]

Would it make sense to have an informal document, probably not even a BEP, documenting best implmentation practices so that people don't have to rediscover the wheel? Even linking to blog posts, issue trackers and implementations may be appropriate for some points.

The discussion about sanitizing path names in for BTv2 or this unicode LTR confusion thing.

Many questions on stack overflow or IRC also arise from the specs leaving a lot of things up to the implementations.

[ssiloti]

I agree it would be nice to collect all of the arcane knowledge about implementing bittorrent into a coherent document. At the moment I can't say I would commit much time to such an effort though. PRs would be welcome of course.

[the8472]

I think for a start a list of links and bullet points in a markdown document and a "just accept PRs" strategy would be good enough. bt.org is hosted as github pages and renders MD automatically, right?

[ssiloti]

Rendering HTML from reStructuredText is a manual process but I can take care of that. Otherwise everything updates automatically from the github repo.