Yeah, sorry, we get some really mangled HTML from the RSS feed that Rohin registered, that’s a bit of a pain to clean up, so we’ve been doing it manually for a bit. My guess is I will get around to automating it, but it’s not super trivial, since the HTML we get has a lot of table-layout stuff that sometimes is relevant to the content, and sometimes isn’t, and so I would have to experiment for a while to find the right sanitization rules to make everything work nicely without human intervention.
I forget if I mentioned this before, but all of this HTML is generated by a script with a much more structured input, which you can see here. Plausibly we should just add another output mode to the script that can be easily imported into LessWrong? (Happy to share you on the spreadsheet from which the input data comes if that would help.)
Currently this is fixed manually for each crosspost by converting it to draft-js and then deleting some extra stuff. I’m not sure how high a priority it is to make that automatic.
Is this page completely unreadable for anyone else? https://imgur.com/a/yfEA72R
Yeah, sorry, we get some really mangled HTML from the RSS feed that Rohin registered, that’s a bit of a pain to clean up, so we’ve been doing it manually for a bit. My guess is I will get around to automating it, but it’s not super trivial, since the HTML we get has a lot of table-layout stuff that sometimes is relevant to the content, and sometimes isn’t, and so I would have to experiment for a while to find the right sanitization rules to make everything work nicely without human intervention.
I forget if I mentioned this before, but all of this HTML is generated by a script with a much more structured input, which you can see here. Plausibly we should just add another output mode to the script that can be easily imported into LessWrong? (Happy to share you on the spreadsheet from which the input data comes if that would help.)
Yeah, that might end up being easier. I might look at the code and make a PR for a minimalist HTML template.
Yep, clicking “View this email in browser” allowed me to read it but obviously would be better to have it fixed here as well.
Currently this is fixed manually for each crosspost by converting it to draft-js and then deleting some extra stuff. I’m not sure how high a priority it is to make that automatic.