Despite having equivalent features, I&#x27;d go out on a limb and say a blog and a bug tracker have very different UI requirements, so it&#x27;s only appropriate to use one as the other insofar as you don&#x27;t care about user experience.  As an example, I read that post and had no idea it was part of a blog until I saw the repo path was &quot;&#x2F;blog&quot; and figured out that they were trying to be cute.  I then clicked on the root of the repo to see the root of the blog and saw the explanation and a link to &#x2F;issues to &quot;read&quot; the &quot;blog&quot;.  I was then presented with a list of issues that was only the post I had just read, and at that point I said oh fuck it I don&#x27;t care to figure out whether there are more &quot;blog posts&quot; if I remove the &quot;status:open&quot; search criterion and I closed the fucking window and then saw your comment explaining that an issue tracker has all the features a blog needs.<p>Ok.