RSS feed rendering issue in Slack #693

Activity

1. puredanger commented on Jun 3, 2024

   

   puredanger

   on Jun 3, 2024

   Last edited by puredanger

   Member

   More actions

   The Rust example is an Atom feed which is a bit different, but the AWS feed is RSS with entity encoded html and looks pretty much the same to me from a formatting perspective as the Clojure news feed (they also include the full post). How do those compare in the Slack reader?

   The FTL template for the current feed looks like this:

   <?xml version="1.0" encoding="UTF-8"?>
   <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
     <channel>
       <title>Clojure News</title>
       <link>${config.site_host}</link>
       <atom:link href="${config.site_host}/${config.feed_file}" rel="self" type="application/rss+xml" />
       <description>Clojure News</description>
       <language>en-gb</language>
       <pubDate>${published_date?string("EEE, d MMM yyyy HH:mm:ss Z")}</pubDate>
       <lastBuildDate>${published_date?string("EEE, d MMM yyyy HH:mm:ss Z")}</lastBuildDate>
       <#list published_posts as post>
       <item>
         <title><#escape x as x?xml>${post.title}</#escape></title>
         <link>${config.site_host}/${post.uri}</link>
         <pubDate>${post.date?string("EEE, d MMM yyyy HH:mm:ss Z")}</pubDate>
         <guid isPermaLink="false">${post.uri}</guid>
         	<description>
   	<#escape x as x?xml>	
   	${post.body}
   	</#escape>
   	</description>
       </item>
       </#list>
   
     </channel> 
   </rss>
   
2. siadat commented on Jun 5, 2024

   

   siadat

   on Jun 5, 2024

   Author

   More actions

   Thanks for looking into it! I created the #testing-rss-feed channel in Clojerians and added those feeds there to test how they look like. Feel free to add/remove feeds there using the /feed command.

   Here's how they look like:

   
3. siadat commented on Jun 5, 2024

   

   siadat

   on Jun 5, 2024

   Last edited by siadat

   Author

   More actions

   Afaict, Slack displays a substring of <description> and truncates the rest of it, potentially leaving an incomplete HTML tag e.g. <di.

   One thing we could do is to substring ${post.body} in <description> ourselves before it is rendered to HTML. Assuming post.body is not rendered already:

           <description>
           <#escape x as x?xml>
   -       ${post.body}
   +       ${post.body[0..*100]}
           </#escape>
           </description>
   +
   +       <content:encoded>
   +       <#escape x as x?xml>
   +       ${post.body}
   +       </#escape>
   +       </content:encoded>
4. siadat commented on Jun 5, 2024

   

   siadat

   on Jun 5, 2024

   Author

   More actions

   But post.body might already be rendered to HTML so it will probably not work 🥲

   Also, it doesn't solve the other problem of the extra whitespace between the lines.
5. puredanger

   added

   backlog

   on May 1, 2025