trying to fix

var/elfeed/db/data/93/934016bb58b29667cd0d720de1f43ce3b64a9603

@@ -0,0 +1,73 @@
+<p>
+    Just over eight months ago, I kicked off <i>This Month in Org</i> with an emphatic
+    announcement of the blog's in the form of a <a href="https://blog.tecosaur.com/tmio/2021-04-26-Welcome.html">Welcome</a> post. If you haven't
+    guessed, this is the first "blog post" I've ever written. In that <i>welcome</i> post,
+    I gave my motivation for starting the blog --- essentially to bridge a perceived
+    gap in information sources between a subscription to the Org project mailing
+    list, and nothing.
+    </p>
+
+    <p>
+    That is why I thought this blog should exist, but until now I have neglected to
+    mention what <i>I</i> want to accomplish with it. By starting <i>TMiO</i> I hoped to:
+    Engage more people with the improvements being made to Org[fn1].
+    Highlight some of the great work being done by Org[fn1] contributors.
+    Encourage more people to consider contributing to Org[fn1].
+    Foster a stronger sense of an Org[fn1] community, outside the mailing list.
+    </p>
+
+    <p>
+    Since then, I've effused about Org to the tune of around ten thousand words. We
+    started off with a fairly dry recount recent changes, which (after initial
+    feedback) has shifted slightly to try to give more context on the improvements
+    and how they may be used. In June I even went as far as to make the majority of
+    the post about pre-existing features (writing Org for LaTeX).
+    This change has been made to:
+    Try to make the blog posts a little more interesting, and less tedious.
+    Potentially introduce readers to nice features of Org they weren't aware of before.
+    </p>
+
+    <p>
+    We have now arrived at the first crucial question of this post: <i>How effective
+    has this blog been in achieving its goals?</i>
+    </p>
+
+    <p>
+    Let's start off by looking at engagement. There is no tracking on this site, and
+    I'm not even counting page views. We could read into Reddit upvotes (which
+    usually hover around 100-ish per post), but with no strong trend I'm wary of
+    reading too much into those numbers. What about engendering an interest in
+    contributing? This is even harder to consider. It is similarly difficult to
+    judge whether this blog might be helping (even if only a bit) foster a stronger
+    sense of community.
+    </p>
+
+    <p>
+    Ok, how about the second crucial question: <i>Moving forwards, what changes should
+    I make to the style of posts, if any?</i>
+    </p>
+
+    <p>
+    Hmmm, this is a prickly one too. Both of these questions suffer from the same
+    problem --- <i>I</i> can't answer them. Simply put, I need to hear from <i>you</i>. Whether it
+    be in the Reddit comments section, or by Email (<kbd>tec@</kbd> this domain), to direct
+    2022's posts I am <i>very</i> interested in hearing your thoughts on:
+    How engaging you've found this blog? (the content, the style of writing, etc.)
+    Whether this blog has influenced your feelings on the Org project and/or community?
+    Whether this blog has affected your thoughts on contributing to Org?
+    What you think this blog has done well/badly over the past year?
+    If there's anything you'd be interested in this blog doing differently in 2022?
+    </p>
+
+    <p>
+    That's all for now! Thank you for reading, and have a great new year 🙂
+    </p>
+
+    <p>
+    Footnotes
+    </p>
+
+    <p>
+    [fn1] Both the org-mode codebase, and also the ecosystem that's sprung up
+    around it
+    </p>