<?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>New Site (Blog/Forum)</title>
    <description type="html" xml:lang="en-us">&lt;p&gt;If you&amp;#39;ve visited my site before, you might notice it&amp;#39;s different now. It&amp;#39;s a complete forum -- the blog part is done through permissions.&lt;/p&gt;

&lt;p&gt;The structure is a tree and based on discussion at &lt;a href="https://curi.us/2396-new-community-website-features-and-tech"&gt;https://curi.us/2396-new-community-website-features-and-tech&lt;/a&gt;. It&amp;#39;s highly customizable and supports things like CNAMEs for sub-forums (which can be ~disconnected from the main forum tree via permissions).&lt;/p&gt;

&lt;p&gt;Every node in the tree supports RSS feeds. Hit the RSS button or add &lt;code&gt;.feed&lt;/code&gt; to the end of a URL to get the feed.&lt;/p&gt;

&lt;p&gt;I&amp;#39;ve made an &lt;em&gt;Open Discussion&lt;/em&gt; node at &lt;a href="/n/88"&gt;/n/88&lt;/a&gt; -- you can post whatever there.&lt;/p&gt;

&lt;p&gt;Nodes can be viewed as any other type of node; atm there are 3 types: &lt;code&gt;root&lt;/code&gt;, &lt;code&gt;index&lt;/code&gt;, and &lt;code&gt;topic&lt;/code&gt;. Add &lt;code&gt;/as:&amp;lt;view&amp;gt;&lt;/code&gt; to the end of a node&amp;#39;s URL to view it via that method, e.g. &lt;code&gt;https://xk.io/n/0/as:topic&lt;/code&gt;. The main forum-nodes have descriptions but -- atm -- those aren&amp;#39;t shown except via view-as or the RSS feeds.&lt;/p&gt;
</description>
    <categoryTags>
    </categoryTags>
    <link>https://forum.xk.io/n/10002</link>
  </channel>
</rss>
