#barnabywaltersjust realised there’s no subtome wiki page — starts writing a stub
#julien51So, yes, when I read your proposal, I found it very similar to what we had designed for PuSH 0.4. The bad news is that we're struggling to get adoption
#julien51But the good news is that I recently heard from folks at Google who said they're adding support for it to their hub
#tommorrisjust saw that Google Analytics includes a thing it refers to as "trackbacks" - a way of finding backlinks from referrers
#waterpigs.co.ukcreated /subtome (+251) "Created page with "{{stub}} SubToMe (Subscribe To Me) is a button content publishers can put on their sites which enables users to subscribe to their feed in whatever reader they choose — sort o..."" (view diff)
#barnabywaltersjulien51: ^ I created a stub — you can log in to the wiki right?
#julien51to test, (while chat still works!) add "notifixlite@appspot.com" to your list of contacts in an XMPP client
#julien51and then say /hello to notifixlite@appspot.com :)
#julien51thanks for the SubToMe page. I'll add stuff to it right away
#waterpigs.co.ukedited /PubSubHubbub (+456) "/* Testing */ expanded testing section, added link to notifixlite and mention some XMPP providers" (view diff)
#julien51jaso the project page is not up to date because Googlers only have access to it :/ and the messages are quite old
friedcell joined the channel
#jasoso the future of push is in the hands of google?
#julien51cweiske : we heard a lot of good things about it too. We would love for it to work with http://subtome.com, do you know if there is a page where you can add new feed url that would accept a query string to pre-fill the feed url?
#barnabywalterscweiske: sure, URLs can handle custom schemes — but no browsers I know of allow you to pick from a list of eligible apps when you go to one of those scheme URLs (as subtome or webactions toolbelt do)
#julien51we want to introduce an 'API' to avoid one redirect so that the SubToMe button itself calls (jsonp!) the subscribing application directly to perform the subscription
#tantek!tell julien51 welcome back! sorry to miss you in the channel. webactions better for publishers since no script is needed. also, have documented "webintents" problems since 2011, their death shouldn't have been a surprise.
#tommorristantek: I'd question whether Wikipedia has a liberal TOS. it's got an honest one which basically boils down to "we give a shit about your privacy and have strict rules about what we do with your personal information, and if you are dick we might ban you"
#tommorrisbut it's a long way from a Facebook-style TOS ;)
#cweiskethe git repositories themselves are clonable of course - that's the nature of git
#cweiskebut the meta data that github collects around them is siloed
#cweiskeand that meta data are the data that make github usable and worthwile
#tommorrisa while back, for work, I had to write a load of custom script crap to transfer from Redmine to Bitbucket. code-repository stuff isn't as portable as it ought to be.
#tommorriswe're all Atlassian'd up here: JIRA, Confluence (which is terrible), and now Bitbucket.
#tantek.comedited /commons (+402) "/* Popular Commons */ note github criticisms from cweiske on IRC" (view diff)
#barnabywalterswow, the bitbicket subdomain thing is retained even in internal links?! nice
#tommorrisbarnabywalters: yep, they've done it properly
#tantek.comuploaded /File:twitter-home-in-stream-reply-context-thread.png "screenshot of Twitter home page stream fragment showing a tweet followed by an @-reply tweet that by default shows a reply-context of the person being replied to with smaller icon, and original text being replied to, same font, just slightly smaller text size for the original tweet, and above that, the precedeing thread, "View 3 more tweets", vertical ellipses up to the original tweet."
#tantek.comedited /reply-context (+237) "/* Twitter home page */ twitter home page reply-context of a reply-thread, ellipsed/collapsed display" (view diff)
#tantek.comuploaded /File:twitter-home-in-stream-reply-context-tweets.png "screenshot of Twitter home page stream fragment showing an @-reply tweet that by default shows a reply-context of the person being replied to with smaller icon, and original text being replied to, same font, just slightly smaller text size for the original tweet, and above that, the immediately previous tweet that was the start of the thread."
#tantek.comedited /reply-context (+180) "show reply context with @-reply, what it's in response to, and the start tweet that that is in response to" (view diff)
#tantekfeel free to document that as a criticism on that page if you want
#waterpigs.co.ukedited /reply-context (+382) "/* Twitter home page */ added comment on the constant flipping of the directionality of time on twitter.com" (view diff)
#barnabywaltersactually that probably opens up the possibilities for a whole other sort of twitter-humour
#barnabywaltersconversations read backwards making more sense than they originally did
#tantekmaybe that's why I prefer IRC for conversations also. interesting.
julien51 joined the channel
#Loqijulien51: tantek left you a message 1 hour, 30 minutes ago: welcome back! sorry to miss you in the channel. webactions better for publishers since no script is needed. also, have documented "webintents" problems since 2011, their death shouldn't have been a surprise.
#_grawityfrom top to bottom, except for things like this :P
#barnabywalters_grawity: well, consider Loqi’s !tells as very much delayed messages :)
#barnabywaltersit’s unlikely that the answer to a delayed question would ever appear above the delayed question its self
hober2, tantek, spindritf, tommorris, bret, reidab, spinnerin, barnabywalters, aaronpk, lion-, jaquecoustaeau, termie_, pdurbin, elf-pavlik, marjolein, josephboyle1, Nabil, Garbee and termie joined the channel
#julien51Absolutely no script is required by any publisher to use SubToMe. Also, SubToMe is browser agnostic (it's web based!), and has already been implemented by many feed readers. But I guess you could also *wait* for another couple years before something happens :) I decided to move forward to make something that works without compromising the future.
jfranusic and scor joined the channel
#tantekjulien51 - that is *great* to hear. thanks for the clarification.
#tantekreally appreciate that you made it work without script. seriously, well done.
cweiske joined the channel
#tantekand +1 to decided to move forward to make something that works without compromising the future.
#@sandeepshettyBlogging was all HTML. Social networks are all plaintext. Something to think about. #indieweb #fedsocweb
#tantekJonathanNeal - we seriously need to start a colophon.txt parody
#tantek(since that's what they're *actually* posting)
EdwardHinkle, hadleybeeman and sandeepshetty joined the channel
#Loqisandeepshetty: barnabywalters left you a message 8 hours, 57 minutes ago: RE webmention on WPC — oops, looks like I forgot to implement that yet! coming soon :)
#Loqisandeepshetty meant to say: julien51: while I'm caching up and since you are here would love see some comments from you here: http://indiewebcamp.com/push-vs-pull
#julien51sandeepshetty: I don't agree with a lot of things in there :/ How should I comment?
#sandeepshettyHomepage has a singin with your domain link at the top right... you need some very basic rel="me" stuff to make it work...
#julien51ha, I know how to use the wiki, but I don't want to put all my comments in there
#julien51when you say pull is simple for publishers, it's actually not accurate. It "appears" simple, and yet that's pretty hard to handle. For example, at some point, almost 40% of Tumblr's traffic was consumed by search engine. That's not *easy* to handle
#grawitythis is partly out of curiosity (I'm interested in the reasons behind decisions), and partly because I want to log in to the wiki with such an address :)
#julien51sandeepshetty I think you're generally missing the point and comparing apple and oranges…
brianloveswords joined the channel
#sandeepshettyok done checking the diff.. lots of stuff to discuss, I wonder if I should do it here or just add to the wiki...
#sandeepshettylet me start here and then I'll move to the wiki :)
#julien51sandeepshetty: up to you, but I don't have a lot of time ahead
#sandeepshettyin that I'll just add stiuff to the wiki and prefix your comment with julien51 and mine sandeepshetty so it's clear who is saying what...
#tanteksandeepshetty - however, foo.example.com/bar may be a bit too little indie, especially if example.com is shared not individual
#sandeepshettytantek: I agree it feels a little less indie... have to admit I haven't thought too much about identity URL ownership...
#sandeepshettyI've always wanted to "own" my domain and never considered using subdomains or paths...
tommorris joined the channel
#grawitytantek: my guess is lazy admins (they go through the backlog only several times a year) plus the requirement to have at least two existing nameservers
#sandeepshettygrawity: what's the reason you want to use the ~grawity and not buy your own domain?
#grawity(it has existed since 1995 though, so I assume they have ways of dealing with it)
#grawitysandeepshetty: well, the domain (nullroute.eu.org) *is* mine
#grawitysandeepshetty: but there's more in it than just my personal site
#bretgosh darnit. wy did .tc have to go up to $119 :(
#tantekgrawity - when you say "mine" - it's not clear how to trust the benevolent nature of eu.org moving forward. at least with domain name rental services you there's a well-understood profit motive / customer service to not screw people over.
#sandeepshettyjulien51: Couple of things: I was comparing push vs pull not PuSH vs pull
#sandeepshettyPuSH is interesting because it's a mix push and pull
#julien51sandeepshetty: well you explicitly wrote that "(PuSH was designed by Google engineers to solve their problems with aggregation and not solve the problems of the subscriber - which is a central actor on the indieweb)."
#sandeepshettyalso the security stuff in required by default with push and not with pull because the publisher doesn't care who is subscribing
#sandeepshettyalso some of the advantages of hubs in PuSH can be had in pull by publishers delegating to an aggregator
#grawitytantek: at first look it's a stable one (it was itself created as a protest against registrars trying to screw people over, and the owner later founded gandi.net)
#sandeepshettyhttps + valid cert is a lot different than having to do crypto stuff like signing
#julien51not really, in both cases you can use libraries to do that on your behalf. It's just that we all forgot how it's done for https and valid certs since we used these libraries, but my point is that you can't say "security is complex in push" and just plainly ignore that it is complex on "pull" too.
jfranusic joined the channel
#sandeepshettynot really, a publisher *has* to confirm subscriptions from subscribers to avoid the attack vector. you don't have to do that with a pull.
ShishKabab joined the channel
#julien51again, not sure what you're comparing? I though you were not comparing PubSubHubbub? That's a pubsubhubbub thing.
#sandeepshettyand a subscriber just has to access the fee url over https with pull while with push there has to be some mechanism to share a secret and then use that to sign the payload and then the subscriber has to check the signature
#sandeepshettyany push/webhook will *have* to do something like that... irrespective of PuSH to avoid the attack vector and confirm origin
#julien51"just access the free url over https" is actually quite complex but hidden from you because you used libraries to do that. There are libraries who do the same for you with PubSubHubbub.
#julien51sandeepshetty: sure, in the same way that CURL has to perform the SSL handshake and check the validity of the cert chain.
#julien51well, great point then! no need to do all these untrue arguments to come to it :)
#sandeepshettyand my guess is that for indieweb stuff you might not need push.. but I could be wrong (like many other situations in the past)
#breti have an idea for subdomians... if i share a domaing of my last name with my family, having a subdomain of my first name would be a valid use case
#julien51sandeepshetty: please do also come up with data when you make your statements like "simple publisher.", or "* better for frequent updates because they are grouped together." because the data have shows the exact opposite, I'd love to learn from you!
#tantekespecially with the real world example given by sandeep!
#bretok tantek i have the tabs open i need to eat though
#tantekjulien51 - take it at least as evidence of the lack of (or just plain dead) community around PuSH / push
#tantek(what happens when your mailing list is your "community")
#sandeepshettyjulien51: I did plan to run some test... will publish some no. when I have them..
#julien51tantek: who said the mailing list was the community? you? where should PuSH be where it's not?
#tanteknot on a dead-end google silo that's for sure
#tantekjulien51 - the default in the past 5 years of "social/federated web" crap is "email list = community". everyone "says it" by doing it - creating a new google group for whatever.
#tantekPuSH, ActivityStreams, OpenSocial, PortableContacts, WebFinger - need I go on? All email-list centric "communities"
#julien51tantek: I don't think you can measure the usefulness of something with the number of comments on a mailing list… I'm worth you and I'm tired of people discussing things in mailing lists (or IRC channels for that matter) I look at implementation. PubSubHubbub is present for a huge number of feeds. That's a fact which is far more interesting to me than X people discuss it on an obscure IRC channel :)
#tantekjulien51 - present is good but mostly inertia. lack of a healthy community means a standard dies.
#tantekor gets replaced by something better (simpler?) that *has* a healthy community
#julien51tantek I don't agree with that. Sometimes things are good. If nobody moves them forward it's probably because nobody knows (yet!) where to push them forward
#tantekyou're welcome to bring the implementation-centric discussions around PubSubHubbub here to IndieWebCamp as a lot of us *are* supporting it and think it's a good thing - we have pages on it :)
#julien51I love the indieweb community (and you know it), but I don't think it's anything in terms of success/adoption compared to what we achieved with PubSubHubbub.
#tantekjulien51 - that may be (nobody knows (yet!) where to push them forward) - but then that means it's vulnerable to a bigco forking and pushing it forward proprietarily
#tantekjulien51 - I'd say realtime federated comments are a bigger end-user relevant achievement than anything PubSubHubbub has achieved.
#julien51tantek: this is exactly why I cam here… but i have't heard anyone tell me how we could make PuSH better. I heard/read uninformed statements like "simple publisher." or " implies your site cannot be static.".
#tantekand I'll point out that PuSH was not used for the notification protocols
#tantekessentially we finally created and established a decent presentation layer for pingback
#julien51ha, that, yes, I read it and it's indeed amazing (maybe the only reason why I'll rewrite ouvre-boite.com), but it also reminds me of SWAT0 a couple years back where Bounds and Prodroumou and Googler demoed the same thing with Identica, cliqset and google buzz.
#tantek10 years after the pingback spec was published with nothing but hints for a horrible presentation - which got implemented and never re-designed
#Loqijulien51 meant to say: tantek: we'd need to ask evan, but I'm sure there was at least another couple impls that 'worked' but were not used. Was it rstatus?
#tantekalso - a big realization from the temporary achievement of SWAT0 was that silo implementation are pretty worthless over the long term
#julien51we also need to stop trying to be nobel prizes. The open web community is full of people who think that whatever everyone else did is crap and that *they* alone will make something better and change the world
#julien51Honestly, there is not a week where somebody comes to me/superfeedr and says, we're doing this new federated social web thing and it's better than what you did, please support it and tell the hubs you host (Tumblr…) to do it.
#tantekjulien51 - that's hilarious: "there is not a week where somebody comes to me/superfeedr and says, we're doing this new federated social web thing and it's better"
#julien51that's my point: if you want others to work with you, work with them!
#bretI was just happy to get rid of all the proprietary logos from my IM account list and use only xmpp for a good 5 years. i still had to maintaint 4 or 5 xmpp accounts, which was slightly better at the time, seemingly.
JonathanNeal joined the channel
#bretI'm trying to introduce folks my department to start idling/participating in irc. Portland state has their own irc server :)
#julien51as for POSSE I'm sure you were still logged in on Fcebook and twitter all the time. You had a point to make, but most people would not spend more than a day posting on their own site with POSSE if they figure out that they can just do it directly on Twitter/FB
#tantekI have not replicated *all* functionality from FB/Twitter to my own site no, but that's a strawman.
#tantekI have not posted directly to FB/Twitter since 2009.
#tanteksince 2010 all my Twitter posts are from my own site.
#tantekjulien51 what do you mean by "Dogfooding alone is self inflicted ban-hell" ? that doesn't make any sense nor does it match *anyone's* experience here.
#tantekeverytime someone here selfdogfoods, they end up aggressively improving their implementation. EVERY. TIME.
#tanteknot true with all the handwavy "hey everyone you should do this" efforts
#tantek"hey everyone you should install my project that I won't even install myself on my own site"
#julien51tantek: I mean that posting to your own site that no one reads quickly becomes really hard to use. People post to twitter or Facebook because other people follow them there.
#sandeepshetty!tell julien51: I've updated the wiki page with my comments. BTW, except for the one instance you mentioned nothing about the push section was about PuSH.
#bretIts super easy to add PuSH to a static site, but there are some technical issues with the way github handles their post commit hooks that cause some misalignments
#sandeepshetty_He mght... there's always twitter and the pubsubhubub mailing list though.
tilgovi, jfranusic and scor joined the channel
#bret!tell julien51: I would love to ask you a few questions about using superfeedr as a PuSH hub for github pages + post commit hooks next time you are on
#tantekand what an amazing set of people have signed up!
#tantekin general, any project that claims to be federated/social/indie web-like is probably something we should critically document on indiewebcamp.com since Wikipedia sucks so bad at that topic area in particular.
#tantekif some wikipedian later wants to copy/reference our CC0/PD text, more power to them
#tantekbut let's create where we won't get hassled/trolled/griefed by deletionists/mergists/relevancists