Ruxtonschmarty: I dunno if its gotten better but there were a lot of timing issues in FF and Chrome 5 or so years ago around the audio tag with subtitles
[KevinMarks], __minoru__shirae, shoesNsocks, [arush], KartikPrabhu, [schmarty], [tw2113_Slack_], [aciccarello], astralbijection[ and [chrisaldrich] joined the channel
@bnijenhuis↩️ I agree that it should be serverside where possible, but the problem is that I manually upload my website. And that won't happen often. To show accurate webmentions, clientside implementation is required here... (1/2) (twitter.com/_/status/1389677435629805571)
@bnijenhuis↩️ I do plan to implement service workers to cache the requests for the user, so that will limit the number of requests. I'll write it up when I've implemented it and will specifically mention the webmentions implementation. (2/2) (twitter.com/_/status/1389677794305654794)
[chrisaldrich]Dirty rats.... Looks like Tumblr is running all the links on their site through href.li to hide the referrers which means that it is much harder for one's site on it to send webmentions.
sparseMatrixOk y'all, I guess I'm slightly lacking in full comprehension of webmention. How exactly does that work? How does my site know, for instance, if one of y'all has commented on some post?
sparseMatrixso basically, every hentry page on a site supporting webmentions will advertise a webmention endpoint in a rel link in it's header; anynone who wants to get its attention, so to speak, will hi that endpoint with the appropriate payload
[chrisaldrich]Thanks [snarfed]. The Brid.gy repo was actually one of the first places I turned to for advice and history. I've seen some mentions that WordPress.com sites may use that same URL wrapper (though most seem to be private or semi-private websites).
[chrisaldrich]I've run across one or two JS-related scripts/code that one can put into their Tumblr theme to get rid of these pesky wrappers. Hopefully I'll get some time later to try one or more of them out.
[chrisaldrich]Since brid.gy bridges all the things, its issues queue is always a wealth of information when some silo-based platform isn't working properly or as expected. [snarfed]++
LoqiAn authorization endpoint is an HTTP endpoint that micropub and IndieAuth clients can use to identify a user or obtain an authorization code (which is then later exchanged for an access token) to be able to post to their website https://indieweb.org/authorization-endpoint
RattroupeBased on my reading of the indieauth spec... I want to be able to enter my site's URL into an indieauth client. Then that client and my site do the oath token exchange
jackyyeah but Rattroupe's going down the route of implementing their own endpoint versus using https://indielogin.com, which is different because the MVP for that would be what you mentioned; adding a /h-card to your website
jackytheir approach wouldn't involve https://indielogin.com and doesn't require them to add a h-card (although it helps for other things like showing your face in the context of a outgoing Webmention - but that's for later)