#tantek!tell barnabywalters do you discover&send webmentions synchronously or asynchronously in your posting UI? either way, do you report webmention results back to your posting UI?
#tantek!tell benwerd do you discover&send webmentions synchronously or asynchronously in your posting UI? either way, do you report webmention results back to your posting UI?
#aaronpkI just showed some of our guys the sample code on webmention.io and blew their minds :) they were like "it's this easy to add comments to the site??"
#tantekaaronpk - note typo at bottom of webmention.io - >/script>
#Loqitantek meant to say: well you're replying to a wiki page and sending it a webmention, shouldn't you thus be ok receiving one from it too?
#acegiakperhaps the webmention comes from the page displaying the change that added the link?
bnvk joined the channel
#tantekthat would be another way to do it - to have revision / deltas send webmentions, similar to how they are posted here in IRC
#tantekthose would even have a specific author could be marked up with p-author h-card
pfenwick, bnvk_, melvster and josephboyle joined the channel
#bretaaronpk, that was a lot of fun at pints! :) thanks for doing that
tilgovi, pfenwick, bnvk, fmarier, tantek and tommorris joined the channel
#petar.petrovic.iocreated /User:Petar.petrovic.io (+172) "Created page with "I am a student from Paraćin, Serbia, currently majoring in software engineering. Recently I got interested in independent web and I occasionally blog at petar.petrovic.io."" (view diff)
#tantek!tell tommorris do you discover&send webmentions synchronously or asynchronously in your posting UI? either way, do you report webmention results back to your posting UI?
#Loqitommorris: tantek left you a message 58 minutes ago: do you discover&send webmentions synchronously or asynchronously in your posting UI? either way, do you report webmention results back to your posting UI?
#eschnou!tell tantek hmm, I don't recall syndicating it on twitter, and google leads me nowhere, so I probably didn't since I considered it a test that could fail :-) Also, I don't keep track of where content is syndicated.
melvster, tpinto, rknLA, lmjabreu, hadleybeeman_, benward and barnabywalters joined the channel
#Loqibarnabywalters: tantek left you a message 10 hours, 16 minutes ago: do you discover&send webmentions synchronously or asynchronously in your posting UI? either way, do you report webmention results back to your posting UI?
bnvk, melvster, andreypopp, glennjones and tantek joined the channel
#Loqitantek: eschnou left you a message 5 hours, 31 minutes ago: hmm, I don't recall syndicating it on twitter, and google leads me nowhere, so I probably didn't since I considered it a test that could fail :-) Also, I don't keep track of where content is syndicated.
#eschnoutantek, yup, never took the time to implement webmentions :-(
#tantekright, so if my site only sends webmentions, my comments won't show up there.
bnvk joined the channel
#tanteknext question for all you webmention senders (aaronpk, barnabywalters, benwerd, tommorris), do you also always send pingbacks? or does your code first do webmention discovery and only if no endpoint found, then look for pingback endpoints and send them?
#cweiskemy lib first tries webmention, and then falls back to pingback
#barnabywalterstantek: taproot looks for webmention, falls back to pingback
#tantekcweiske - cool. Is that deployed live on your site?
#barnabywaltersor I could save the results of each webmention request on the note and then just wait a few seconds before sending an AJAX request and reloading note content
#tantekand his code responds to 410s by deleting received comments also
#tantekI think I like cweiske's HEAD request first approach because it seems like the simplest way to both minimize bytes requested by the server and avoid GETting non-HTML links (which I do link to plenty often)
#aaronpktantek: I also look for webmention first, and fall back to pingback if not found
melvster joined the channel
#tantekaaronpk - somewhere on the wiki I wrote up a feature request for pingback.me or webmention.io to synthesize pingbacks but I can't find it
#tantek.comedited /Falcon (+863) "/* Working On */ more webmention implementation details. HEAD request before GET, fallback to pingback discovery/sending, and reasons why for each" (view diff)
#barnabywaltersthinking a little about the stream pagination problems we were talking about with Alf at IWCUK
#barnabywaltersthe problem is that pagination is done on the page level
#tantekbarnabywalters - indeed, a potential 3rd parameter for webmention that we may end up needing as part of an evolving dynamic whitelist / second-degree approach to fighting spam.
#barnabywaltersthey go away if we don’t trust rel=next/previous on stream pages, and only trust prev/next rels on individual post pages
#tantekthey also go away if pagination always reflects a specific date-time period
#tantekwe don't actually need pagination - just crawlable archives by date-time period
#tantekbarnabywalters - when you write your post about it, please start from the end user use case. e.g. user comes to your site, and then wants to ...
#barnabywalterstantek: RE webmention GET/HEAD discovery, ideally you’d be able to send the request, then check the headers before reading the body — if the headers contain a Link or content type isn’t HTML, close the connection, otherwise parse body
#barnabywaltersnot sure how tricky it’d be to do in PHP though
#shanershadleybeeman: no idea. i just saw it mentioned on twitter by @tomcoates.
#Loqibarnabywalters meant to say: actually, great point — the relationship between your site and silos is exactly the same as between human readable flat files and DBs
#josephboyledoes it depend on the silo supplying convenient APIs for posting and reading?
#tantekjosephboyle why would it? PESOS = a dependence on the silo = you're vulnerable when it inevitably shuts down.
#tantekPOSSE = maybe your code gets an error code when it attempts to explicitly syndicate out. Which if you code defensively you just ignore and go on your merry way.
#barnabywaltersa quick bit of thoroughly unscientific testing indicates that the time-to-headers-received for HEAD vs GET requests is not significantly different either way
#tantekjosephboyle - don't worry about "biggest case for social for people in general" - that's too hard to predict/understand (unless you've got some solid data/studies behind your hypothesis there)
#tantekworry about / build what's the priority for your own personal site instead
#hadleybeemanAbsolutely, tantek. And when I have a free extra minute, I'll look forward to starting that. :)
#barnabywaltersthe only place I can find a consistent difference (HEAD being faster than GET) is on google.com, and there it’s < 0.1 of a second
#tantekhadleybeeman - it doesn't take much longer to edit a wiki page than it does to say something in IRC - so clearly you have free extra minutes :P
#tantekbarnabywalters - do you ever link to large JPEGs or other media files? what does your system do then when doing a GET to send a webmention/pingback?
#barnabywalterstantek: yes, quite often. I don’t do any particularly intelligent checking
#tantekyeah - I don't want to accidentally cause massive GET requests
#tantekon my server. so a HEAD first seems like a reasonable defense against that.
#barnabywaltersall of this is premature optimisation anyway ;)
#tantekbarnabywalters - I disagree - I've already linked to many MB/GB resources in the past - so that's not premature/hypothetical
#tantekit's not optimization, it's defensive programming
#barnabywaltersI wonder if opening a GET request to a huge resource and then closing the connection after parsing the headers causes much load for the server
#barnabywaltersyou can’t install extensions by downloading them, or by opening the files, and there’s no button in the extensions UI or file menu to install one
#barnabywaltersbut you can install untrusted extensions with almost no warnings by dragging them in
caseorganic joined the channel
#tantekaaronpk - what does Aral's indiedata talk have to do with realtime?
#caseorganictantek: not sure at all, but he was given a standing ovation by about 30% of the audience
#caseorganictantek: and it was more about focusing on design in open source. started off a little strange and then inspired people, so it was useful
#caseorganiche said that he created the term indiedata - which reminds me. it's time for an official timeline of indieweb
#caseorganictantek: especially after i give the ending talk
#tantek.comedited /timeline (+1700) "move some non-key indieweb ideas/achievements to history (needs more pruning/focus), research and document Pingback origination dates with citations, linky linky" (view diff)
#tantekok that's a good enough iteration for now - at least I dug up the Pingback history and we know who to ask for more details if need be
#peatYeah, bit us pretty hard. Had to switch our infrastructure over to public messaging. :/
#peat... there are some whitelisted sites (eg: cnn.com), but most links get killed.
#aaronpk"But here’s how I read this: Twitter wasn’t overly concerned about DM spam in the higher ups, until one of the higher ups received the spam. Then they squashed it by banning URLs in DMs."
#tanteklove that totally unbeknownst to folks here people are citing /monoculture
#tantek.comedited /site-deaths (+652) "Dopplr shutdown announced today for 2013-11-01 - just two week notice. note data export URL and how to export contacts" (view diff)
#tantek.comedited /pingback (+563) "explicitly mention backward compatibility for reason to receive pingbacks, add new section on How do I implement sending with suggested implementation approach" (view diff)