#GWGmiklb_: That is why I wanted some testing this time before I moved on. So I asked you and chrisaldrich to try it and see if there was any feedback.
#GWGmiklb_: Also, if you are interested in the parser, open up your development console and retrieve a URL. It will show you the information coming from the backend.
cweiske, loicm, KartikPrabhu, jonnybarnes and arush joined the channel
#petermolnarre GWG: embed: I did look at it, in order to figure out how to disable it
#petermolnarwp ships with oembed for the blog itself, providing a json with some js in the response, and when I think about embedding remote json in my site via iframe I get jumpy
#cweiskehow is that different from showing indieweb remote comments?
#petermolnarI don't do that either, but I do store them: pull content, parse with pandoc to markdown, store in markdown, display with pandoc to html5
#petermolnarif anything manages to slip through that, I'll give them a cookie
#GWGpetermolnar, I wanted to consider using a similar design for my reply context.
#petermolnarcweiske no, with embeds, you can't, that's the point: embeds are copyright-safe things because you don't copy anything, just show the actual, remote thing
#petermolnarwhat I do can hit copyright walls, but since I'm not showing it, only storing it for potential future use, meh.
#petermolnarI guess if I only show quotes as [...] blabla [...] + url, as WordPress did for pingbacks, it shouldn't hit any copyright issues
matigo, hacker, KartikPrabhu, miklb__, [eddie] and [chrisaldrich] joined the channel
#loqi.mecreated /splatter (+137) "prompted by ben_thatmustbeme and dfn added by ben_thatmustbeme" (view diff)