#tantekkylewm: that's a tough decision. man, sorry to hear that j12t, but brave, and hopefully we can figure more things out in this community to help you iterate.
#aaronpkj12t: kudos for calling that early and not letting it drag on
#tantekit's very likely I'll be in NYC on 2014-06-04. Any other NYC folks here who would be interested in a late night HWC drinkup/meetup? like from 20:30-22:30 EDT (thus synchronized with the PDT meetups?)
#GWGtantek: If I wasn't going to be out of town....
#j12tThanks for all the nice words. Worst thing is to have a successful campaign that successfully lead into the wrong spot. Didn’t want to be there ...
#j12tI’m actually more confident now than going in, because now I know a lot more about the state of the market.
#KartikPrabhuaaronpk: yeah well thanks :P I mean what parts need to be there... I suppose I need to have some sort of authentication do-dad..
netweb joined the channel
#aaronpkKartikPrabhu: try signing in, it should walk you through all the steps
#KartikPrabhuhmm oh i understand. just do all steps that Quill does...?
#aaronpkQuill is a client, and if you try to sign in, it will tell you all the things you need to do to support it
#aaronpkSo if you look at the doc pages you should be able to implement the same things it does to make a client
#bnvk1barnabywalters: so if I currently have <a class="p-author h-card">John Smythe</a> and I want to add the u-uid for user, is <a class="p-author h-card">John Smythe<span class="u-uid">21123234123</span></a> OK?
#bnvk1or does the "John Smythe" need to be wrapped in something as well since I'm adding a child?
#tantekthe "have no time" issue is a key one - indieweb software needs to be zero admin - it should "just work" and not require updates if you're ok with current functionality
#tantekis skeptical about the auto-update methodology too due to things quietly breaking.
#j12tBTW, the “private messages” stuff recently discussed is also eerily similar to what we had in LID for URL-to-URL-based encrypted, signed messaging
#KartikPrabhutantek: I think the author is arguing more about money going to writers on the Web or something. Just like you would buy a book in real life
#tantekI provided a simple analogy to an existing ecosystem/adoption pattern that proves that payment to publishers is *not* necessary for widespread adoption
#tantektherefore demonstrating the author's assertion of *need* to be false
#KartikPrabhukylewm: no. I just found out about this a few days back. link?
#gRegor`@joeld is his twitter name, actually. I'm an internet acquaintance of his and have mentioned indieweb a few times. I'll suggest he check out the chat sometime.
#tantekanyone talking seriously about selling something on the open web, or creating protocols for doing so, should be *at least* attempting to do so with existing tech first
bnvk joined the channel
#tantekor providing critique of why existing tech does not work for them
#gRegor`Is Firefox Marketplace YAAS? (Yet Another App Store) :)
#tantekso that's my summary dismissal of this article. go do your homework before proposing additions to HTTP.
#kylewmKartikPrabhu: I haven't listened yet... http://thechangelog.com/123/ I learned about gittip from an interview he did with them last year though. interesting guy, kind of an iconoclast
#tantekgRegor`: all based on open standards, so you can actually make your own app store at your own domain
#KartikPrabhutantek: I am curious as to why some of these "marketplaces" are widely known but others aren't. Had never heard of FF marketplace before
#kylewmKartikPrabhu: @Shanley blasted him on twitter last week, interesting read
#KartikPrabhuso Gittip is like a money-exchange silo
#barnabywalterstantek: as far as I’ve seen, the firefox marketplace and associated standards are designed for packaged apps. how would one use it/them for buying/subscribing to content?
#tantekand perhaps see if you can get joeld to join us here in #indiewebcamp
#gRegor`I get tantek's overall point about payments, but I'm not sure I follow the SMS coronary. We do pay for the content, just not directly to the person providing the content.
#LoqigRegor` meant to say: I get tantek's overall point about payments, but I'm not sure I follow the SMS corollary. We do pay for the content, just not directly to the person providing the content.
#tantekbarnabywalters: advantage your personal "web app" could provide - local caching of say all your blog archives so people could read everything you wrote offline.
#barnabywalterstantek: can that not be done from a regular website anymore?
#tantekof course it can, but why not try charging for it (since it's extra work for you) and see what happens?
#luxagraftantek: well, i was assuming if something were done at the protocol level, as per that article, it would be easy to implement otherwise yeah, no advantage over today
#tantekaaronpk - for each indiewebcamp, e.g. /2011 it can have an expenses page, e.g. /2011/expenses which documents all expenses paid by whom for what
#tantekluxagraf - of course there are exceptions (hence *almost* never true), but that's not the point. preponderance of data (e.g. # of protocols) are *not* easy, not even close to, to implement
#barnabywaltersaaronpk: I tend to just use a simple normaliser and work from there rather than trying to learn large frameworks and figure out how to fit my brain-pictures into their assumptions
#aaronpkbarnabywalters: I don't really have brain-pictures, I just want to get it out on the page and not have it look like the default browser css
#tantekaaronpk, /expenses is a good start! but needs payer / payee columns
#luxagraftantek: agreed. i think the whole argument is wrong anyway.
#tantekluxagraf - also, it fails the "scratch your own itch" test
#tanteki.e. want to solve payments on the web? great, put up your website into an appstore for pay to try it out and document the results.
#jonnybarnesbarnabywalters aaronpk I'm stealing the term brain-pictures, thats fantastic :P
#barnabywaltersaaronpk: I’ve found that it generally only takes a hundred lines or so of CSS to bridge the gap between nasty browser defaults and looking-okay
#aaronpkbarnabywalters: you should share those hundred lines :)
#jonnybarnesluxagraf: I imagine its something wrong with your config, could be that TLS1.2 is getting disabled somewhere, maybe in the main http block
#tantekanyone proposing stuff for web architecture but not actually experimenting with it on their own site (or at least showing concrete steps to experimenting with it - i.e. for "harder" problems) is usually dismissable as hand-waving.
#luxagrafjonnybarnes: i had a great moment of hope yesterday when i moved all the https config stuff to the main config file, but unfortunately that didn't help.
#barnabywaltersaaronpk: I’m a little afraid of doing that, because I’ll look at different sites and say “hey, there are some similarities here, I just need to abstract this and this and this…” and then POOF, a new CSS framework is born
#luxagrafjonnybarnes: no. which might be the problem. i tried to figure out a way to linke nginx to a self-complied version, but could not figure out how to do that
#jonnybarnesand my site was defo ising spdy so nginx must have been using the self-compiled openssl
#jonnybarnesatm my site is on a vps with a new enough version of openssl in the repos so I didnt need to self-compile openssl
#aaronpkindiewebcamp.com for sure, and probably indieweb.org too. but how about webmention.io? or micropub.net? then there's also sandeep's webmention.org but I don't even know if he'd want that
#gRegor`Traveling tomorrow and decompressing Sunday :)
#jonnybarnesluxagraf: then in the output of ./configure you shoud see the line Using system OpenSSL library in Configureation Summary which is near the end of the output
#gRegor`joeld_: Tantek can probably best reply to your post. He was away in transit for a bit, but might be back.
barnabywalters joined the channel
#tantekis mobile right now and mostly listening. :)
#gRegor`joeld_: What was the service you were using to distribute your ebook in progress? I forget.
#joeld_tantek: so my question then is, are distributed little "app stores" somehow a better solution than including micropayment functionality in HTTP? Why do we need app stores?
#joeld_tantek: you're right that I'm talking without doing, because there currently is no way to do what I'm actually talking about
#joeld_tantek: so far I guess it feels as though I wrote an article on the minimum wage and you're berating me for not tipping buskers.
#luxagrafaaronpk: that's all wired does with old URLs
#joeld_I'm not saying there's no way to do "busking" on the web a la app stores or gittip or Patreon or whatever various little parties have put together. I'm saying it would be better for it to be handled at the protocol level.
#luxagrafjonnybarnes: well, it's definitely one of the the 3rd part modules, because compiling stock gets me an A- (I need better Forward Secrecy support I guess)
#barnabywaltersjoeld_: how might that be achieved? what’s the minimum functionality which would have to be added to HTTP to achieve your goal?
#tantekI'm saying you're not even trying busking yourself.
#aaronpkand well summarized in your post "The real source of this problem is that the open software and protocols that power the internet lack a crucial piece of functionality: the ability to set prices or accept payments for things."
#luxagrafjoeld_: that's awesome. I'd like to see it happen. but wouldn't good place to start be with your own site?
#aaronpkhowever I can think of at least a dozen ways I can set prices and accept payments for things
#joeld_tantek: also, subcompact publishers tried app stores. It was a quagmire precisely because there are too many of them.
#joeld_aaronpk: yes, that's the problem: there ARE a dozen ways.
#joeld_aaronpk: I'm saying, ideally, there would be one: HTTP.
#bnvkalso, not to mention the totally screwy-ness of Int transactions
#tantekI'm saying without at least trying existing deployed & adopted open web payment systems, eg by packaging & selling your own website, you likely lack the experience to back a claim like "at the protocol level"
#bnvkfor instance PayPal offers no ways to transfer money to Iceland
#joeld_credit cards and transaction fees are a huge obstacle here too.
#joeld_because they set a floor for prices that is way too high for most resources.
#tantekThat's not about making money for yourself. It's about gaining experience to use to make credible proposals. Without experience, proposals are just hand waving.
#bnvkin fact, the only way to accept credit card donations in Iceland is to 1 of the 2 local paypment processes who majorly gouge on fees
#aaronpkthe fact that it's an open market for payment processing has allowed companies like Stripe or Gumroad to come along and demonstrate a clean and new way of handling payments in the existing infrastructure. that's a good thing i think.
#joeld_tantek: you know Siskel and Ebert never made a movie right? ;)
#joeld_tantek: but I have experimented on storefronts like Kindle Publishing for Blogs, leanpub, etc. if that's worth anything to you.
#tantekThey never proposed how to make movies either.
benwerd joined the channel
#joeld_OK, I think I understand the objection that I haven
#barnabywaltersjoeld_: I had not heard of any of those, and would be interested to read about your (presumably negative) experiences with them
whaity joined the channel
#tantekProprietary experience counts too obv. But proposing open web protocols without even discussing existing open web protocols shows lack of research at best.
#joeld_...'t rebuilt a new HTTP implementation on my own
#aaronpkpopping up a level on this... frankly I think regardless of whether there ends up being payment extensions to http or whatever, there's still the more fundamental issue of fraud prevention and actually making money change hands that's not gonna be in http
#joeld_tantek: if I were proposing anything above Transport on the OSI model I think that would be a valid concern.
#aaronpkthe mechanics of moving money around is complicated enough that there are entire companies devoted to specific aspects of it
#aaronpkI guess I'm saying I don't see that addressed at all in the post. It seems to be kind of hand-waved at the end, with "As soon as you start attracting attention, change starts trickling in."
#joeld_aaronpk: in a perfect world, I would have included a satoshi-style white paper on the payment system. tbh I don't have one.
#aaronpkit seems too early to talk about adding payments to http when there isn't even a way to send small payments
#joeld_aaronpk: but in the article I'm trying to focus on the need for such a system and the implications of its being in place (or not), so even assuming I had a reference implementation it would be out of place here.
#aaronpkI definitely agree with the sentiment of the article
tantek joined the channel
#joeld_aaronpk: well there I think blockchain protocols are showing us [the/a] way forward
#tantekjoeld, I think another aspect was the focus on protocol first, rather than UX
#joeld_tantek: UX is definitely a consideration that deserves fleshing out more.
#tantekI mean, perhaps I missed something, but I'd expect to see a sketch of a UI flow of how micropayments could work without jumping to the conclusion that changing http was necessary.
#tantekI'm just wary of discussing protocols before UX
#tantekbut that's a newish principle/value that folks here in indiewebcamp are trying to practice / propagate
#tantekthat is, UX first, formats/protocols second
#joeld_tantek: my thought when writing it (and mentioned in the medium version) is that app stores have pretty much solved the UX aspects of this, which is possible in large part because they have direct access to your wallet.
#tantekI guess if app stores have solved the UX aspect, then that leads to the conclusion that one should at least *try* open web app stores before proposing anything
#aaronpkjoeld_: if what i'm imagining is your vision for this is correct, then it sounds like you want something that is nothing like the existing app store experience
#joeld_aaronpk: well OAuth is not something your browser handles, so no, I'm not really thinking in those terms.
#aaronpkbut your browser *could* handle it if it were built in to browsers
#joeld_aaronpk: ok I see what you are saying. Technically anything could be browser-handled yes, with extensions, e.g...
#jonnybarnesluxagraf: have you worked out which module is messing things up yet?
#aaronpkwith extensions until the browser builds it in eventually, yeah
#joeld_aaronpk: I'm talking about HTTP-level stuff though. HTTP handles GET and POST requests. Those requests should be able to include pricing information and payment details.
#aaronpkthe point is you can learn a lot about the best way to design a protocol by looking at what the end experience should look like
#aaronpkit's really tempting to jump into protocol design because it's so easy to do it when you don't need to worry about UX design
#bnvkaaronpk: have you written down your major gripes with Bitcoin / blockchains anywhere? All I remember you saying was the size of the public ledger being your biggest concern
#aaronpkbnvk: no I don't really want to get involved
#luxagrafjonnybarnes: None it would seem. When I started recompiling I also moved all my config files to focus on just the luxagraf rules. problem is in one of the other config files
#bnvkaaronpk: it's mighty interesting to me how interested you are in digital money, yet how anti BTC you are
#aaronpkbnvk: and that sentence is probably the online documentation that mentions me and bitcoin in the same sentence (except now this one too dammit)
#aaronpkthere are several members of the community with whom I have had very negative experiences, and nobody with whom I've had a positive experience in that context, so I just don't engage
#gRegor`A custom HTTP header is much easier to experiment with than extending HTTP.
#luxagrafjonnybarnes: I got it. it's a totally unrelated config file that references a self-signed cert (it's not a public site, also behind htpasswd) but
#aaronpkthere are any number of ways to make the browser "handle" the request for payment. the most widely implemented one right now is a paywall in html :)
#luxagrafjonnybarnes: and it sets ssl_protocols SSLv2 SSLv3 TLSv1
#luxagrafwhich seems to override the other... which makes me think I don't really understand how nginx is loading config files...
#luxagrafjonnybarnes: anyway, I changed it and now it's working so problem solved. now i just need to fix Forward Secrecy and Session resumption
#tantekin otherwords, u- properties are designed for easily re-using the URL you already have in your content for functional reasons, e.g. as a link or embedded image
#tantekwithout having to explicitly declare the property value separately as a string
#tantekand iCalendar RFC 2445 5545 uses the name "Attachment" - I think we should go with "attachment" as a property name (despite iCalendar using "ATTACH" as their property name
#tantekbnvk if that sounds good to you, try publshing a page marked up as such, and we can then add it to http://microformats.org/wiki/h-entry#Properties in the experimental / proposed additions section alongside u-photo