[API] Adding HTML parsed fields to comment/post body and profile/image description

If you don’t write code that interacts with the API, this topic is not intended for you.
 
Right now, we serve only the Philomena/Derpibooru markup strings for:
 
comment.body  
post.body  
profile.description  
image.description
 
I was in the process of making the API also return:
 
comment.body_html  
post.body_html  
profile.description_html  
image.description_html
 
The issue is while 99% of stuff works great, links of the form \>\>2322234p return a huge div with data the site relies on for client side filtering.
 
Ex:  
`”description”: “>>14p”

“description_html”: “<div class=\“image-show-container\” data-aspect-ratio=\“1.2333333333333334\” data-comment-count=\“1\” data-created-at=\“2020-04-07T04:13:47\” data-downvotes=\“0\” data-faves=\“0\” data-height=\“3000\” data-image-id=\“14\” data-image-tag-aliases=\“safe, artist needed, oc\” data-image-tags=\”[1,142,144]\” data-score=\“0\” data-size=\“medium\” data-source-url=\”\” data-upvotes=\“0\” data-uris=\”{"full":"/img/view/2020/4/7/14.png","large":"/img/2020/4/7/14/large.png","medium":"/img/2020/4/7/14/medium.png","small":"/img/2020/4/7/14/small.png","tall":"/img/2020/4/7/14/tall.png","thumb":"/img/2020/4/7/14/thumb.png","thumb_small":"/img/2020/4/7/14/thumb_small.png","thumb_tiny":"/img/2020/4/7/14/thumb_tiny.png"}\” data-width=\“3700\”><div class=\“block block–fixed block–warning block–no-margin image-filtered hidden\”><strong><a data-click-unfilter=\“14\” href=\”#\”>This image is blocked by your current filter - click here to display it anyway</a></strong><p><img data-click-unfilter=\“14\” height=\“250\” src=\”/images/tagblocked.svg\” width=\“250\”></p><span class=\“filter-explanation\”></span> <a class=\“filter-link\” href=\”/filters/1\”>your current filter</a>. </div><div class=\“image-show hidden\”><a href=\”/images/14\” title=\“Size: 3700x3000 | Tagged: safe, artist needed, oc\”><span class=\“imgspoiler\”><picture data-image-id=\“14\”><img src=\”/img/2020/4/7/14/medium.png\”></picture></span></a></div></div>”   There are multiple ways this could be handled:   We could just let it go. Your applications would probably want to just cut that out/ignore it.   We could cut it out on our end. Your application would not get the huge bloat ofdiv` content.  
We could attempt to parse it for you (if a valid filter is provided).  
Or we are open to taking suggestions.
 
What are your thoughts on this?
 
I have made a git issue over here or you can leave comments/ideas below.

Speaking personally: I’m making a mobile app using a cross-platform framework. Its support for HTML markup is limited enough to basically be nonexistent. Conceivably, converting HTML into something platform-displayable could be easier than writing my own parser for Derpi’s markup, but probably not by much.
 
tl;dr: the HTML return values don’t help my use case, so I’ll cast my vote in favor of doing whatever is easiest on your end.

Agh. Wasn’t logged in. Previous post is mine.

@pingzing  
I develop on Discord myself, and while I have a HTML -> Markdown converter, parsing derpi’s markup was proving to increasingly be a problem—hence me wanting to fix things a little.
 
The eventual plan (I believe) is to move derpi’s markup system to Markdown, probably with 1 or two extra additions (like >> and its derivatives). But even then, outputting HTML is not a problem (literally just calling the lexer on the data already there).
 
Thanks for the reply!