bear.imcreated /container (+223) "Created page with "{{stub}} '''<dfn>Container</dfn>''' is a application management tool used to bundle the application, configuration and operating system into a single self-contained bundle...."" (view diff)
bear.imcreated /kubernetes (+159) "Created page with "{{stub}} '''<dfn>Kubernetes</dfn>''' is a container orchestration environment used to manage container environments. == See Also == * https://kubernetes.io/"" (view diff)
bear.imcreated /helm (+179) "Created page with "{{stub}} '''<dfn>Helm</dfn>''' is a tool to manage the kubernetes configuration files for continuous integration and deploy within kubernetes. == See Also == * https://helm..."" (view diff)
tantek^^^ seeing people that I've never heard of post about getting #indieweb things working amongst themselves is pretty cool (and evidence of it not just being an echo chamber)
tantek.comedited /code-of-conduct (-38) "Similar Codes of Conduct - since all examples are based on IW CoC, note that explicitly instead of as exceptions" (view diff)
tantek.comedited /acquisition (+433) "add self with a couple of examples, found a 2016-02 post for a rhiaro acquisition as a good enough at least since, lowercase generic red see also" (view diff)
LoqiZegnat: [eddie] left you a message 12 hours, 23 minutes ago: my concern about using repost for “save later”. Most existing Micropub clients are just going to send the url under repost-of. But then Aperture doesn’t currently parse extra urls in posts. So my “save later” feed would end up with the repost url but no content (no title, content, etc) from the initial page I wanted to read later
Kaja_, [kevinmarks], petermolnar, yoroy_, strugee, cweiske2 and aaronpk_ joined the channel
Zegnat!tell [eddie] I actually didn’t check what current Micropub clients send for repost posts. I actually expected nested h-cits, but that expectation might have been wrong!
[manton]Repeating what I said in the Micro.blog Slack... The main issue I can think of is that the Webmention would probably create a comment in WordPress (for example) that had the same content as your original post, since it's kind of like you linking to yourself. To look good, I think the receiving code would need to display it differently.
sknebelBridgy gives the link in return to the webmention triggering it and the sending code can then handle that, but general micro.blog syndication doesn't have that
sknebelSince syndication links are a property if a post, micro.blog could make a micropub request editing the post, but I don't think there is prior art for that and it's kind of bad giving out full ability to post to the blog
sknebelAlthough I guess you have to be prepared to get webmentions from syndicated copies anyways, since you can't stop them from being sent by someone
[eddie]I think there are potentially two different issues from your original question on micro.blog [gerwitz]. I believe one issue is you want to be able to respond from your site to someone whose post url is NOT a micro.blog post URL. The other issue is you want to allow people to find your micro.blog post from your site if they want to reply to you. Does that sound accurate from your initial request on micro.blog?
[eddie]So I think there definitely must be a solution, the challenge will be thinking through how passive syndication works and the least obtrusive way to integrate that both for people adding support for it AND for not interfering with existing expected behavior.
[eddie]I think the two most obvious solutions (which have already both been mentioned above) is 1: Adding rel=“canonical” to the micro.blog page on the link to the original post. Then sending a webmention. The expectation would then be if a webmention is received with the target url being part of a rel=canonical link, then it is considered a “syndication notification”
[eddie]2: Micropub Update, this would mean micro.blog the hosted service holds an access token to your website with “update” scope. Whenever it parses a feed and creates a new post, it would send a micropub updated request adding the syndication value containing the URL of the micro.blog copy (example: https://www.w3.org/TR/micropub/#add)
[eddie]The downfall of #2 is that micro.blog holds a token that can edit any post on your entire site AND your micropub endpoint has to support both JSON posting AND the update ability, which not a lot of sites support
[eddie]It’ll be good as more IndieWeb veterans hop on throughout the day read this conversation and provide their input because the dangers we have to balance are making the bar too high for people to support versus messing with existing functionality 🙂
aaronpkthe only trick is it would be surprising to most people to get a webmention from their syndicated copy right now, so maybe it could be an opt-in feature
aaronpki've been wanting to set up an indieweb aggregator for a while now, where it crawls everyone's site listed on /irc-people and publishes a new feed from everyone's sites any time they mention indieweb keywords. so that is a sort of automatic syndication as well.
aaronpkthis mechanism of linking to the canonical with rel=canonical then sending a webmention feels appropriate for that as well, especially since rel=canonical is already a thing
ZegnatIf I get a webmention and I parse the page the webmention is from, do original post discovery, if it turns out it is my own post take action accordingly?
[eddie]That’s true, that would probably work: “in the h-entry that represents the POSSE copy, look for a link with “u-url” and “u-uid” - use that href as the original post URL.”
[eddie]Would we then say if a post matches the original post discovery algorithm, it should be considered a syndicated copy and not be used as a response?
sknebelSounds like a solution. Display would be a question (I'd probably limit them showing up to approved sources, so people can't randomly create the impression on my site that I syndicated to them
ZegnatLots of people are alreadyd filtering out likes and reposts, some even do content parsing to filter out reacji. If you are already running the mf2 parser, you can easily implement parts of the original post discovery alg
ZegnatAnd since link relations are parsed as part of an mf2 parser, for the first two checks, you can rely on the mf2 parsing you are (maybe) already doing. No need to implement your own HTML parsing there.
ZegnatLots of discussion still on going on that discovery alg though, not sure how mature it is or if tantek was thinking of converting it to a W3C Note like Post Type Discovery. But something to keep in mind :)
[eddie][manton] How does that general direction of this sound to you. Opt-in Webmentions to avoid throwing Webmentions at people that might not be ready for this kind?
[manton]Catching up on this discussion. I like where it's going. And yeah, all Micro.blog conversation links have u-url. Happy to add canonical too, but maybe it's not necessary.
aaronpkoh, i think it's when i find something from the micro.blog timeline and the URL is a canonical URL and then I can't get my reply syndicated to micro.blog because their site doesn't link to their micro.blog URL
[manton]The weird thing to understand about Micro.blog conversation links: it shows the same thread for any URL that links to the same conversation, but depending on the post ID in the URL, it changes the markup to apply h-entry/etc. to the post being linked to.
[eddie]So as far as replies to micro.blog, a cross-posted reply (original post on aaronpk’s site, reply post on my site, attempting to syndicate reply to micro.blog) is on GitHub here: https://github.com/microdotblog/issues/issues/75
[eddie]A reply to a micro.blog hosted post (original post is on a micro.blog site, reply post on my site, attempting to syndicate reply into the system) is on GitHub here: https://github.com/microdotblog/issues/issues/77
LoqiDropbox is a file hosting silo that provides js;dr URLs for the files hosted there that display just file name and a spinner unless you load some number of scripts from various domains https://indieweb.org/Dropbox
gRegorLoveHm, it is in the "Public" folder and worked before. Guess they changed/broke URLs at some point. It shows "Only you" in Dropbox now, and an option to create a link.
[eddie]So the idea is since with passive syndication you don’t have a direct response, we had to figure out how to get the syndicate-to url back into our sites
[eddie]For my site m.b is like syndication because I actually created an internal syndication target that when selected adds the post to my feed that m.b reads
[eddie]In fact, I currently store a u-syndicated property on the post with the uid= my micro.blog url. This allows until I get the actual syndicated url back per above discussion, people can see the post is syndicated to micro.blog and at the very least get to the m.b timeline (see the globe on https://eddiehinkle.com/2018/02/22/4/note/)