#tantekin the bridgy case, since FB RSVPs have no user-authored text, it makes sense to figure out a way to omit any display text if the only information is the RSVP status
#tantekok first things first we don't need e-content for sure
#aaronpktantek: but for consumers that don't recognize rsvps, it should still show up as a regular reply
#LoqiAn event is a type of post that in addition to a post name (event title) has a start datetime (likely end datetime), and a location https://indiewebcamp.com/event
#KevinMarksno, a "what si the text UX we want" one
#KevinMarkswithout parsing any markup, bridy's relected post say "Tantek Çelik is attending. Tantek Çelik is attending."
#KevinMarksin fact, if you read the alt text too (as as creenreader would) it says "Tantek Çelik is attending. Tantek Çelik Tantek Çelik is attending."
#kylewmthe bridgy ui is what you get when you generate microformats html *from* microformats json ... probably not the ideal way to design for user consumption :)
#Loqikylewm meant to say: the bridgy ui is what you get when you generate microformats html *from* microformats json ... probably not the ideal way to design for human consumption :)
#KevinMarksbut you and aaron are parsing that HTML
KartikPrabhu joined the channel
#KevinMarksbridgy is generating json first then html?
#KevinMarksthe problme is that bridgy says it redundantly
#kylewmfor an implementation that does not recognize RSVPs as special, I would want that to show "kylewm: I'm attending HWC and hope to get help setting up my website!"
#kylewmfor an implementation that does recognize them as special, "kylewm: [[RSVPed Yes]] I hope to get help setting up my website!
#snarfedso re bridgy rsvps…i glaze pretty fast at markup, as usual, but i'll implement anything as long as i don't have to understand it
#snarfedfeel free to file an issue if/when there's a clear conclusion
#kylewmfor the markup i was imagining, I think we would need a new property <span class="p-rsvp">yes</span> I'm going to HWC. <span class="p-rsvp-comment">I may be a few minutes late</span>
#kylewm(obviously it would need a better name than p-rsvp-comment
#tantek.comedited /event (+540) "/* Attendees */ separate silo attendees, start document some of the indie event rsvp display brainstorming" (view diff)
#tantekkylewm: I don't think we need a new property
#tantekwe already have an explicit way to provide comment content (rather than implied)
#tantekand that is p-summary or p-content - depending on whether the publisher wants the entire reply displayed as a comment on the destination, or only a summary
#tanteknote p-name has *always* been fallback reply/comment content
#tantekRSVP aware consuming code: if there's a p-rsvp, use it, and only display a comment if it is in a p-summary, or p-content
#kylewmI think I need to see an example, typically reply code would use the content property instead of the name property if it was available
#tantekRSVP unaware consuming code: (already defined behavior in /comments-presentation ) if there's a p-summary use it, else if p-content use it, else if p-name use it.
#Loqitantek meant to say: kylewm: yeah - because it didn't read sensibly
alanpearce joined the channel
#kylewm<div class="h-entry">In reply to <a class="u-in-reply-to" href="http://aaron.pk/hwc-event">Homebrew Website Club</a>, <data class="p-rsvp" value="yes">I'll be there</data> <span class="p-content">but I may be a couple minutes late</span></div>
#kylewmRSVP aware consumers would handle that properly. Kyle [[RSVP Yes]] but I may be a couple minutes late
#kylewmRSVP-unaware consumers would only dispaly "but I may be a couple minutes late"
cmhobbs joined the channel
#aaronpkbut isn't "I'll be there" part of the user-entered text in this case, so should go inside the p-content?
#kylewmI thought that was the whole entire problem we were trying to solve?
#kylewmyou disagree that that's what i would want?
#aaronpklol well I disagree with that being a desirable outcome. Seeing just "but I may be a few minutes late" seems wrong, since the user entered more than that.
#aaronpkthat's a good one. so you type "I really miss you guys" and choose "RSVP yes", that is handled fine for rsvp-aware consumers. but what about unaware?
#tantekaaronpk, kylewm I think the first problem is that the DRY violations in the Bridgy output is confusing things more than we need.
#aaronpkcurrently that will appear as just a comment saying "I'm not available to host this week" on rsvp-unaware consumers, which does not include the RSVP yes/no information
#tantekI think what we discovered is the "name" is the general fallback
#tantekor rather, "name" *works* as a general fallback
#tantekfurther question - could/should we use *summary* as a *deliberate* fallback?
#aaronpkinteresting, I could see doing that for my bike rides
#tantekthat would free-up "name" to be more name-like if/when needed
#tantekwhereas "summary" kind of makes sense for the *visual* summary of an RSVP with an icon representing yes/no/maybe for example, or even the auto-generated text for it
#tantekI still think summary is a good way to communicate to consuming code that the summary *can* be displayed instead of the full content, with perhaps a way to expand to show the full content
#tantekinstead of the consuming code having the ellipse the content at an automatic but inopportune breaking point
#kylewmtantek: I'm still a little confused about the previous issue. We have solved it so RSVP-aware implementations can ignore content-less bodies, but not for RSVP-unaware implementations (afaict)
tilgovi_ joined the channel
#kylewmmaybe that's just an ignorable case. events that don't recognize rsvps would be pretty weird
#tantekperhaps because the latter use-case is unclear
#bretpeople markup things with mf2 to get access to a machine readable version of the page, people markup with semantic tags based around a loose idea of how they should be used
#bretmaybe due to lack of an end goal, what you could possible get back from semantic tags is relatively low quality
pwcc joined the channel
#bretstill, if there was an actual usecase with how semantic are used together, like there is with mf2 classes, (maybe mirroring mf2) people would use them in a useful way
#bretanyway, not planning on writing a parser anytime soon
#aaronpki dunno we seem to get by just fine with microformats classes, which have the added benefit of being recognizable in the source code
#fkoomancweiske: there is a standard for publishing fingerprints on webpages...so I'd prefer to use that :) I also like the scoping to the particular instance of "IndieCert"
#Loqiben_thatmustbeme: tantek left you a message 5 minutes ago: yes there are nicely styled hCards documented on the microformats wiki (obviously easy to re-use for h-card) http://microformats.org/wiki/hcard-examples-in-wild#Individuals (see the first subsection "Nicely styled)
bupkes and danlyke joined the channel
#kylewmfkooman: in your indieauth proposal, I don't understand why/when you would want the auth and verify endpoints to be different
cweiske joined the channel
#cweiskeaaronpk, how is a hub supposed to make a thin ping in pubsubhubub 0.4?
#kylewm.comedited /IndieAuth (+276) "/* Why is the IndieAuth verification response form-encoded instead of JSON */ vote to settle on one canonical format" (view diff)
#rasculi had it running but i couldn't get any of the extra stuff working like twitter
#aaronpkugh people don't like the form-encoded response
#aaronpkthe only reason I could see to switch to JSON response is that the OAuth 2.0 spec says it should be JSON
#kylewmare there other examples of APIs returning form encoded data?
#bretwho cares about form encoded, use the library that every language has
#aaronpkremember when every language had an xml parser?
#aaronpkyeah if someone wants to make a wiki page comparing the behavior of parsing form-encoded and json in a bunch of langauges/environments that would be awesome
#cweiskeaaronpk, about the pubsub payload: section 7 says: "... with the payload of the notification. This request MUST have a Content-Type corresponding to the type of the topic. The hub MAY reduce the payload to a diff between two consecutive versions if its format allows it."
#cweiskebut the content-type must be that of the topic....
#aaronpk"Notification: A payload describing how a topic's contents have changed, or the full updated content. Depending on the topic's content type, the difference (or "delta") may be computed by the hub and sent to all subscribers."
#bretelf-pavlik: the form encoder is working great actually... the %5B%5D just looks funny. thats the [] next to the keys that tell it which array to go into
#bretelf-pavlik: is that script what you were looking for?
#elf-pavlikbret, please give me few minutes... will take a break from Social IG ACTION-4 and check it now
#cweiskeaaronpk, another pubsub question: 5.2. Subscription Validation says "Subscriptions MAY be validated" but a sentence later it's "hub MUST perform the verification of intent"
#cweiskeI originally thought that VoI is the validation
#cweiskebut it reads as validation is something different
#ben_thatmustbemeaaronpk, i feel like we need an alternative to indieauth.com just so people get the difference between indieauth and.... what is the actual auth mechanism called? rel-me-auth?
#aaronpki think it's saying that hubs can do whatever they want to validate subscriptions, like having their own access controls or rate limits or usage limits
#aaronpkso you could make a hub that lets people subscribe to 4 topics for free, but requires $$ to subscribe to more
#kylewmreally interesting to read fkooman's proposal and aaronpk's response.
#benwerdI feel bad being commercial here, but FYI: https://withknown.com/pro/ is completely live. Indie Web capable, does IndieAuth and Micropub, has strong connections to brid.gy.
#elf-pavlikbenwerd, i understand that you keep *all* the codebase open source and just charge people who don't want to deploy it themselves or use https://indiehosters.net service?
#gRegor`You can get a free .withknown.com subdomain. Pro has additional features though.
#gRegor`So there's a free version people don't have to deploy themselves
#benwerdelf-pavlik: The whole codebase is indeed open source. The sad exception will be Google+ Pages integration, which we legally can't open.
#donpdonpindieauth feature suggestion, from showing the login process to a friend with a domain name but no interest in hosting a webserver, which seems reasonable.
#snarfedso aaronpk tantek_ kylewm etc, i'm thinking about the rsvp markup and presentation discussion yesterday…and i'm wondering how much of it applies to likes and reposts too
#Loqisnarfed: GWG left you a message 24 minutes ago: I will be deploying several alternate CSS options in your name
#snarfedi think best practice right now for g+ posse is manual, by popping up their sharebox with everything pre-populated so the user only has to click "post"
#ben_thatmustbemewas getting ' Error: 400 Bad Request The server could not comply with the request since it is either malformed or otherwise incorrect. Missing required parameter: source_key Missing required parameter: source_key' when trying to preview post of 'https://ben.thatmustbe.me/photo/2015/3/5/2/'