LoqiIt looks like we don't have a page for "some techniques people have for sanitizing reply content on their site" yet. Would you like to create it? (Or just say "some techniques people have for sanitizing reply content on their site is ____", a sentence describing the term)
Loqisanitize, specifically "sanitizing HTML", "sanitizing for (display inside) HTML", or "sanitization" is a common operation performed by any site which displays content from external sources, including user entry https://indieweb.org/sanitize
[cleverdevil][zach] it was a bit of an exploration of what’s possible. I’d like to get back to it at some point potentially, but I’m sticking with Known for now.
[miklb]anyone around by chance that uses Gulp/node? I’m trying to run a task against a file icons_base and want to save it as icons and not finding the right `pipe(gulp.dest()` path
[KevinMarks]about once a month someone tries to embed script in the SVGs, and then emails me excitedly because it executes in their client before uploading, because I do that on purpose to deter them.
[grantcodes]Yeah that's definitely not the goal of my tools. My stuff is good for a personal site, but editing it is not a beginner level. But webmentions are long long way from writing your first html
omz13My attempt to roll my own server are going well... I now have indieauth and micropub working (passing most of the micropub.rocks tests), and can create posts on my test server from quill and teacup :-)
[tantek]!tell Jacky a bit delayed, re: how to display reply content from others on your site, we've been collecting various how-tos, exampes, techniques here: https://indieweb.org/comments
[tantek]that being said, definitely interested in making it clearer. that whole larger section started as me braindumping all the thoughts I had to go through, details I had to figure out, to get POSSEing to Twitter working on my site back in 2010!
[grantcodes]I personally would find it easier to follow if the specific methods (eg cassis functions) were moved to a separate section. So it became more about what the requirements are, and then a potential way to implement it after.
[tantek]tinbox << simplify [[Twitter#POSSE_Notes_to_Twitter]] by: <br>1. removing use of [[permashortcitation]] (and only using [[permashortlinks]]) and <br>2. extract inline use of CASSIS functions in POSSE explanations, and instead provide them as specific techniques after the full prose explanations.
[cleverdevil]Thinking about my new /following page... the current implementation has each feed as a `u-follow-of` with an `http` or `https` `href`... considering changing these to `feed://` URLs so that when people click/tap on the links, they can be opened in their reader... but can’t decide if this is somehow incorrect.
[cleverdevil]That said, if the average person taps/clicks on a link on the page, their browser is highly likely to either display a mess of JSON or XML, or to download the linked feed.
[cleverdevil]I think the default on most OSes for handling unknown link types is to direct the user to some app store or something where they can find an app to handle those link types.
[grantcodes]Maybe have a link to the site root for humans and the feed URL for machines? Although the root isn't always guaranteed to be what you're actually following
LoqiA web action is the interface and user experience of taking a specific discrete action, across the web, from one site to another site or application https://indieweb.org/webactions
[grantcodes]If you want the feed link visible for people who like that I would make the name of the feed link to the root URL and add a little RSS icon to the feed. (Or don't if it is an mf2 feed)
[cleverdevil]I think the way I’ll do it is to keep the structure of the page, with the links being href to the feed, but I’ll add an onclick handler to preview it.
Loqi[schmarty]: [grantcodes] left you a message 2 days, 8 hours ago: I was just working on some micropub client stuff and realised it will be pretty close to what you described at https://martymcgui.re/2019/06/30/232547/ I'm starting lower level though, with a set of react components that automatically build out mf2 properties. But could be extended to include the sort of interfaces you mentioned