#tantekKartikPrabhu: why would checking original-post-discovery be any different than checking u-syndication ?
#kylewmwell many people don't include perma(short)cite/links in their tweets, not to mention indie-reposts or indie-likes where it isn't possible
#KartikPrabhutantek: checking u-syndication is easier since you have permalink of the post that webmentioned and get mf2 from that. For original-post-discovery there is a long-ish non-trivial algorithm to follow
#tantekOk I have a hypothetical reason - untested - which comes to the same conclusion as you KartikPrabhu re: having the u-syndication already there when a webmention receiver retrieves the original: POSSE reply threading
#KartikPrabhuparticularly if for some reason Bridgy backfeed hasn't yet sent the backfeed
#KartikPrabhuyou can still use u-syndication to POSSE a reply to a reply
#tantekwhen indie A replies to indie B and sends B a webmention, when B goes to reply to A, if B's copy of A's post already knows the Ap POSSE copy, then B can immediately reply back both to A, and POSSE reply thread their Bp POSSE copy to Ap.
#gRegorLovekylewm has done that on some replies, I've noticed.
#tantekit makes it easier to do the right thing, and connect all the replies
#KartikPrabhupossibly and link to it from POSSE or some page that has this deduping of comments
tilgovi joined the channel
#tantek.comedited /Webmention (+189) "move rel webmention from brainstorming to resolved, id up near discovery, webmention as one of many space separated values" (view diff)
scoates, nloadholtes and KartikPrabhu joined the channel
#tantek.comedited /Webmention (+1148) "/* How does this solve the spam problem */ note vouch. POSSE or webmention first? Thanks to kylewm and kartikprabhu for reasons." (view diff)
#tantek.comedited /POSSE (+229) "/* FAQ */ POSSE or Send Webmentions First - summary answer an link to longer answer on webmentions page" (view diff)
callovarne joined the channel
#tanteknice post: http://stream.boffosocko.com/2015/i-like-what-youve-done-with-the-final-product-and - in particular: "some of their infrastructure allows one to easily make posts on one's own page which then act as replies on another's site. This is particularly interesting from the viewpoint of teaching wherein students and professors can interact with each other, but still have/own all of their individual work."
#tantek.comedited /Twitter (+587) "/* POSSE abbr note to twitter */ include kartikprabhu's suggestion about More: along with some implications of attempting that approach" (view diff)
#tantekKartikPrabhu: ok I captured your "More (at):" suggestion as it seems reasonable
#KartikPrabhusince when did Twitter start putting "descriptions" for "Trends"
#KartikPrabhuvery annoying and cluttering the Twitter page
#tantekKartikPrabhu: that's very odd - you're POSSEing a like kind of like a quote?
#tantek.comedited /Twitter (+260) "/* POSSE abbr note to twitter */ note KartikPrabhu's like example that has a quotation, and then he POSSEd manually as a note to Twitter" (view diff)
LCyrin joined the channel
#Loqislack/snarfed: KartikPrabhu out of curiosity, would you use bridgy publish for your current manual posses if you could customize the ellipsizing and link text?
KartikPrabhu joined the channel
#KartikPrabhutantek: err yes. didn't know how else to do it since there is no Twitter copy
#KartikPrabhusnarfed: I use Bridgy Publish for most cases, except when heavy editing of the text is needed to make it read nicer on Twitter
#tantekKartikPrabhu: well it's odd that you're liking and quoting at the same time
#tantekyou've almost written your own note post there - since the actual quote is not continuous in the IRC channel archive you link to
#KartikPrabhutrue. I also add my own text to likes sometimes to keep note of why I like it
jciv joined the channel
#tantekKartikPrabhu: that sounds more like a bookmark
snarfed, n8fr8, callovarne, KevinMarks_, KevinMarks and j12t_ joined the channel
#tantek.comedited /Webmention (+105) "/* POSSE or Send Webmentions First */ add citation to IRC discussion for conclusions" (view diff)
#tantekaaronpk: perhaps not quite as productive a wiki day as yesterday, yet answering that FAQ I think is useful for helping implementations that do POSSE & send webmentions
#GWGBut, either way, we'll see what I can do over the course of the summer.
#GWGTo get Bridgy Publish working, I need to fix my theme, because Bridgy Publish was picking it up incorrectly. Which means I'm marking up incorrectly.
#tantekGWG - go get your private test account - that's an easy thing you can take care of in a few minutes
KevinMarks, snarfed, KevinMarks_, Jihaisse, glennjones, fkooman and tantek joined the channel
#acegiakSo here's an interesting observation: Since I've started consciously making an effort to take and post selfies occasionally people reply to those posts with compliments. The ability to "like" that reply post is a really nice subtle way of sayinga polite "thanks" without having to up it into a foofaraw of an actual third reply post
KartikPrabhu, craftycorvid, nloadholtes, tmro, fkooman, eschnou and davidpeach joined the channel
#@deewuIt's so self-congratulatory. Lookit you, leaving the walled gardens and content silos! You see the light and goodness of the #indieweb! (twitter.com/_/status/604282724304732160)
#tommorris"C'est á Portland, repère de hipsters américains au Nord-Ouest des Etat-Unis que le projet Indie Web naît en 2011." bwahaha.
#Loqitommorris: KartikPrabhu left you a message 3 days, 10 hours ago: it seems my security level has gone down to B because of the whole logjam thing. But I don't understand if that is my erroe, my cert providers error or the hosting companies error! The resolution is so un-understandable! ref: https://weakdh.org/http://indiewebcamp.com/irc/2015-05-25/line/1432612996420
#tommorrisKartikPrabhu: hey, it's nobody's error - you can generate new DH keypairs from the certificate.
#Guest99613yeah I just went through generating new moduli files on every machine I SSH into. it was less than ideal.
#aaronpkbasically i took the parsed microformats json of the edit example we made, and trimmed out anything that could be implied by the micropub endpoint
#aaronpktechnically the "properties" object isn't needed, but that makes it match the parsed JSON
#tantekaaronpk: any chance we can develop the form encoded version first? simpler design first? and then go all trendy JSON?
#aaronpkkiiinda... except once you require nested properties, form-encoding becomes ugly/hacky
#tantekI like this design process for such protocols: HTML+mf -> form encoded -> trendy JSON
#tantekthat way we can swap out the trendy next year for whatever
#aaronpkwe don't need nesting for *creating* things because we can just assume every property specified in the create is part of the tthing being created
#tantekaaronpk I'm convinced we can figure out flat & simple for form encoded
#aaronpkbut for editing things, we first need to specify the URL of the thing being edited, and then also need to specify the changes
#aaronpkthat's what led to the "mp-" prefix spec'd out earlier
#bretaaronpk: how do we handle properties that are deleted?
#aaronpkthat would look like add[category]=indieweb in form-encoding
#aaronpkexcept that form-encoding itself doesn't have the concept of nested properties, but most parsers have implemented it with [] despite it not being in the spec
#aaronpkand because it's not in the spec, you get the difference between languages of how they handle things like foo=1&foo=2 vs foo[]=1&foo[]=2
#tantekexample: the term "collection" is often used in various Social Web WG discussions, and when you use a specific term "list", then you incite debates about "list" vs "collection" etc.
#bretaaronpk: sorry was pulled away from irc. no, node's http server does not automatically decode the body, and even express requires that you set that middle ware up as of today. requires libs to do the encoding and decoding. using the JSON.stringify or JSON.parse on the body of the req or res is easier in this case. but doing form encoded isnt hard either,
#bretputs it in the funny looking form encoded on wire encoding until whatever on the other side turns it back into whatever native object the language uses
#tantekbret - you can escape the gridlock by braindumping them to your User: page Itches section
#tantekthe reason braindumping them there (externalizing them from your brain) works, is because it's a distinctly differnt cognitive task to recognize/discover/document itches, than it is to prioritize them
#tantekso by default just braindump them to the end of your existing list, until no more come to mind
#aaronpki've been using Wunderlist for that recently. although I think I need to make a separate list for "my site" vs "indieweb things"
#tantekthen take a mental break (walk, drink, eat, etc.) and come back and look at the whole list and see what "hits you"
#tantekanyone here intersted in an early Octoberish IWC Austin?
#tantekI ask because there's an AEA (An Event Apart) Austin early October, and it may make sense logistically and in terms of crossover to have an IWC before/after
#rhiaroooh my favourite couchsurfer so far is in austin!
#bretone insight i had... whats the alternative to virtualdom (eg, representing your dom as a js object)? not having one and tying all logic to the real dom api
#bretvirtualdom gives you access to your dom, but with a different api
#bearthe reason they use virtualdom vs native is to control refresh/updates
#bearwhen you touch the real dom you cannot control when updates happen
#KartikPrabhuI could for starters just duplicate the hreview backcompat to hreview-aggregate but both of those are lacking in the recommended "item" property translation
#kylewmKartikPrabhu: no it doesn't :/ and the transformation for 'fn' looks totally wrong
#kylewmor represent it generally like {'item': {'vcard': ['p-item', 'h-card'], etc. }}
#kylewmKartikPrabhu: if it's literally the only case where we have to do this kind of conditional behavior, I think it's fine to hack it in. when there are two or three such cases, it'll be worth it to generalize
#KartikPrabhuhmm. i think the "item" thing in hreview and hreview-aggregate is the only case so far
#KartikPrabhuok kylewm my mf2py repo is updated with the hevent -> vevent fix. feel free to pull from that and add these hacks :)
#LoqiGit is a popular distributed source control management system that can be used to host and share code from independent sites https://indiewebcamp.com/git