[snarfed]aaronpk if you let likes through with hand moderating each one (eg i assume you do that), and you facepile and ellipsize them (which the wordpress synd links plugin does by default), the experience takes zero effort
[tantek]aaronpk one problem of the facepiles / likes in general that are from Twitter, linking to the relevant Tweet is next to useless. like nearly 300 links to the POSSE tweet? why?!?
@DavidDeAngelisThis is my #11thtwitteranniversary, yes, my #11anniversary or #11twitteraniversary, or just say, my #11twitterversary #MyTwitterAnniversary Whichever be stated, I espouse my 11th anniversary on twitter #webmention #followme #comefollowme or just celebrate! Ty be well & be safe!XO (twitter.com/_/status/1269538837967052800)
moppy, jeremy, shrysr, gxt, Kongaloosh, Kongaloosh_, Salt[m]1, KartikPrabhu, leg, nekr0z, [jgmac1106] and neonkit joined the channel
@aswath↩️ EnThinnai is counter to network effects and so designed a proto-webrtc and advocated triangular conn model. There is no moat in SSO. There are OpenID, Indieauth and webID. (twitter.com/_/status/1269640584718954505)
[tantek]anytime you find yourself asking is there a standard "give me JSON for ...", ask yourself instead, where in the HTML is that information already and if so, how can I parse it out
[fluffy]Like I’m thinking of making my own “actor” (in the activitypub sense) that supports webmention and activitypub and a few other things and it’d be great to have a means for it to provide user notifications in a manner consistent to what the social readers expect.
[fluffy]So what’s the use case for monocle asking for a specific token endpoint when it seems to expect a specific one to be used? Or am I completely misunderstanding something as usual?
[fluffy]Like it seems to me that monocle should be using its own specific token endpoint that’s relative to itself as the resource, rather than requesting an arbitrary token for the user that it can only validate/use if it’s a specific one.
[fluffy]Okay so. I’m using aperture as my microsub endpoint. But I’m using a separate thing (yet to be written but will be a plug-in for Publ) for micro pub.
[fluffy]How does the token endpoint validate tokens? I feel like we had this conversation at one point before and the answer was “that’s specific to the thing” like it isn’t specified as part of indie Auth
[fluffy]The authorization code verification is, as far as I know, correctly implemented in Publ. At the very least, https://gimme-a-token.5eb.nl/ works correctly with it.
[fluffy]And monocle is making a request to it and getting a 200 response, which only can happen if my endpoint has provided a token after verifying the authorization code.
[fluffy]it’s doing the authorization code, my endpoint is verifying the authorization code and returning a 200 response. Maybe there’s something missing in the payload that monocle is expecting.
[fluffy]Sweet, I got it all working. Log in to monocle as https://dev.beesbuzz.biz (which doesn’t require a password for the indieauth endpoint) to see.
@ysamjo↩️ I'm aware of WebMentions. But as with other Microformats, I don't think they stand a chance without active pushing by big players. I mean it's already late in the game.
For example, why are those things not the standard for every wordpress com account? (twitter.com/_/status/1269693680396447746)
[tantek]aaronpk, fluffy, this sounds like a reasonable misunderstanding (of indieauth flow). Is there some way we could add trouble-shooting or something to the wiki to help make it more discoverable / clearer?
[tantek]big players pushing standards often either make them massively bloated (all the XML attempts, schema org etc.), OR they end up killing them (see aaronpk's post on how many metadata formats Google has killed), or BOTH (OpenSocial)
[tantek]because, simply, Webmention is not spam-proof enough on its own to be able to withstand that big of a target. Something like Vouch or Vouch itself is necessary for Webmention to be able to withstand (most) spam/abuse by default, and provide a smooth & unburdensome UX for both folks replying to blog posts, and folks receiving those replies/comments
[fluffy]> The token endpoint verifies the access token using (how this verification is done is up to the implementation), and returns information about the token
[fluffy]Gimme-a-token is an okay starting point but it missed that I wasn’t returning `me` in the token grant and it does nothing for token verification. Which is straightforward to do manually but I had no prompting to actually implement it.
[KevinMarks]The opensocial lesson was also that with one big player adopting it, another big player declares war on it and fights it as a giant threat.
[fluffy]Another IndieAuth question… I forget what the thoughts were regarding scheme change in identity validation. Are they allowed or not? I think that was something that wasn’t particularly clear from the spec.
@gRegorLove↩️ I haven't tested it in that setup or done a lot of multilang in PW. Would it be a separate PW page for each translation?
Generally I would expect it to work. Webmentions are saved to a specific page ID. (twitter.com/_/status/1269757847568437248)