jonnybarnes, [tw2113], KartikPrabhu, callMeBaby, JK_na, fredcy_, jalcine[m], Salt[m], samwilson, smacko[m], jamietanna[m], hirusi[m], nekr0z, Rixon, JameySharp[m], gRegorLove, gxt and prologic joined the channel; prologic left the channel
#prologicThanks for all the help guys! Especially aaronpk ! Its official twtxt.net (and all twt.social pods) now support webmentions and indieweb microformats! 🎉
gxt, KartikPrabhu, swentel, [jeremycherfas], nickodd, loicm, dckc, mblaney, moppy, JameySharp[m], gRegorLove, samwilson, jamietanna[m], smacko[m], nekr0z, fredcy_, jalcine[m], hirusi[m], JK_na, Rixon and Salt[m] joined the channel; mblaney left the channel
jonnybarnes, [spieper], jeremych_, [jgmac1106] and justache joined the channel
#aaronpkprologic: awesome! does my comment show up now or should i re-send it?
#prologicwell umm you should resend it; however "comment show up" I'm not sure how this works per se?
#prologicBut any webmention inbound should be handled and posted to thw internal twtxt feed
dckc and nickodd joined the channel
#prologicaaronpk in fact I'm actually curious about the whole "user experience" of web mentions in the first place
#prologicwhen you have time maybe you can walk me through how some non-technical person might interact with something via (unbeknown to them) webmention
#prologicalso really interested to see how far we can take twtxt <-> webmention interop
#GWGI love this enhancement to my IRC client that shows [schmarty] photos when his website is cited.
jonnybarnes, prologic and [tw2113] joined the channel
#@TrevorFSmith↩️ I agree with that description of what happened. That said, I think the core problem today is that RSS/Atom alone is no longer enough for us. We want to read, like, and comment without bouncing from site to site. The indieweb community uses webmentions and webactions for this. (twitter.com/_/status/1295761746318090241)
gRegorLove, [jgmac1106], jonnybarnes, zenen, vika_nezrimaya and [chrisaldrich] joined the channel
#jackyaaronpk: the 'seeing' if it worked is something I -kinda- want to push into webmention status pages tbh
#[tantek]that's also a good practice. there's two specific examples that may help: morning pages, and evening logs though I realize this is more of a #indieweb general chat (we could make it dev-specific if you like, up to you)
jonnybarnes, swentel, KartikPrabhu and [jgmac1106] joined the channel
#lahackerhey guys is there a nook on the wiki that might discuss webmentions on an updating article (ie. wiki article) -- eg. continuing to show someone's like to your article even after it's been substantially edited -- is there a way to backfeed an explicit "version" bump? -- a "version" property? or should this case be covered by the replying party offering some kind of revocation on their end?
themaxdavitt, peterrother, vika_nezrimaya, jonnybarnes and [chrisaldrich] joined the channel
#lahacker[snarfed]: this is only for two parties -- thought salmention was for a third party swimming up to the first (eg. threaded comments)?
#lahackeri'm talking -- an article or even note changes drastically and my original comment/like/etc. no longer applies
#lahackerspecifically in the context of a resource that has multiple version URLs
#lahackerthe replying party should be able to reply to /IndieWeb (the actual article) in a general sense or a specific version /IndieWeb/versions/3 -- but is there some existing mechanism so suggest that the original reply be repointed to the versioned page it originally pointed to instead of the new one
#[snarfed]salmentions are definitely both directions, so a replying party could use them to trigger any behavior they want
#[snarfed]versions will be site-specific, and different, so i’d hesitate trying to do anything based on versions specifically
#[snarfed]a start would just be reacting at all to a salmention from the original post. afaik we don’t have any example of that in the wild yet
[tantek] and deathrow1 joined the channel
#lahackerhmm rel=canonical is an idea -- just always have a rel=canonical pointing to /IndieWeb/versions/>{n} on /IndieWeb and the replying party can offer the choice of which to reply to
#lahacker[snarfed]: correct me if i'm wrong but salmention only kicks in when there's a third party, no? in this case i'm talking about two parties only
#lahackerconsider a book where several commentors complain about a confusing chapter, the chapter is rewritten, their comments should somehow point to the old version
#lahackershould i just handle that all on my end (author side)
#lahackersomeone could follow through from their comment and find no said confusion in the now updated chapter
#lahackerthis is a common problem with changing titles of articles and what not on reddit/hackernews type sites
#[snarfed]we have something somewhere about sending wms from an original post to responses when the original post changes. maybe salmentions, maybe elsewhere
#[tantek]I think we brainstormed them both directions, however I believe there were concerns that could result in loops
#[tantek]the primary use-case of salmentions is upstream AFAIK, though cases like "A: C commented on a post B that you were tagged in" are almost sideways
#lahackerso i think i got it right the first time -- imagine the case of the replying party's "like" permalink -- the UX of this whole discussion kind of revolves around what my "In reply to.." aka reply-context shows
#lahackeri've been approaching the concept of an "edit" from multiple angles trying to tack it down -- tantek mentioned once "just resent a webmention"
#lahackerbut in this case i guess i'm just wondering how others or if no other prior art ideas as to how to attack this level of granularity
#lahackeri'll start with just noting the version the article/page/book was at when the comment was received (if they only point to the naked /IndieWeb)
#lahackerchronological order will be simple enough.. another ordering possibly not
#[tantek]lahacker, might help to have a step by step list of the user actions taken and expected user-visible result
gRegorLove joined the channel; prologic left the channel