#[KevinMarks]For svgshare.com I parse with html5lib and remove all script tags (I also only use img on the site, except for the upload dialogue, so anyone who uploads a script exploit only hacks themselves)
#btremedited /svg (+1656) "/* Example */ Adds second example of svg with h-card markup" (view diff)
gRegor, gRegorLove_, [ender]1, [snarfed]2, [manton]1, [tantek]1, IWSlackGateway1, [KevinMarks]1, [schmarty]1, strugee-, Zegnet, emery, btrem, angelo and porquilho joined the channel
#[jacky]also would that mean that parsers that support embedded SVGs _should_ parse it under SVGTiny? I know there's no recommendation on sanitizing HTML in the mf spec
btrem joined the channel
#[tantek]jacky, that's a very good suggestion if I understand you correctly, to make that explicit in the mf2 parsing spec ("[mf2] parsers that support embedded SVGs _should_ parse it under SVGTiny") — can you file an issue for that? https://github.com/microformats/microformats2-parsing/issues/
#btremAre there rules for parsing html that restrict elements to reduce security vulnerabilities?
#Loqi[aaronpk] you can put all sorts of interesting things in an SVG, things that I would be worried about republishing in a reader
#btremIs this something specified by mf2 parsing rules? Or something that consumers do to protect themselves?
#aaronpksomething that consumers do, long standing practice even before mf2 "html sanitization"
#btremThen does it make sense to specify that svg be parsed in a special way, with SVGTiny?
#btremISTM that it is up to consumers to take precautions. So maybe parsing rules should provide a general warning about republishing e.g. `h-entry`, with suggestions on how to reduce the dangers.
[hollie] and ur5us joined the channel
#[tantek]the idea is that parsing with/for SVGTiny is at least *a* defined method for SVG sanitization, whereas HTML sanitization is still very much custom design/code.
#btremre: my Firefox comment: the image was disappearing in a specific set of markup and css. Probably not a bug, since I saw the same effect in Firefox and Chromium. In any case, it was completely unrelated to `u-logo`.