<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/rss/rss.xsl"?>
<rss version="2.0">
  <how_styling_rss_works style="display: none;" xml:lang="en-us" type="html">
# Styling RSS w XLS notes

XML files can include both xml-stylesheets (XSLT) and normal stylesheets (CSS).
XSLT files are transformations, and allow you to process an XML doc into an HTML doc (among other things).
In this case, it doesn't matter if we import the CSS here or via /rss/rss.xsl -- it gets applied either way.
The XSLT will output HTML for us, but the HTML content from the RSS feed (i.e., the bodies of posts) must be unescaped.
There's a special attribute (`disable-output-escaping`) which will do that.
However, we need to run some JS, too, because not every browser supports decoding html like that.

* firefox does not seem to support `disable-output-escaping="yes"`, so it requires the JS in rss.js
* chrome does support `disable-output-escaping="yes"`, so don't remove those attrs

The JS works by testing `#cometestme`, and then (if needed) looping over elements matching `[name=decodable]` and basically `el.innerHTML = el.textContent`.

Note, `disable-output-escaping="yes"` is a legacy feature from XSLT v1.0; the new way to do it is with character maps.
When I tried those, they didn't seem to work in firefox (which is when I tried the original JS).
IDK if chrome support character maps, but if it does, then that is a good update to implement. TODO I guess.

</how_styling_rss_works>
  <channel>
    <title>Philosophy work and "I need a new site"</title>
    <description type="html" xml:lang="en-us">&lt;p&gt;I&amp;#39;ve been doing a lot of work on philosophy recently.&lt;/p&gt;

&lt;p&gt;Public work takes two main forms: &lt;a href="https://www.youtube.com/watch?v=-nUP-Xqh_Dw&amp;list=PLKx6lO5RmaetREa9-jt2T-qX9XO2SD0l2"&gt;the tutorials&lt;/a&gt; are all up on youtube,
and &lt;a href="https://xertrov.github.io/fi/"&gt;a site&lt;/a&gt; where I&amp;#39;ve been publishing related work.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;I&amp;#39;ve hired &lt;a href="https://www.elliottemple.com/"&gt;Elliot Temple&lt;/a&gt; to tutor me with the ultimate goal of improving my writing.&lt;/li&gt;
&lt;li&gt;We discuss a lot of things in &lt;a href="https://www.youtube.com/watch?v=-nUP-Xqh_Dw&amp;list=PLKx6lO5RmaetREa9-jt2T-qX9XO2SD0l2"&gt;the tutorials&lt;/a&gt;; topics so far include grammar, text analysis, controlling and directing one&amp;#39;s habits, time and energy managements, epistemology (including one of Elliot&amp;#39;s most significant contributions: &lt;a href="https://www.yesornophilosophy.com/"&gt;Yes/No Philosophy&lt;/a&gt; &lt;a href="https://curi.us/1917-rejecting-gradations-of-certainty"&gt;(1)&lt;/a&gt; &lt;a href="https://curi.us/1595-rationally-resolving-conflicts-of-ideas"&gt;(2)&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;I am regularly updating &lt;a href="https://xertrov.github.io/fi/"&gt;https://xertrov.github.io/fi/&lt;/a&gt; with notes and things I&amp;#39;m writing or thinking about.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I&amp;#39;ve come to realise the current site I have is pretty bad for higher volume stuff, and jekyll is bad in general for maintaining a library of criticism.
So I&amp;#39;m thinking about potential new things to use for a site.&lt;/p&gt;

&lt;p&gt;I want to migrate everything, have a large amount of customizability WRT posting, and it should do comments well. Building stuff is okay if it&amp;#39;s feasible.&lt;/p&gt;

&lt;p&gt;Oh, and it shouldn&amp;#39;t have silly issues like jekyll does (e.g. sorting a list of pages can fail if they don&amp;#39;t all have a field, e.g. &lt;code&gt;date&lt;/code&gt;, in their frontmatter; it&amp;#39;s hard to provide a default if &lt;code&gt;date&lt;/code&gt; is missing, and even if it is present on all pages, you can&amp;#39;t sort the pages by &lt;code&gt;date&lt;/code&gt; if some of the values are &lt;code&gt;Date&lt;/code&gt;s and some are &lt;code&gt;String&lt;/code&gt;s b/c Ruby doesn&amp;#39;t know how to).&lt;/p&gt;
</description>
    <categoryTags>
    </categoryTags>
    <link>https://forum.xk.io/n/2034</link>
  </channel>
</rss>
