#dev 2025-12-21

2025-12-21 UTC
CrimeWave joined the channel
#
autumnlilybug hey all, a couple questions
#
autumnlilybug I am planning to write up a more complete reference for my "passive webmention" thing and I can't decide whether that's a good name or not. Would "GET-style webmention" or "redirect-style webmention" or some other name be more appropriate?
#
autumnlilybug (tl;dr for those who weren't around during that discussion: a webmention-like API except using a GET request, such that a hyperlink to the appropriate endpoint both notifies the target site of a webmention and redirects the clicker of that link to the mentioned page. primary advantage is that a webmention can be sent using a web browser thus eliminating the need to use cURL/equivalent tools or a CMS plugin)
m0suli, thegreekgeek, [schmarty], grufwub, Maxpm and [tantek] joined the channel
#
[KevinMarks] You can send a POST with a web browser too, you use <form> instead of <a>. Your webmention endpoint can redirect to the target on a POST as well.
#
aaronpk That's what mine does
rjomara58538, ttybitnik, [schmarty]1, duanin2, opencircuit, chrisaldrich and proofreed joined the channel
#
autumnlilybug [KevinMarks]: I guess I should have worded it as "can be typed into a web browser"(?), the idea being that one can just type in the URL with a couple of parameters and send a webmention without using a site with a form on it, or a non-browser tool.
#
autumnlilybug The advantage over a form being that you don't have to go back and forth between their site and yours to send the webmention
#
autumnlilybug you just write your post with a link to their endpoint, visit your own post (which I do after publishing anyway to make sure everything is formatted right) and click the link
#
ulhar4409 maybe a bookmarklet to send webmentions could be useful?
#
ulhar4409 while i feel like a get->post request proxy could work, you'd still need to encode the parameters into a url, no? unless you use the Referer header, but i'm not sure if that'd be reliable here
#
ulhar4409 also, by "link to their endpoint", do you mean the target URL that you'd mention, or the actual endpoint? because at face value i feel like this implies manual endpoint discovery (painful after considering this requires checking Link headers in the http response)
troojg joined the channel
#
[snarfed] bcakground: https://seaglade.dev/blog/webmention-implementation/ , https://chat.indieweb.org/dev/2025-11-13#t1763062574418000
#
Loqi [preview] [Katherine Isabella Del Toro] Implementing a Webmention Receiver For The Blog
#
ulhar4409 ow, big sidebar on my phone
#
ulhar4409 but hmm, even reading this i'm not sure i understand the benefit
#
ulhar4409 (and as a reader i would probably rather not be the conduit by which a webmention is sent, zzzz)
#
ulhar4409 maybe later i'll try putting together a bookmarklet to send webmentions, but i haven't done bookmarklets before, and my free time is lacking
duanin2 and [Schepp] joined the channel
#
autumnlilybug ulhar4409[d]: probably yeah
#
autumnlilybug ulhar4409[d]: that's what my endpoint does
#
autumnlilybug kinda. it doesn't proxy the request but it functions identically to the post endpoint except with the params encoded in the url instead of a post request body
#
autumnlilybug ulhar4409[d]: agh sorry i had meant to fix that and forgot T-T
#
autumnlilybug ulhar4409[d]: that's fair I guess. there's no requirement for the link in the page to be the webmention link, you can also just send it by typing it into your browser
#
autumnlilybug ulhar4409[d]: see my blog post, but tldr the endpoint is an API endpoint that takes a param for the source, a param for the target, and optionally a param for the voucher, and then if the synchronous validation step succeeds the user is redirected to the target, otherwise to a 404, and the async step is identical to a standard POST-style webmention
#
autumnlilybug ulhar4409[d]: Manual discovery is only necessary in the same scenarios that would otherwise require manual discovery for POST-style webmentions anyway, a CMS integration can discover a get-style webmention endpoint the same way as a post-style one
#
autumnlilybug in regards to my question earlier, I think I am going to start calling it GET-style webmention (in comparison to POST-style webmention) as opposed to passive webmention (active webmention) because "passive" implies that it is found rather than sent and that's not actually how it works
chrisaldrich joined the channel
#
ulhar4409 autumnlilybug[d]: i feel like if there's no proxying then the utility might be limited depending on who feels like supporting get-style in their software
#
ulhar4409 which for *receiving* is probably fine but for sending will likely be an obstacle
#
autumnlilybug ulhar4409[d]: That's definitely an issue yeah
#
autumnlilybug just fixed the small screen issue
#
ulhar4409 nice
gRegor, CrimeWave, [morgan], barnaby, troojg and DanQ joined the channel
#
gRegor autumnlilybug, I see your site is advertising the endpoint `rel=webmention`. If I send a traditional POST webmention there will it work with this setup, or does it only handle GET requests?