snarfed, gavinc and lukebrooker joined the channel
#tantekKevinMarks++ for starting /etag - it's a good start. A step-by-step How To, and perhaps IndieWeb Examples section (is anyone programmatically setting ETag / Last-Modified headers? ) would be even better!
#LoqiA reader (or indie reader) in the context of the indieweb is the portion/feature integrated into an indieweb site that provides a way to read content from other indieweb sites, possibly including posts from the current site as well https://indiewebcamp.com/reader
#mblaneyI realised that I set the time to 24 hours so that the author had a chance to edit posts and they could be re-syndicated.
#mblaney(ie not due to any other polling assumptions)
loic_m joined the channel
#Loqi[mention] Brynn Evans, Deb Schultz, Christian Crumlish, Kara Murphy, Adam Rifkin, Paul Mison, Sabrina Bruning, Doc Searls, Pascale Diaine, Nicole Tollefson, Elisa Jo Harkness, Simon Law, Joël Franusic, Sarah Austin, Matthew Levine, Thor Muller, Colleen Taylor, Joichi Ito, Ben Ward, Katarzyna Babula, Beau Smith, Dan Gailey, Stacey Rivet, Bettina Warburg-Johnson, Matt Harris, Chris Heuer, Cari Levay, Zoe Schiffer, Charles Hope, Olya Lapina, Lawrence Lessig, Jesse Vincent, Zack Fischmann, Jon Pierce, Robin Andersen, Mo Kudeki, Stephanie Vacher, Faruk Ateş, Loic Le Meur, Jordan Harband, Stephen Wyatt Bush, Natalie Downe, Jessica Suttles, Erin Jo Richey, Kevin Smokler, Joseph Smarr, Paul Tarjan, Micah Snyder, Stephanie Haupt Sullivan Rewis, Jeremy Anderson, Brendan Eich, Mary Specht, Jen Bradburn, Laura Forrest, David Baron, Jet Villegas, Anselm Hook, Karen Nguyen, Sarah Dopp, Edward O'Connor, Thomas Vander Wal, Arezu Aghasey, Evan Prodromou, Yan XZ, Paul Hammond, Ian Fung, Larry Halff, Jordan McArthur, Jay Alle
#Loqi[mention] Nate Koechley, Cariwyl Hebert, Justin David Kruger, Nima Dilmaghani, Liza Sperling, Mathias Crawford, Daniel Burka, Erin Stevenson O'Connor, and Zibi Braniecki were invited to https://webmention.io/notification/HWyxJpI76_Hcfx0deU2v_A
kerozene, eschnou, j12t, fkooman, LauraJ, glennjones, sammachin, sparverius, scor, loic_m and modem joined the channel
#voxpelliOh, looks like http://tantek.com/ disappeared from the internet, "This web site is currently inactive. Please contact billing to reactivate your account."
friedcell, j12t, LanceyWork, kerozene, j12t_, eschnou, nitot, hs0ucy, tantek, scoates and snarfed joined the channel
#JeenaLooks like nobody is comming to the HWC in Gothenburg today, so I'm stopping it and going to our company event driving gocart instead too
#KartikPrabhuJeena: might want to note it on the evnt page that it is cancelled
#voxpelliwould be cool with an indieweb event "reader"/tracker like Lanyrd – where one could get a notification about such a canceled event :) with some micropub rsvp:ing and favoriting
#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
#voxpelliyeah, I know, but there's no reader/tracker for them specifically :)
#voxpelliKartikPrabhu: yeah, but on eg. Lanyrd I can both rsvp and track an event – no matter if I'm invited or not – and if I do then I should get updated around it and Webmentions wouldn't be enough for that
#voxpelliactually not really sure how one would communicate a cancellation properly – Pubsubhubbub-subscription to the details of a specific event? Unlike an h-entry one is often very interested in keeping track of what happens to an h-event
#voxpellievents often add more detail around the event and maybe change the time and/or location – or cancels it completely
#fiatjafLoqi: !tell snarfed: the screenshot from your site at https://www.brid.gy/about shows the comments on the side of the post, but I couldn't manage to get them showing like that in your actual site. has something changed? or is my resolution that is too low?
#Loqii'm sure !tell snarfed: the screenshot from my site at https://www.brid.gy/about shows the comments on the side of the post
#fiatjaf!tell snarfed: the screenshot from your site at https://www.brid.gy/about shows the comments on the side of the post, but I couldn't manage to get them showing like that in your actual site. has something changed? or is my resolution that is too low?
#Loqi[snarfed]: fiatjaf left you a message 3 minutes ago: the screenshot from your site at https://www.brid.gy/about shows the comments on the side of the post, but I couldn't manage to get them showing like that in your actual site. has something changed? or is my resolution that is too low? http://indiewebcamp.com/irc/2015-09-23/line/1443022234266
shiflett joined the channel
#fiatjafsnarfed: I like the comments on the side of the bridgy screenshot. it has been a source of confusion for me over the last months. every time I see the screenshot I go to your site to see it better, and it is never there.
nitot and Geng joined the channel
#GengHi there. just to make sure. Today we still have the prewired thing to do in Codebase, right?
danlyke joined the channel
#GengEr... or maybe I should ask if there is anyone online first?
#tantekJeena - sorry to hear about Göteborg HWC cancellation but understandable - no RSVPs on your indie event or POSSE copy?
#tantekwas hoping to hear about a SWAT0 demo from you!
cweiske and tantek joined the channel
#tantekvoxpelli: yes - site disappeared briefly yesterday and a few hours this morning due to exceeding bandwidth limits - nearly all due to bots, nearly all due to bad behaving bots, and a big % of that was excess polling of Atom feed.
cleverdevil joined the channel
#tantekinteresting discussion about event (post) cancellations and other event info updates (name, location, description, time) !
#tantekwe do have an existing (proposed) protocol for this for responses in general (and thus would apply to events + RSVPs etc.)
#tantekmakes sure it's on the wiki and not just a latent undocumented brainstorm ;)
#voxpellitantek: the SWAT0 will still happen, but in a while instead of now :)
#tantekI will add that to /event as well since it is non-obvious that this is a (hypothetically) solved problem - I don't know of any implementations yet
#voxpelliOh, WebMentions again :/ So if something gets stuck in the moderation queue or rejected otherwise by publisher then no way for client to subscribe to updates
#tantekif you send a response webmention to an original post, you should be ready to receive a webmention right back to your response from that original post when the original post is updated, WITHOUT moderation
#voxpelliIf the original post doesn't understand/accept the response, then it won't send any updates
Geng joined the channel
#voxpelliIt's Pubsubhubbub with implicit subscribe basically :P
#voxpelliAnd for it to work with my endpoint I would more or less have to create a PuSH-like hub that users of my endpoint can ping on updates rather than them pinging a Pubsubhubbub hub
#tantekI'm a little confused how this requires PuSH in any way
#tanteksince it's easier to support receiving webmentions than subscribing to PuSH updates
#tantek(as evidence by more implementations and deployments thereof in the community)
#voxpelliWe have two techs: WebMention and PuSH. One is for upstream notifications, the other for downstream subscriptions. Yet the latter is often attempted to be solved by the former.
#tantekwebmention is for any kind of peer-to-peer where A links to B
#voxpelliSo it should not be possible to subscribe to updates of something without interacting with it? That will force the same polling to happen as killed your site yesterday
#tantekno there's no polling with webmentions - that does not follow
#tantekalso - bad bots that have no curlable presence on the web were at fault - nothing to do with visible servers
interactivist joined the channel
#voxpelliTo receive a reverse WebMention you first have to do a regular WebMention. So unless you do, you can't receive updates.
#tantekthat's a tautology. that's like saying, in order for the protocol to work, you have to use the protocol.
#tantekand sending a single webmention != polling !
#voxpelliso unless someone has sent you a WebMention about them accepting an event, there's no way to notify them about changes to the event – unlike there would with PuSH – because the only thing needed then is that someone has subscribed to updates
#aaronpkanyone should be able to come along and say "i want to know when this page has changed", and if that page supports PuSH then great, if not, it can just poll it
#tantek.comedited /event (+767) "/* Brainstorming */ Response context CRUD, including what to do if/when you cancel an event" (view diff)
#voxpelliaaronpk: somewhat different, somewhat similar – one can solve the goal of the other in some cases
#tantekaaronpk "if you're talking about getting updates to an event, that's what PuSH is for" I disagree - you're jumping to plumbing ignoring the use-case
#voxpelliUse case: Privately track URL:s one are interested in, but haven't (yet) RSVP:ed to
#aaronpkif I save an event, I usually explicitly don't want to tell the event I saved it, it's like a private bookmark of sorts. I certainly don't want to be listed as someone who has saved it
#tantekPuSH is harder than webmention to implement. simpler solution preferred. QED.
#Loqivoxpelli meant to say: Use case: Privately track events one are interested in, but haven't (yet) RSVP:ed to
#voxpellitantek: I disagree, I find PuSH to be easier in this case
#aaronpkpretty much if you start extending webmention to do this it becomes PuSH
#tantekvoxpelli: evidence disputes your assertion of ease. more implementatations of receiving webmentions than PuSH.
#tantekand simpler! fewer moving parts, less code, less indirection, etc.
#voxpellithe salmentions added enough complexity in my endpoint, distributing updates of content itself will be a pain as it's outside of the scope of my endpoint really – it's a task for a PuSH hub
#tantekaaronpk - absolutely not - because PuSH has the whole "H" part
#aaronpki'm like 90% sure that if you start actually explaining how to use webmention to do this you'll find out pretty quick it looks like push
#tantekwebmention works with a simple HTML form, PuSH does not etc.
#voxpellialso: it's impossible to unsubscribe from WebMentions – hence WebMentions should only be used for scenarios where you can't be expected to subscribe to something
#aaronpknow what you've done is moved the state managment of keeping track of subscribers into the webmention sender, and now it's no longer a simple protocol
#aaronpkbut I can't really be sure i'm not going to show up in a generic "mentions" list if I send that
ttepasse joined the channel
#tantekyou can if your bookmark is a private post perhaps?
#aaronpkbasically I don't trust that your implementation of events is going to properly understand the "bookmark" or whatever it is and not display it as a mention
#tantekhmm - private reply to a public post - that could work!
#voxpelliand that's not more complicated than PuSH? PuSH definitely has mor eimplementations than private posts in the community
#tantekthe right thing for the public post to do would be to keep track of the private reply (perhaps to show original author), but NOT display it to everyone who sees the event
#tantekyou're asking someone to do work for you who is not benefitting
#tantekyou've misplaced incentive with where the work must be done
#tantekthus, it won't get done, or it certainly won't scale
#aaronpkare you more willing to start handling private webmentions?
#tantek(scale meaning socially/investment in human time here, not a technical "scale")
#voxpellidoing a WebMention POST or a PuSH POST – both are as easy I think – difference is that with the WebMention POST you need to do one per response, but with the PuSH POST the hub can know who has subscribed
#tantekheck yeah, private webmentions are FAR more useful personally!
#tantekwhereas ALL the work to support per post PuSH does not benefit me at all - so I won't do it
#tantekthere may be some experiments, but insufficient motivation for it to get much adoption
#voxpelliI do my PuSH POST:s through GitHub WebHooks right now – for WebMentions updates I would have to create a similar Hub functionality somewhere to at all be able to replicate it. So much harder for me
#tantekvoxpelli: that makes no sense. if you support webmentions at all, you're sending them upon publishing to all links in your post
#rhiaroskimming backlog, I display bookmarks in theory but nobody has bookmarked any of my posts yet
#voxpellitantek: my webmention sender have no idea about what webmentions I have received
#tantekdoesn't matter. you link to your responses, thus you can send webmentions to them
#voxpellialso: My webmention sender, while still not fully built, will be based on PuSH
#voxpelliso my webmention sender needs to poll my webmention receiver – argh :P
#rhiaroAnd I also second the idea of being able to subscribe to / follow any post (including events) without them displaying it. But I guess I'd have to poll for updates.
#voxpellianother problem with WebMentions instead of PuSH: One can't detect support for such updates
#kylewmfor subscribing to individual posts for updates, I'm concerned about the part of PuSH that requires you to periodically refresh your subscriptions
#rhiarohang tight kylewm, need to run my incoming wm wrangling script
#tantekwith /vouch a bit more work for sure, but even then I don't think it's close to PuSH complexity / state management
#tantekthe use-cases are receiving responses and displaying them, and then updating responses when the original changes, and lastly salmentions, updating responses when another response changes
#voxpellitantek: how would you know that you don't need to poll a site for updates, because you will receive WebMention pings on all updates?
#tantekif a site chooses to not send you webmentions, it's either broken or they don't want to, so you can respect that and not worry about it
#voxpelliwell, very few sends such webmentions today, so that would mean many sites will have to be considered broken for quite a while
#tantekvoxpelli: no, not broken per se, but just partial implementations, which is basically every indieweb site - everyone has different levels of implementations of the building blocks, different IndieMark levels, and that's ok
#voxpelliand those who start sending such updates will have a hard time knowing if the receiver is at all interested
#tanteksame thing with webmentions in general - again, it's ok
#voxpellieg. displaying a reply-context isn't mandatory in any way
#tantekassumption of mandatoriness is not why this stuff works
#tantekthis stuff works because people have incentive to provide good UI
#tantekmaking things "mandatory" typically fails because it misplaces incentives vs work to be done
#tantekthe only thing long term scalable/maintainable/reliable thing you can do is design protocols based on incentives being aligned with work
#tantekno amount of "MUSTS" in a spec will make things actually work in practice'
#voxpelliI think we shouldn't rule out PuSH in this case and see which wins in the long run when we have had more implementation experience
#tantekvoxpelli: sure - if you want to implement PuSH on every post - go for it - not saying not to!
#tantekI'm saying it's a methodologically flawed approach since it has a misalignment of incentive vs. who does the work
#tantekbut that shouldn't stop you if you feel like doing the work yourself on your own site :)
#voxpellibiggest problem we have right now imho: Too few readers with too little diversity inbetween them, thus making it hard to dogfeed certain scenarios
#Loqivoxpelli meant to say: a big problem we have right now imho: Too few readers with too little diversity inbetween them, thus making it hard to dogfeed certain scenarios
#tantekvoxpelli: you're right about not enough indie readers - still waiting to see someone implement inline reading on their own site with the post /create UI at the top
#rhiaro(also your other reply to that post doesn't show up because of another bug i have)
#voxpelliwhat originally sparked this event discussion was the idea of a Lanyrd like reader for indie-events and it was in the context of that PuSH was btorught up
#tantek(with screenshots would be nice! - I say this having documented a bunch of the existing stuff there)
#voxpellitantek: probably not the right place – Facebook allows everything to be saved privately – so not specific to events
#tantekreally? I only saw "Save" as a button on their events
#[aaronpk]voxpelli not quite, imagine that you want to receive updates from a page or feed, with PuSH you look for the hub endpoint, if you were to do it with webmention you'd look for a webmention endpoint
#tantekand maybe create a separate stub page for it
#tantek(with those examples of event, group post, pages)
#voxpelli[aaronpk]: if you wanted to send a "subscribe" WebMention, yes, and then that site would do a lookup on that page and find the callback URL as the WebMention endpoint of that URL – so instead of explicitly sending a callback URL, one embeds it in a "subscribe" webmention
#[aaronpk]With webmention subscriptions you'd basically create a URL that acts as your verification of your subscription, and it's easier to manage that because the subscription would be active as long as that URL exists
#[aaronpk]To unsubscribe you'd delete your subscription URL and resend the webmention
#voxpelli[aaronpk]: so it would be like an infinite PuSH subscription that one would have to explicitly unsubscribe from – something one could make PuSH do as well, but which I imagine there has been a specific reason to not do
#voxpelliso rather than the subscriber doing regular resubscribing, the publisher will do regular polling?
#voxpelliI think I rather have subscribers resuscribe than publishers polling – the ratio between publishers and subscribers tend to be that there are a lot more of the latter than the former
#aaronpknot even polling, because in order to send that webmention, the publisher has to *discover* the webmention endpoint *from the subscription url*
#tantekI'm thinking of implementing that + 1 feed item minimum
#tantekthus allowing subscribers to *only* poll once a day
#voxpelli[aaronpk]: the subscriber can request a specific hub.lease_seconds, but the publisher can choose to ignore it, but will always communicate the time frame
#aaronpkbasically waht i'm saying is that's not much of an optimization and adds complexity on both sides
#voxpellito know whether you need to resubscribe every day/hour/week?
#aaronpkrhiaro: re: wanting to create an ubsubscribe post, I think that'd be fine too. it would need a reference back to the original subscription URL
#kylewmi thought there was some minimum for what the lease would be?
#voxpellikylewm: didn't see any when skimming through the specs – feels like something the spec shouldn't care about
#aaronpki guess i don't see the problem of having to discover the webmention endpoint when you go send another webmention
#aaronpkpoint is you *can* optimize if you want, but you don't have to
#aaronpkwhereas PuSH requires a certain level of complexity off the bat
#KevinMarkssnarfed: would If-Last-Modified help with the facebook-atom duplication problem?
#snarfedsorry, i jumped into the conversation without context :P
#gRegorLove(Scrolling back) A subscribe and unsubscribe could still be the same URL. Have it return HTTP 410 when it's unsubscribed, and set the updated date to the unsubscribe date.
#voxpelliyeah, I'm just saying PuSH twice a sentence
#voxpellikylewm: yeah, as all the current hubs have the same use case they probably have all set similar minimum times (wonder if they have a shared max as well?)
#KevinMarksthe point of the /etag conversation was to help minimise polling
#voxpelliaaronpk: it layers a lot of stuff on top of WebMentions which makes it increasingly hard to implement a full WebMention endpoint
#voxpelliit was simple before Salmentions, then Salmentions complicated things and this will add even more and then we have the Vouch things etc etc – eventually it will be too much to selfdogfood
#KevinMarksmy cunning plan is to eventually make voxpelli manage my annotations web-wide
#aaronpkreally? I think it's mostly just doing the same things
#KevinMarksas I can webmention anything via voxpelli's app, and it will keep them for them until they decide to ask
#voxpelliaaronpk: Salmentions made my endpoint much much more complex – from one HTTP request to 3-4 per ping
#aaronpki meant the subscription part. i also haven't implemented salmentions yet
#voxpelliaaronpk: the subscription part means I would have to start accepting pings for content updates – like any PuSH Hub would
#aaronpkbut you should be doing that already for regular webmentions
#voxpelliI don't care about the contents of a webpage until I'm supposed to deliver a salmention to the pages it mentions
#snarfed(ie not just responses to kylewm's original tweets)
#voxpelliaaronpk: but you said "but you should be doing that already for regular webmentions"
#aaronpki was talking about sending webmentions when you've updated the post
#voxpelliaaronpk: so why should KevinMarks be notifying me of his new posts today when all I'm doing is receiving comments on his behalf?
#aaronpki'm getting lost. the term "me" is getting used to mean both your personal site and your webmention service, and i can't follow
#voxpelliI only receive comments, the WebMentions sending is typically out of scope of my endpoint (although salmentions forced me to do add it partly – and with me I mean my endpoint)
#voxpelliand thinking about it I should probably also defer the salmention-pinging to an external service
Geng joined the channel
#snarfedpulled the trigger, hold on to your butts...
#KevinMarkswell, I only have a couple on my main site, as I didn't POSSE the most comment-provoking tweet
#tantekKevinMarks, no need to be inflammatory, just thank the XOXOFest folks for how well they sorted/filtered out all the trolls, especially in person and in Slack, e.g. (insert your favorite GG hashtag here)
#snarfedunlikely that we'll do it in bridgy any time soon, so you probably would get there before us
#voxpellisnarfed: yes, because I don't fully POSSE yet, so it misinterpreted URL:s and stuff – hence my ticket about wishing to lock things down to just those URL:s with a explicit u-syndication
#voxpellisnarfed: the proposal was basically: Don't do anything hard on your part, let me do all the hard stuff for you ;)
#snarfedvoxpelli: #51 actually gets halfway there; many things now will only be sent as mentions, not actual replies/likes/etc
#snarfedvoxpelli: lol ok. i like that spirit! i'll actually read and reply soon.
#KevinMarkshm, so I'd need a public block list for voxpelli to see to filter
#voxpelliKevinMarks: well, public or private, so proposal to snarfed was to export your Twitter block list as a private block list you could link to from your profile and/or import directly into my endpoint
#tantekKevinMarks: nah, you just need some sort of block UI. whether that's with a list, public or not - those are details.
#tantekcan an app that has Twitter read-only OAuth into your account read your Twitter blocklist?
#voxpelliI don't want to save such data in my endpoint – that would make me silo:ish :P
#snarfedok bridgy #51 (smarter posse vs mention detection) and #456 (search all tweets for mentions of your site) are now on for everyone, with hopefully final logic for both
#tantekvoxpelli: again, that's too plumbing-centric a definition / viewpoint.
#tanteka follow list or a blog roll *can* be used as a whitelist for some particular use-case, like Vouch but doesn't have to be either.
#tantekFlickr even calls it "Your Block List" literally in the UI
#tantekhence the term is preferred over something like "blacklist"
#voxpelliwhitelist as in "people I prefer to see more from", blacklist as in "people I prefer to see less from"
#KevinMarksah, bridgy doesn't know that that tweet was a POSSE
#voxpelliand I meant it from the perspective of the actual format being XFN like and that the things are two sides of the same coin, rather than as a kickass definition
#snarfedKevinMarks: if you add known.kevinmarks.com to your twitter profile, it will
#voxpellitantek: and XFN captures all of the positive relations of the positive side of coin, so the block list / mute / blacklist counterpart would capture the negative relations on the negative side of the coin
#KevinMarksdo I have to use bridgy publish to let it know?
#tantekvoxpelli: XFN does not capture all the positive relations
#Loqivoxpelli meant to say: tantek: and XFN captures many of the positive relations of the positive side of coin, so the block list / mute / blacklist counterpart would capture the negative relations on the negative side of the coin
#voxpellilets rephrase it then: XFN has some cool relations (evidently not all). To make it useful in relation to block lists it could be extended with some more.
#tantekit could be yes. in other ways I've grown to be skeptical about putting more human meaning like that into (mostly invisible) rel attributes
#tantekworthy of documenting brainstorming / experimentation especially with use-cases
#voxpellitantek: remember one thing: That framing something so that it accurately reflects the message that one wants to convey is something that comes with the skills of a language. So we who are not native english speakers might sometimes make mistakes there and it's kind of frustrating when you then focus on that.
#tommorris(funnily enough, today I've been getting my head around how to do friends only/private posts.)
#tantekvoxpelli you are absolutely correct and I apologize.
#kylewmdoes anyone who POSSEs likes to Twitter show a u-syndication url on the original?
#kylewmannoying bug in redwind caused by u-syndication = the URL of the liked post instead of the URL of the like itself (because likes in twitter don't have a url of course)
#kylewmtrying to decide between adding a made up #fragment like bridgy, or just leaving off the syndication url
#tantekif you enjoy IndieWebCamp and hacking/building things - you'll be delighted at Science Hack Day too - strongly encourage you to check it out if you can make it out to SF 2015-10-24..25.
#gRegorLoveProbably not wiki worthy. "Salesforce Marketing Cloud (formerly known as ExactTarget) is a provider of digital marketing automation and analytics software and services."
#tantekhuh - yeah not unless someone here is using them for their Indieweb site?