@polm23↩️ Sorry, I think we're still not on the same page. My concern is that if GET was acceptable a static site could just used a fixed endpoint to accept WebMentions and http://webmention.io or whatever would be unnecessary. (twitter.com/_/status/1052391615908564992)
@polm23↩️ I assume there's a significant difference in intent between ordinary links and WebMentions - in the latter case there might be structured data, an expectation/hope of reciprocation, etc. (twitter.com/_/status/1052392067752583168)
ZegnatParse the requested URL, KartikPrabhu? This idea delays all handling of the webmention to the build step, at which point you scan the server access logs for requests to the wm endpoint.
ZegnatThat's a different thing though, [schmarty]. That's generating webmentions from visitors, they want to handle actual webmentions that have been sent irrespective of whether people have clicked the links.
@kevinmarks↩️ The point of webmention is that the target page fetches the source page, checks that it does link and does something in response (displaying the comment, adding to a like count, noting an rsvp etc) That needs code to run and generate new pages, so can't be done statically. (twitter.com/_/status/1052462835320676353)
@polm23↩️ Verification doesn't have to happen on the web server - I can download the log, moderate the webmention requests, add them to my static site and build it locally, and then push it live. Of course I need my local machine for that but the web server can be completely static. (twitter.com/_/status/1052502921848315904)
@kevinmarks↩️ I think we're converging on the same thing. My website http://kevinmarks.com is static, but it uses an external webmention service. I could build those in statically too, but my site is really static, it's a bunch of pages made by hand. (twitter.com/_/status/1052503890028048384)
aaronpkindieauth avoids ID tokens by just returning the user's identifier in the code exchange step directly, rather than returning an ID token where you can extract the user identifier
aaronpkthere's also an open issue to consider removing the "me" parameter from the first URL, which would make it actually compatible with a generic OAuth 2 client
aaronpkit's probably a good idea in general to simplify things when possible, so i'm inclined to start making that change, but it is a breaking change to the current indieauth spec so every client/server will need to update
Loqi[aaronpk] Here's a quick survey of current implementations of token endpoints:
## Integrated Micropub/Token/Authorization Endpoints
* p3k - verifies the `me` parameter exists, but does not use it for anything
* Wordpress IndieAuth plugin - verifies the `m...
GWGI'm on Location right now. I need to code an alternate reverse geolocation provider. Annoying this happened just as I finally got all the Micropub Android location parameters I wanted.
aaronpkI didn't do an implementation survey of the details of the authorization endpoint because we *know* it's not technically needed for the flow to work
aaronpkwhereas with the token endpoint there is at least one use case that does require it, but it's debatable whether that's a useful use case or whether that could be accomplished some other way
jeremycherfasNow fixed. WithKnown has an interesting approach to html entities and sanitation. I did go digging once to see if I could fix it without opening myself to hacks, and then forgot about it. But now that I am using Omnibear more, I need to revisit that.
[jgmac1106][cweiske] I start every classroom from Kindergarten to College making a list of expected behaviors. Community matters. These things work. Sorry you feel Code of Conducts are too subjective to make you feel safe
snarfedyeah storing each user's followers, so you know where to deliver posts, is probably where bridgy fed needs to end up if it wants to propagate original posts too
aaronpkyeah there really isn't a better way to do that. you wouldn't want to offload that work onto the person's website since at that point they may as well build out more of the AP spec themselves too.
swentelI could test with setting up one myself maybe, but mastodon probably has bridgy fed stored (at least that's what it should be doing), don't want to confuse it
[schmarty][dougbeal] fly.io is more like a proxy service. Fly.io proxying for a glitch.com app is like Heroku running a nodeJS app with a collaborative editor and hot reloading.
[eddie]One thing that should be really fun about My Url Is will be pushing forward IndieWeb stuff in the podcasting sphere and be able to use it as a proof of concept on various things. Of course supporting h-feed podcast listening, also it receives webmentions (doesn’t display them currently, but it does forward them to my notifications channel, and I’ll display them eventually).
[eddie]I’m thinking about a Microsub server bridge that listens to a channel or all channels within a Microsub server and creates an rss feed for a normal podcast player
[eddie]lol yeah, currently what I’m doing is in Overcast or Castro I can use their share button to share into Indigenous and select “listen”. That sends the url of their website as the listen property to my Micropub server where my server scrapes their respective website and pulls the needed info for my listen posts
[eddie]The nice thing about the RSS feed bridge is that when you clicked “listened” it could create the Micropub post AND mark your microsub post as read
[schmarty]A microsub client that makes an RSS feed out of a channel does sound good. I have a goofy hacked together setup for manually collecting Supporters-only posts on backer services like Patreon and Drip. It’d be sweet to be able to kick them into an Aperture channel and subscribe to that.
snarfedthere are lots of podcast apps and third party plugins that do scrobbling. i wonder if any let you enter your own server. we could translate the scrobble (last.fm ?) protocol to micropub listen post
[schmarty]snarfed: I didn’t have much luck finding podcast apps with scrobble support. One or two on android supported libreFM but I couldn’t tell what API support it had
[eddie]The strange thing is, I don't feel like you should have to worry about HEIF at WWDC they suggested anytime an app doesn't KNOW that the destination supports HEIF it should fallback to JPG or PNG 🤔
[schmarty]Not sure how hard it is to get into the beta, but this should be able to add some building blocks to GitHub pages sites. Sending webmentions, websub notifications, for starters.
[schmarty]Also should enable GitHub pages sites to use site generators other than Jekyll, since you can probably do build steps and push to another branch.
[renem]Thanks for moving. I think I know what’s going on. I haven’t change the mf2 things but added a JS lazy loader which handle images differently. And I think this is a good starting point.
[renem]The lazy loader JavaScript replaces the data-src and data-srcset with src/srcset when the picture gets visible in the browser view. But of course this will never happen for a parser like Bridgy. I’ve to change that or add a noscript Tag as well to handle this.
[dmitshur], [eddie], [kevinmarks] and dougbeal|mb1 joined the channel