#voxpellicweiske: depends on what generates the tokens for you – if it's not your own system but rather eg. IndieAuth, then you would need a web flow that grabs it for you
#cweiskecurrently indieauth requires a callback URI to which the browser is redirected
#cweiskecli clients don't have such a redirect URI
#cweiskemaybe indieauth should specify some special redirect_uri value that tells the auth server to echo the auth code
#cweiskeso auth servers implement that themselves, and I don't have to host a service for other people only because I wrote a MP client
#voxpellithere are alternative flows to negotiate OAuth tokens that are more suitable for eg. CLI tools, TV:s etc – such as a pin-based approach, where the callback url is replace with a pin code
#cweiskeok. unfortunately, the indieauth spec does not allow such things
#voxpellisimplest change to make it support it would probably be to just make the redirect_uri optional in the authorization flow and if not specified then just print the code instead
#cweiskevoxpelli, the "code" currently looks like this: code=ZW1vamk9JTVDMzYwJTVDMjM3JTVDMjIyJTVDMjUxJm1lPWh0dHAlM0ElMkYlMkZhbm93ZWNvLmJvZ28lMkZ1c2VyJTJGMy5odG0mc2NvcGU9JnNpZ25hdHVyZT1GSVhNRQ%3D%3D&me=http%3A%2F%2Fanoweco.bogo%2Fuser%2F3.htm&state=1472992410
#GWGDoes anyone return json in a Webmention implementation?
seekr joined the channel
#bearI know I would welcome an IndieAuth way to use my command line tools - right now my CLI says "after the browser opens, copy the access token..." which is not very helpful
#Loqiaaronpk: cweiske left you a message 3 hours, 37 minutes ago: re micropub draft: why is the media endpoint only discoverable after fetching an auth token?
cmal joined the channel
#voxpelliaaronpk: I wonder if one could discover that a service supports that? and somehow use that?
wolftune joined the channel
#GWGI'm thinking of completely taking over the WordPress system for sending pingbacks and switching to a webmention first, pingback fallback design.
snarfed joined the channel
#aaronpkcan you do that? that sounds like a good idae
#GWGBy the way, aaronpk...the ability for a WordPress site to delegate its pingbacks to webmention.io should be in WordPress 4.7. Until now, you couldn't filter the default pingback endpoint easily. Is that a problem?
#snarfedGWG: bridgy respond json to wms, both for hosted blogs and for publish
#GWGsnarfed: As long as I'm using the REST API, which autoconverts every output to JSON unless you turn it off, I figured I'd consider outputting as JSON.
#voxpelliGWG: snarfed: I send JSON on some errors, but on most responses only send JSON or plain text if stated as an acceptable response format by client
#ZegnatNot going to lie, those animated profile pictures are pretty fun. Though to be fair, acegiak has been rocking one of those for some time now (hashtag-indieweb)
#tantekhttp://lanyrd.com "Ooops! / 503 / Gosh! Looks like something has gone a bit wrong. Don't worry though, we know and are fixing it. Please try again later. /Follow @lanyrd on Twitter for updates or email support@lanyrd.com"
#GWGIf you are looking for webmention and if isn't there, you should go for pingback, that means I would have to look in the head for webmentions, then the body, then the head again for pingback.
#Loqitantek: snarfed left you a message 15 minutes ago: benwerd's email to known-dev wasn't about posse vs pesos. it was about posse + backfeed vs pure indie interactions.
#tanteksnarfed, then I don't understand, as they are complementary, not vs
#GWGtantek: It isn't about the code. Trying to decide how to put it together.
#tantekhmm I suppose an outline of how to call it would help
#GWGEvery time I map it out, I feel like I'm repeating myself.
#tantekthat library helps reduce repeating yourself, that's the point
#miklbcan't remember if ASL is compatible with GPL
#GWGtantek: Not really, alas. The code for extracting the information is already in WordPress. I'm just trying to figure out how to gracefully fall back.
#tanteksnarfed, the whole premise of "APIs changing breaks POSSE" seems like arguing an absolute in a vacuum
#GWGI just want to make sure it doesn't get criticism.
#miklbas long as its constructive, it would only make it better
#tanteksnarfed, also really curious about how you got the "letter of the law" impression when /principles and /code-of-conduct would hopefully give a different impression?
#KartikPrabhuGWG: ask forgiveness not permission. If anyone criticises it then think about changing
#snarfedtantek: the api fragility point was a smaller point, just at the beginning. the bigger point was surprise and social norms around backfeed
#snarfedfor people who *aren't* part of the community, brought in via backfeed
#KartikPrabhutantek: the one thing I got from that email is that silo users might not realise that their responses are backfed. That seemed to be the most relevant point
#tantekpoints about surprise and social norms are certainly worthy of more documentation
#LoqiA disclosure is a bit of content, typically on a home page, on an indie web site that proactively discloses some aspect about the site that the site owner wants the user to explicitly be aware of https://indieweb.org/disclosure
#tanteksnarfed, why is "nearly enough" the metric?
#tantekisn't any incremental improvement a good thing?
#KartikPrabhusnarfed: I agree that it might not be enough since the Twitter bio page is rarely visited (at least by me) when replying
#snarfedsocial norms are a very different thing than shipping code
#snarfedanyway, gotta run, definitely worth talking more later!
#tantekno successful social network started with thinking "not nearly enough"
#tantekso yeah, I'm going to reject that kind of framing, because it causes you to not ship
#tantekKartikPrabhu: it's never enough. that's the problem. you can always think of more fear-based excuses.
#miklbso if I'm understanding the conversation, people are bothered their public silo comments that are used to mine data to sell ads are bothered the comment might be aggregated with the original comment on a personal site?
#tantekthus "not nearly enough" is nearly useless framing
#tantekmiklb - no, the assertion is, they *might* be
#tantekas soon as you give into "not nearly enough" reasoning, you've already lost
#KartikPrabhuno. I was thinking of the problem: "Is there a way to warn users, while they reply on a silo, that their comment might be backfed"
#KartikPrabhuand the current answer to all silos I use is "no"
#miklbseems silly me. like thinking your conversation in a crowded bar is private.
#tantekKartikPrabhu: what is the utility of such warnings? what's the use-case? (especially given that usually such warnings just get ignored by users, like nearly all warning dialogs)
#tantekKartikPrabhu: the question "Is there a way to warn users?" presume that's a good UX, which it is not
#tantekmiklb - that's a different problem, and somewhat more nuanced, see /publics for more on that
#KartikPrabhuthe utility is to give fair warning (for sake of politeness) that their content may appear where they might not expect it to.
#tantekKartikPrabhu: I disagree. Since everything you post (what aaronpk said) would need such a warning, and currently you don't get such warnings for everything you post.
#tantekthis is also one of the reasons that when Bridgy was first proposed, there was a strong consensus to only backfeed replies to public posts
#KartikPrabhuyes. backfeeding only public posts is an acceptable solution in my mind.
#tanteksnarfed, and I have discussed the implications of backfeeding responses to private posts, and have yet to come up with a way that would make the privacy expectations make any sense (be predictable)
#tantekso no one is doing it yet AFAIK (backfeeding responses to private posts)
#aaronpkWould sharing the same privacy settings (visibility?) be appropriate?
#tantekif there was some way you could pull that off!
#LoqiACL is an abbreviation for access control list, and in the indieweb context refers typically to a list of people who are allowed to view (and perhaps edit etc.) particular posts or perhaps an entire site https://indieweb.org/ACL
#aaronpkthe classic problem is that sites with private posts have two different ways of handling access control. In one case, people who are added can see things previously posted to that group. In the other case, people who are added can only see things posted from that point onwards.
#KartikPrabhuis there any real need for consistency of the above across sites?
#KartikPrabhusame way we do not require consistency in say webmention handling or parsing?
#tantekaaronpk: I think nearly everyone has settled on the first model
#tantekonce you get access, you can see all history
#Loqiprivate posts refer to posts or portions of posts which are private to either the author or to a limited audience chosen by the author https://indieweb.org/private
#LoqiA private account is a silo account where all posts on its profile are private, and only approved followers (or friends) can see posts https://indieweb.org/private-account
#aaronpkprivate IRC channels (or other things that are not logged) are the other way. But that does seem less common
#tantekaaronpk - that's only because of the accident of IRC logs being separate from chatting in them
#tantekpresumably once you get access to the channel, you can see all logs too
#tantekI do think this (private posts) is an area indieweb is going to have to innovate soon to continue broadening reach / appeal (assuming that's a goal)
#tantekI'm certainly hesitant to implement some post types without it (e.g. checkins)