doubleloop, snarfed, iasai, dougbeal|imac, KartikPrabhu, [cleverdevil], ingoogni, eli_oat and [tantek] joined the channel
#[tantek][chrisaldrich] could you perhaps update /Getting_Started_with_WordPress with that "minimal set" approach? Would be great to simplify that doc to make IndieWeb WordPress more approachable by more people!
#[tantek]In particular, there's a lot of unnecessary explanatory pre-amble (anything about "Generations" or "IndieMark") that doesn't actually help someone just trying to "Get Started"
[eddie] joined the channel
#[eddie]!tell jacky I think tags and mentions can both be seen in the silo world as well. It's the same as hashtags and @-mentions
#[tantek]eddie I think jacky means the distinction between person-tagging and person-mentioning, which is quite distinct in silo posting UIs like FB, Twitter, and Swarm
#[eddie]hmmm, true. I should login facebook and do a test. Last I knew I thought you could mention someone by typing their name in the regular text area, or tag someone as "with X"
#[eddie]But that might have changed where if you mention them, they automatically get added to "with X"?
#LoqiA person tag (AKA people tag) is a person mention that is also a tag on a post that refers to a specific person by URL rather than just a word or phrase, and is done as an explicit tagging action by the user, beyond just mentioning a person via hyperlink / h-card / or @-name, autocompleted or not https://indieweb.org/person-tag
[tantek], djmoch and chrisaldrich joined the channel
#chrisaldrichI think I had tried to set it up at the summit ages ago when there were still issues with Auth that I think have been fixed. Haven't looked at it since then.
#aaronpki don't think that plugin existed at IWS last year? but yeah the auth issues have plagued wordpress micropub/indieauth forever. seems to be quite a large number of web hosts that block the HTTP Authorization header by default, which is probably what's happening here
#chrisaldrichThe plugin was about a month later... I was doing the header manually.
#Loqi[indieweb] wordpress-micropub: A Micropub Endpoint plugin for WordPress
#chrisaldrichLooks like I've run afoul of two accounts when my site when from http to https... aaronpk, can you tweak things so that I can keep the #16 account with my https version and kick the #99 version?
#snarfedZegnat also wrote some even more detailed troubleshooting tool for that header
#aaronpkchrisaldrich: oops yeah i can tweak things around for you
#chrisaldrichWhich looks roughly like what changelingmx is reporting on Github...
#aaronpkso the hosted Aperture service makes a request to the token endpoint (part of the indieauth plugin) to check if it's valid. i'm guessing the web server is blocking the HTTP Authorization header from coming through. (Some micropub clients also send the access token in the post body and sidestep this issue)
#GWGThere's a diagnostic tool built into the Indieauth settings page
#[tantek]Can the plugin provide a better error message to help the user (1) understand what is actually happening, (2) take possible actions to fix it?
#aaronpkkinda. the trick is Monocle gets a generic HTTP 403 error message back from WordPress. I've updated Monocle to output a host of debug info which has been helpful so far (at least helpful to GWG) since it clearly spells out the error the wordpress plugin is returning
#aaronpkwhat the user sees is from Monocle, so I'd need to be able to show something there that's more actionable to the user, so i'm open to suggestions there
#chrisaldrichSetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1 doesn't seem to work... let's try the other option...
#[tantek]sounds like multiple pieces need to co-operate to communicate a helpful and actionable error message to the user
#[tantek]that makes me think that it might be something that could be helped by an explicit protocol for those pieces to use to communicate that info
#aaronpkhow do I know if that piece is working tho heh
#aaronpkthe problem is the user sees an error in monocle and needs to understand that it's a problem with their wordpress and not a problem with monocle or aperture
#aaronpki got blamed for aperture being the problem here
#aaronpkbut i don't know how to help people in the right direction
#[tantek]I feel like this is a risk for many things WordPress due to the complexity of setup (plugin switches to flip) and the fragility (theme changes, plugin updates, WP core updates -> things break)
#Loqi[Changelingmx] Yes. I can log into micropub clients just fine. Trying to log in to Monocle results in the following:
There was a problem trying to load the channels from your Microsub endpoint.
Microsub endpoint: https://aperture.p3k.io/microsub/220
Your web...
#chrisaldrichI think in the majority of these cases, it's a hosting issue where they're stripping out headers and not letting them through...
#aaronpkbut as you can see, it's a bit of a challenge to go from that error message to understanding that it's a wordpress hosting environment issue
#snarfedso the wordpress plugin should probably add a user-visible message and link to that faq page in all of its 403 errors, since this is a known issue. cc GWG
#aaronpki can defiinitely make monocle highlight the "error_description" value more prominently on that page, so if the wordpress plugin provided a better message there it could be more useful
#aaronpkat least "Bearer Token Not Supplied" is a lot better than it used to be