[snarfed]^ "The IETF Standards Process...requires at least two independent and inter-operable implementations," 😆 well yeah I guess that's a minimum bar
[fluffy]oh yeah the http://huntr.dev folks assigned a CVE after all, it was just a bug that it hadn’t been originally. And now I feel like I’ve finally made it: a piece of software I wrote is widely-used enough that people bothered to find an issue with it and open a CVE against it!
sknebelnot sure how much it'd be actually used? insert HTML snippets directly? (since its much more than just escaping, but you can make it do that too I think)
ZegnatWhat is the usecase? Inserting potential HTML as text? I think the "correct" way to do that is createTextNode, where you can safely use < and >. For almost everything else the correct way is to write out the unicode symbol and not create HTML entities.
[jamietanna]Snarfed did I remember seeing you'd recently shipped a big change to Bridgy Fed? I'm currently seeing my "notifications" feed as including a lot of other folks' content 🤔
[fluffy]I’m not a fan of using the DOM methods for generating things, though. It’s unnecessarily verbose/unwieldy and usually slower than just shoving a text string at .innerHTML or whatever.
[fluffy]yeah I just played with it on jsFiddle and it worked fine. I just don’t like the DOM manipulation methods and I’d much rather just build strings template-style.
[fluffy]I just find it really weird that there’s no standard function for converting a text string into entity-escaped or URL-encoded as another text string. Both of those come up *all the time* in webapps, and the lack of standard functionality is probably where a lot of XSS issues come from.