#aaronparecki.comedited /Webmention (+156) "/* Verification */ verification is a MUST if the receiver is going to use the webmention, allowing receivers to avoid verification if not needed/wanted (#12)" (view diff)
#snarfedkylewm: yeah, good point, no idea. that may be a showstopper
#snarfedtantek: sure! the API part would have been useful too, since we know that's how we'd do it, but no matter, that definitely describes the user feature. thanks!
#tantekI figured you could add the API details for the requested user feature :)
#bearI wasn't seeing it in my local tests so that I fixed it
#bearmy hunch is that a dependency is out of date on the server
#tanteksnarfed, kylewm, next-up for me & person-tagging is to figure out a way to immitate person-tagging on the Twitter POSSE copy of photos
#tantekI'm hoping that by experimenting and prototyping that I can come up with something straightforward for Bridgy Publish to do, or at least a recipe / functions for others to use when Bridgy Publishing a photo to Twitter
#aaronpki thought twitter supports proper person tagging now
#LoqiA person tag (AKA people tag) is a special kind of tag that refers to a specific person by URL rather than just a word or phrase, and is done as an explicit tag by the user, beyond just mentioning a person via hyperlink / h-card https://indiewebcamp.com/person-tag
#KartikPrabhu"I might even person-tag a note and not mention the person's name in it at all." i don't see how you write a post about someone and then not mention them in the post but then tag them
#KartikPrabhuI guess I'll just put person-tag in my list of things not understood
#tantekKartikPrabhu: if you don't use person-tags yourself in existing behavior, then don't bother
#KartikPrabhuaaronpk: oh thanks for the example. So you wanted to tag anomalily because she is related to the post/you wanted her to see it, but the content is not about her
#matrrixsnarfed: Does https://brid.gy/about#facebook-publish imply that if someone comments on a FB post that I have posted using Brid.gy won't get webmentioned back to my site? or is it the inverse that is affected?
#KartikPrabhumatrrix: brigy-publish is for publishing while (normal) bridgy is for backfeeds. If you are signed up for bridgy you can do both
#KartikPrabhuyeah. the FB API might not give access to read private posts but can give access to post private posts. But i must defer to snarfed or kylewm on this one
#tantekpetermolnar: worth investigating how they could confirm Google indexed anything, and yet "JSON-LD content fails to show up in the search results."
zero-gravitas joined the channel
#GWG!tell tantek Interested in attending. I have family there I can stay with.
#tantek!tell GWG FYI I will be in NYC the weekend of the 19th-20th - might still be able to pull-off a one-day IWC NYC if we get a venue and rally a critical mass.
#GWGtantek, Saturday is better for me. But I'd come out to say hi either way
#LoqiGWG: tantek left you a message 8 minutes ago: FYI I will be in NYC the weekend of the 19th-20th - might still be able to pull-off a one-day IWC NYC if we get a venue and rally a critical mass. http://indiewebcamp.com/irc/2015-12-08/line/1449589607054
#aaronpkhow about once you get a second response identical to an existing one then you group them
#aaronpkso if someone replied "cool" it would show up as a comment, but if someone else replied "cool" after then it would group them and show a counter
#tanteksince those are the only two actually documented / specificed / and very well interoperably implemented extensions so far
#tantek"property" is more of an experiment than an extension, it doesn't even have an extension spec yet
#tantekand thus because it is not even close the level of quality / progress as Vouch and Salmention, "property" does not deserve any consideration to be in core
#tantek.comedited /Vouch (+9) "move protocol summary to before indieweb examples and rename to protocol, already have summary at top, this is the place for details." (view diff)
#tanteknow just to move the relevant spec text from comment-propagation to /Salmentions and reword it to handle all responses (e.g. tags, likes like SWAT0 does)
#gRegorLoveHeh "Yo is a social application for iOS, Android, and Windows Phone. Initially, the application's only function was to send the user's friends the word "yo" as a text and audio notification,[1] but it has since been updated to enable users to attach links and location to their Yo's.[2][3]" https://en.wikipedia.org/wiki/Yo_(app)
#gRegorLoveYo takes its first step to eventually reading email
#ZegnatAll my own code just kept running, so not really. But that is with a relatively "young" codebase, no PHP 5.4 compatibility that might have gotten deprecated
#ZegnatBut obviously YMMV, so read the migration guide. It isn’t as long of a read as you might think. And it can save you a lof of headaches in the end. E.g. they changed JSON parsers which might lead to bugs if you are pulling external data
#KevinMarks_seems to imply that indexes do some kind fo brain-dead parsing of the fields
#ben_thatmustbemeonce thats done, i think i have a way to recognize <any set of 1-4 emoji> (as some are multi-character compositions) or any single html special characters in that range
#ben_thatmustbemei might expand it to any html special char, not sure
#ben_thatmustbemewonders if he should actually check for ZWJ and VARIATION SELECTOR to make sure i'm not just getting multiple Emoji right next to each other
#kylewm.comedited /Micropub-brainstorming (+437) "/* Discovering Supported Syndication Targets */ note aaronpk's suggestion to host an h-card for the syndication target instead of passing information to the micropub client directly" (view diff)
#kylewmaaronpk: can you make sure i characterized your suggestion correctly there?^
#aaronpkI think the explicit language around posts and comments should be in the Salmention extension and that's a good justification for the extension existing
#aaronpkfwiw adding the code to handle checking for updated children added quite a lot of complexity to my webmention processing, and it is not even a complete implementation of it
#tantekshould "Updating existing webmentions" explicitly mention properties of the h-entry as a minimum viable/required/MUST aspect then, and then MAY for checking for updated children?
#tantekand then the Salmention extension can make checking for updated children a MUST
#tantekjust trying to find out a good incremental separation here
#aaronpkit would have to mention it in vocab-agnostic terms such as "properties of the object on the page" or something, since the webmentioned document may not be HTML+microformats
#aaronpkup until the SWAT0 demo I treated an update naively, just replacing the existing content from the page with the new content, but the notification was the same as the first time it came in
#tantek.comedited /Webmention (+466) "/* Updating existing webmentions */ expand upon webmention update implementation requirements, may, and if so, MUST support Salmentions" (view diff)
#tantekaaronpk - it's a MUST conditionalized on a MAY
#bearthe MUST is nestled nicely in the part about the optional implementation in the MAY part
#aaronpkyeah i just mean that if someone were to develop an extension that worked in a different way it woudln't be possible to reference it then
#tantekthat's the point, it says you MUST at a minimum support direct properties, but may support more, but if you support more, you MUST do so this way
#tantekcorrect - by default for interop we assume there is no need to develop an extension that worked in a different way
#tantekbecause the assumption of "an extension that worked in a different way" leads to *less* interop by default
#tantekI too have witnessed far too many failed spaghetti specs
#tantekwhere you think you're done, and then there's a *requirement* to implement a whole another spec
#bearthe xmpp community is digging out from that tech debt by forcing new specs to be tighter focused
#tantekwhereas this way, in the "core" spec, the "feature" is a MAY (which means, STOP HERE by default), and if/when you do decide to venture further, here is how to do so
#snarfedand the visible html in those mf2 pages is low low priority
#aaronpkfeature request: visibly link the profile URL and put it first in the list, and treat other URLs in the bio as alternate URLs and make them show up after