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
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
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
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?
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?
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.
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, 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?
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
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
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?
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: 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.
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)
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.
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
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)