2020-01-20 How to deal with weird stuff in feed aggregation

Planet Jupiter is entering the phase where all the features I want have been implemented and now I’m only dealing with weird stuff and workarounds. I’ve seen blog posts containing double escaped HTML. I unescape the first layer and turn the post to plain text (adding pilcrow signs for paragraph breaks) and so on. But if somebody adds double escaped HTML, that still leaves escaped HTML in the output. I’m guessing this is a bug in their Wordpress plugins responsible for indie web support or something. But what am I going to do: tell them to fix their setup? Or add a workaround that simply tries to unscape HTML a second time? Guess what I’m doing...

I had to consider other things as well: what about elements that aren’t being rendered by browser? They also shouldn’t be “rendered” by the feed aggregator. One feed, for example, contains a style element. The style element contains CSS instructions ­– this should not end up in the page excerpt. Anything else I need to remove from the excerpt?

Tags:

Comments


Please make sure you contribute only your own work, or work licensed under the GNU Free Documentation License. Note: in order to facilitate peer review and fight vandalism, we will store your IP number for a number of days. See Privacy Policy for more information. See Info for text formatting rules. You can edit the comment page if you need to fix typos. You can subscribe to new comments by email without leaving a comment.

To save this page you must answer this question:

Please say HELLO.