#aaronpkI believe it means using social networks and other social technology inside a business
#tantekis going through that page and creating stub/definition pages on the indiewebcamp wiki to try to help with understanding terms/phrases and their relation to the indieweb
#aaronpki have not yet seen that term outside the w3c page, but the idea is not new
#tantek.comedited /social-business (+650) "add other definitions of social business - clearly means different things to different people / contexts" (view diff)
#benwerdPondering IndieWeb Hangouts using Webmention to initiate the call request and a Node.js / Holla install to actually make the video / audio happen.
#benwerdReally like the idea of using authed webmentions for notifications between servers regardless.
#tantekok I've written a function to pull my old style "in-reply-to: http://example.com/post" inline text references into actual reply-contexts with rel=in-reply-to etc. links
#shanersaaronpk: ZenText currently has a malformed .gemspec. are YOU requiring it or do you know which of the gems are, by chance?
xtof joined the channel
#shanersaaronpk: i just needed to update my rubygems install
xtof joined the channel
#aaronpkzentext? not sure. also I just realized I haven't done bundle install on that in lik 1.5 years so who knows what versions of gems there are now
#Jihaissepfefferle: in sempress, is there is a reason for showing a thumb square image of the "Image a la une" for all post types except for the post ?
#Jihaissedon't know in english how this image is called...
#pfefferleyou mean the little icon at the left of a post?
#pfefferlethe reason is that the other post types have less text in common… so i thought it would be good to show a smaller image… do you prefer a full version?
#SRCRI have an IndieAuth question, what would you suggest as being properly authenticated, the HTTP 200 is good enough or should I also do something with the JSON i get back?
#aaronpkSRCR: you have to check the JSON that comes back in order to know *who* logged in
#aaronpkotherwise you just know that someone logged in but not who
#tantekbenwerd - indeed, subscribe to indie h-entry updates
#SRCRaaronpk: well I also get it back in the URL, but best would be to get it from the JSON i agree thanks..
#aaronpkyea you get it back from the URL so you know which indieauth server to use to verify it
#aaronpkso that people can delegate to other indieauth servers
#aaronpkSRCR: so for example if bret.io logs in, he'll be redirected to your site with "me=bret.io" in the URL, you'd go check the bret.io home page and look for rel="indieauth" and use the server pointed to there to verify the code
#tantekimagine you changed your permalink URL structure at sometime in the future, but left redirects in place for your existing permalinks, you'd still want to receive webmention updates to them right?
#aaronpkthe development process. the redirect issue occurred to me while I was building it, but I chose to gloss over it instead of overthink it in favor of getting something working
#aaronpknow I also need to go implement the webmention verification step (including looking for redirects) on an async queue, because checking all those redirects would take too long on the http post
eschnou joined the channel
#aaronpkinterestingly, processing that on a queue means the only response my webmention endpoint would ever return to the POST request is a "202 Accepted". I would never have the opportunity to respond with an error.
#aaronpkit's like I tell you "Hey X just linked to Y", and Y redirects to Z. You say "really? let me check if X linked to Y" and then look for Y on the page. you don't need to look for Z
#tantek.comedited /webmention (+207) "/* Protocol Summary */ clarify what source and target are set to, and precisely where redirects must be supported" (view diff)
#aaronpkall the more reason for me to turn webmention.io into a webmention client anybody can use, heh
#tantekaaronpk - shall I try sending a webmention to you now and see at what point it fails? ;)
#aaronpkso assuming I move this to be processed on a background queue, which I will do for a number of reasons, the only response I can return is "202 Accepted" even for invalid links
#tantekfor protocols like webmention to scale they have to be asynchronous, which means you can't really return much state information
#aaronpkshould we even bother documenting error codes to return then? why not just require the response to be "202 accepted"
#tantekI suppose the only errors we can return are for malformed webmentions, e.g. missing/invalid source param, missing/invalid target param - where invalid means invalid URL
#tantekaaronpk - nope, HTML5 rel values are officially registered on the microformats wiki. The HTMLWG tried an experiment with using IETF/IANA and it was so much of a pain that the alternative of using an open wiki won out :)
#tantekaaronpk - I agree with the asynchronicity and queuing, however, ideally we'd like webmentions to work fairly realtime - similar to silo-ux of leaving a comment and having it show-up others' view of the same post.
#aaronpkagreed, but it's not always practical or advisable to handle all that processing in the actual HTTP POST thread
#aaronpkmy queuing system grabs jobs as soon as they are inserted, so to the outside world it appears instant anyway
#barnabywaltersaaronpk: is forking processes a potential way of removing the need for a queue?
#barnabywalterswhen I eventually move things async I’m probably just going to either call it via an AJAX request or just make the request on the server side and then immediately close it
#benwerdbarnabywalters: I use (not for idno) a signed HTTP request method for dealing with asynchronous processing, which also has the benefit of (1) being able to execute on other servers (2) not necessarily needing a queue
#aaronpkbarnabywalters: I can share my setup for php queuing with you. it's pretty simple actually
#benwerdat the point where you want to launch something, a cURL request is made to the script, via actual HTTP. (You could even do this via webmention.) The signing is for authentication to prove that it's a safe call
#aaronpkbut that hangs the requesting thread open right?
#benwerdyou can flush the HTTP response in PHP and continue working after everything's been sent to the browser.
#benwerda little string and blu-tack, for sure, but it works
#aaronpkoh, well that only solves half your problems
#barnabywaltersaaronpk: sure, I’d be interested in knowing how you handle async stuff
#aaronpkunless you send a connection: close header an http client will still keep the connection open. and either way you end up with the server maintaining the resources it used to handle the request.
#aaronpkbarnabywalters: sure, I can do a little post about it
#benwerdI do send a connection: close header. but point taken about the resources
earplugs joined the channel
#aaronpkand of course handling one request at a time isn't going to ever cause a problem, but get any sort of traffic on it and it'll fill up ram fast
#benwerdright. it's not for massive scale, for which you really do need queues etc etc
#tantek.comedited /webmention (+993) "number protocol summary steps, stub Implementation Notes with some discovery and redirect details" (view diff)
#aaronpkthe other thing this queue gives me is I can run the web server as the "apache" user and run the queue as the "aaron" user and I don't need to give apache write permissions to anything
#tantekaaronpk - another thought for target URL verification - if URLs "typically" on your site support receiving webmentions then you could just check to see if it links to your domain or your short-domain
#aaronpki think that gets you most of the way there, but it still doesn't catch the t.co case
#tantekand that would provide a very visible federated advantage to app.net over Twitter
#tantekwould make for a more impressive app.net demo
#tantekthe way to get Twitter to change isn't to ask Twitter directly (they're too big for that)
#tantekit's to get every other player smaller than them to adopt what you want and get others to talk about how the other smaller players are doing a better job
#tanteklet me know when you think that's been done and I'll try resending the webmention
shaners joined the channel
#aaronpkcool. probably won't be able to get to it tonight.
#tantekaaronpk - no problem at all. took me long enough to implement in-reply-to support for my old posts :)
bnvk joined the channel
#tantekI went through my old posts, and the only Falcon posts where I have in-reply-to: replies to indie domains are that one to aaronpk's post, and this one http://tantek.com/2011/010/b1/owning-your-data to zeldman.com
#tantekonce sending this webmention is working, then implementing better reply-to-indie-web posting flow is next on my list
#tantekso I can start properly posting replies to all of your awesome indieweb posts (e.g. eschnou's original post that's aggregating indieweb comments).
#bretWas their much discussion about indieweb commenting before eschnou's thread?
#aaronpkyea, I led a discussion on it at last year's camp
#aaronpkalso I set up pingback.me to help make it easier to build, before sandeep came along and simplified the whole thing by rewriting pingback as webmention :)
#barnabywaltersI managed to dig out some ancient backups of my website earlier today
#barnabywaltersI’m going to re-import some of my original “notes” in to the current wpc