#dev 2016-11-15

2016-11-15 UTC
#
gregorlove.com edited /template (+1173) "/* Open Source Examples */ ProcessWire description" (view diff)
#
tantek whoa
#
gRegorLove whoa?
#
@nsureio //No Comment - TV Control, Geolocation & Webmention APIs - iProgrammer http://news.google.com/news/url?sa=t&fd=R&ct2=us&usg=AFQjCNGcHRfTPuukFpnJ_n589uvrjNyX7g&clid=c3a7d30bb8a4878e06b80cf16b898331&ei=sV0qWPjvIY3zugLw3YPYBA&url=http%253A%252F%252Fwww.i-programmer.info%252Fnews%252F81-web-general%252F10264-no-comment-tv-control-geolocation-a-webmention-apis.html (twitter.com/_/status/798329302458585088)
#
tantek I mean, like lots of content
#
tantek.com edited /js;dr (+82) "js;dr in print! (article)" (view diff)
tantek, KevinMarks, cweiske and gRegorLove joined the channel
#
gregorlove.com created /live_streaming (+23) "r" (view diff)
#
gregorlove.com created /video_streaming (+23) "r" (view diff)
#
gregorlove.com edited /2014/Cambridge/Live (+267) "moving content from /livestreaming" (view diff)
#
gregorlove.com edited /livestreaming (-321) "r to /streaming. Cambridge 2014 content copied to /2014/Cambridge/Live" (view diff)
#
cweiske aaronpk, is there anything I can do to make it easier for you to merge the chat patches?
KevinMarks joined the channel
#
www.svenknebel.de edited /live_streaming (+501) "create as standalone page" (view diff)
#
www.svenknebel.de edited /livestreaming (+5) "move redirect to *live* streaming" (view diff)
#
gregorlove.com edited /streaming (+21) "/* See Also */ live streaming" (view diff)
#
gregorlove.com edited /live_streaming (+38) "see also" (view diff)
#
www.svenknebel.de edited /streaming (+95) (view diff)
#
www.svenknebel.de edited /live_streaming (+176) "/* IndieWeb Examples */ barnaby" (view diff)
#
www.svenknebel.de edited /live_streaming (+127) "/* Silo Examples */ youtube, facebook" (view diff)
KevinMarks_ joined the channel
#
cweiske.de edited /search (+255) "/* Software */" (view diff)
#
cweiske.de edited /search (+94) "/* Christian Weiske */" (view diff)
#
cweiske.de edited /discuss (+72) "/* Chat */ link search" (view diff)
loicm joined the channel
#
adactio.com edited /events/2016-11-16-homebrew-website-club (-47) "/* Where */" (view diff)
#
tyler.cat edited /live_streaming (+83) (view diff)
#
vanderven.se martijn edited /events/2016-11-23-homebrew-website-club (+19) "/* Nürnberg */ (Surprise) attendance update." (view diff)
tantek and KartikPrabhu joined the channel
#
ben.thatmustbe.me edited /2016/MIT2/Guest_List (+288) "/* RSVPs from other sites */" (view diff)
#
ben.thatmustbe.me edited /2016/MIT2/Guest_List (+0) "/* Participants */" (view diff)
#
ben_thatmustbeme interesting bit I came to when working with pubsub, I was planning to extend my hub to give the option to receive different formats from the pages (the hub would process it into a json doc if you specifically requested that when signing up)
#
ben_thatmustbeme but the spec specifically says that the format must match that of the page to which people are subscribing
#
ben_thatmustbeme aaronpk: think thats fine to do as an extension though?
#
aaronpk what do you mean "when signing up"?
#
aaronpk if I'm a random subscriber and I come across a website that advertises its hub, I expect that hub will behave the way the spec says, and that I'll get the notification in the same format as the topic URL. Without that, we don't actually get interop in the spec.
#
aaronpk now if you're talking about making something like superfeedr which lets you subscribe to arbitrary URLs whether or not they support PuSH and link to a hub, that's totally outside the spec and you can do whatever you want.
loicm joined the channel
#
ben_thatmustbeme i was thinking, by default, send the same content
#
ben_thatmustbeme but can still sign up to other sites
#
ben_thatmustbeme and even be a client to other sites, where it will sign up to their hub for you
#
ben_thatmustbeme so more like superfeeder i guess
#
aaronpk i don't know what you mean "sign up to"
#
aaronpk subscribe?
#
ben_thatmustbeme but when subscribing to a url, add in "format=mf2"
#
ben_thatmustbeme or rather hub.format=mf2json
#
ben_thatmustbeme is what i meant
#
ben_thatmustbeme but then it guess messy if the page coming back doesn't have mf2, or isn't even html
#
ben_thatmustbeme blah, i guess it gets a bit too messy
#
aaronpk it doesn't make sense to do that for generic hubs unless it's part of the spec
#
aaronpk otherwise you can't guarantee a hub is going to understand whatever you send it
#
aaronpk but yeah if you're making a tool that lets you subscribe to arbitrary URLs then you can do whatever you want because that's not PuSH
#
ben_thatmustbeme the idea being that it will operate as a generic hub if thats all you want to use it for
#
ben_thatmustbeme but if you want to use it as your only place to subscribe, it will basically offload the push subscribing and such for you
#
aaronpk the "you" that can use a hub as a generic hub is only the owner of the website, since it requires the website delegates to a specific hub.
#
ben_thatmustbeme yes
#
ben_thatmustbeme any website owner could still delegate to is as their hub
#
aaronpk honestly i would start small with this rather than trying to build up something as complicated as superfeedr
#
ben_thatmustbeme any subscriber would successfully use the spec to receive push updates from the hub
#
ben_thatmustbeme thats really the only part that would be complicated, but I think you convinced me to start small
#
ben_thatmustbeme am definitely including webmention as a way for publisher to notify the hub still though
#
ben_thatmustbeme that way a rel=hub link in the html, and salmention will basically take care of notifying the hub of every page update for me
#
aaronpk it just so happens that the publisher notifying the hub of new content isn't part of the spec, so that works :)
#
ben_thatmustbeme i guess it was a question of "if adding extensions, is it ok to overrite parts of the spec so long as they don't harm interop"
#
ben_thatmustbeme i think we actually do that with return codes for webmention + vouch
#
ben_thatmustbeme i'd need to double check that with the most recent spec though
#
ben_thatmustbeme actually, we definitely do since the spec says nothing about "reply with" responses
tantek and cweiske joined the channel
#
cweiske aaronpk, is there anything I can do to make it easier for you to merge the chat patches?
tantek joined the channel
#
tantek.com edited /MediaWiki:Sidebar (+10) "Brighton" (view diff)
#
aaronpk cweiske: sorry i'm just behind on things. let me take a look again
KevinMarks joined the channel
#
calumryan.com edited /events/2016-11-16-homebrew-website-club (+0) "/* Where */" (view diff)
#
aaronpk cweiske: merged and deployed
KevinMarks, rMdes, KartikPrabhu, KevinMarks_, Zegnat and gRegorLove joined the channel
#
cweiske aaronpk, great
#
cweiske now we have prev/next buttons for phones directly in the chat list which makes it so much easier to switch between days
#
cweiske no need to open the menu anymore
KevinMarks, loicm and pfefferle joined the channel
#
pfefferle good morning
#
gregorlove.com edited /2016/MIT2 (-12) "s/indiewebcamp.com/indieweb.org/" (view diff)
#
gregorlove.com created /2016/MIT2/Demos (+312) "initial demos page" (view diff)
#
gRegorLove There's been some mixed naming of IndieWebCamp MIT / Cambridge, heh
#
gregorlove.com created /2016/MIT2/Introductions (+1439) "initial page" (view diff)
#
gregorlove.com edited /2016/MIT2 (+622) "/* Schedule */ +Participating section" (view diff)
#
gregorlove.com created /2016/MIT2/Sessions (+402) "stub" (view diff)
#
gRegorLove !tell tantek Noticed with 2016/LA and 2016/MIT2 the pages didn't have the Participating sub-section which links to the code of conduct. Should make a note somewhere to ensure that's included on IWC pages.
#
Loqi Ok, I'll tell them that when I see them next
#
gRegorLove !tell tantek I updated it on https://indieweb.org/IndieWebCamps#Before
#
Loqi Ok, I'll tell them that when I see them next
KartikPrabhu joined the channel