Post AdeGswPFM5DBHqip4y by Hyolobrika@social.fbxl.net
 (DIR) More posts by Hyolobrika@social.fbxl.net
 (DIR) Post #AdeGswPFM5DBHqip4y by Hyolobrika@social.fbxl.net
       2024-01-08T21:32:21.282204Z
       
       0 likes, 0 repeats
       
       @alex @sj_zero Not sure if this is a problem in the frontend (Soapbox) or the backend
       
 (DIR) Post #AdeHFY6FtL42YwcS7k by SirVo@noagendasocial.com
       2024-01-08T21:36:25Z
       
       0 likes, 0 repeats
       
       @Hyolobrika @alex @sj_zero inb4 "open a ticket"
       
 (DIR) Post #AdeHRl51SQsGIKreng by Hyolobrika@social.fbxl.net
       2024-01-08T21:38:39.518950Z
       
       0 likes, 0 repeats
       
       Should I open the ticket on the Soapbox repo or the Rebased one (assuming the backend here is Rebased) though?
       
 (DIR) Post #AdeUT8KLfmXi7UymEy by sj_zero@social.fbxl.net
       2024-01-08T23:17:59.454420Z
       
       1 likes, 0 repeats
       
       The issue may not be with soapbox/rebased but with your rss reader. I just loaded my rss feed into nextcloud news and it loaded up. (It could be in part due to the really long titles) I'll try a couple other rss readers.
       
 (DIR) Post #AdeUTAxPtUywHFH0Pg by sj_zero@social.fbxl.net
       2024-01-08T23:57:06.068809Z
       
       0 likes, 0 repeats
       
       I tested with rss.app, rssguard, quiterss, nextcloud news, feeder, Read You, spaRSS DecSync, and Nunti.Only Read You showed the same error message, but some of the feeders were better with the feed than others for sure. RSS guard portable failed entirely on a "protocol error" whatever that means.