""a"" search results - search chat.indieweb.org

383251 results for ""a""

but the reliance on the link being clicked is certainly a downside
autumnlilybug at 2025-11-13 21:09
and your point about the link needing to be clicked for the webmention to be sent is correct, though there's nothing stopping someone from either manually typing the passive webmention into their browser (which is arguably less work than using curl to send a POST for many people) or simply clicking the link in their own post after publishing
autumnlilybug at 2025-11-13 21:07
Not sure what "comment-style" notes are, but for articles, I have built something within my publishing, which enumerates each external link and tries to send a webmention (well, I manually trigger them).
[Trevor_Morris] at 2025-11-13 21:03
That does make sense I suppose. The benefit that I had in mind is that an HTTP get can be sent by simply typing an address into a web browser, and one could even link to the passive webmention endpoint in their own post such that the first time the link is used the webmention is sent implicitly (which is why I called it "passive" - nothing has to happen in the sender's publishing software nor does any manual work need to be
autumnlilybug at 2025-11-13 20:59
The foundation of HTTP and the web is verbs, eg GET and POST. GET is for retrieving data that remains unchanged, and POST is used to create or update (could use PUT for that, but native browser support isn't as good as POST) data. This is why a webmention should be using POST. I'm not sure what benefit you get from using a query string vs a form. HTML forms are pretty easy to build and send the correct data in the POST format. General
[Trevor_Morris] at 2025-11-13 20:56
It could also work with a form at the bottom of the post, with the `target` pre-populated as a hidden input. Several of us do that with a POST method form, but easy to switch it to GET!
gRegor at 2025-11-13 20:49
that's a good idea
autumnlilybug at 2025-11-13 20:46
also, if you *do* have a CMS or some existing automation, you can still send passive webmentions because the GET request is just as automation-friendly as a POST. So in practice there's no real downside that I can think of.
autumnlilybug at 2025-11-13 20:41
anyways, the advantage is that you don't have to mess with curl or any other low-level tooling, and you also don't need a CMS to handle sending the webmention, you can just click that link (or type it into your browser and leave a normal hyperlink in your page)
autumnlilybug at 2025-11-13 20:40
Webmention relies on HTTP POSTs which are non-trivial to automate without using a CMS. I decided to implement a GET handler on my webmention endpoint that uses the search parameters `s`, `t`, and `v` in place of the formdata fields `source`, `target` and `vouch`. If you were to link to, say, `example.com/page1` with a normal webmention, you would use a normal `href` to that URL and then send a POST. With passive webmention
autumnlilybug at 2025-11-13 20:36

Sort by:

Relevance Date

Filter results by:

Tag

Query took 0.04s.

Search tips

Exclusion: +foo -bar
Logical OR: foo OR bar
Exact phrase: "foo bar"
Partial words: foo*
Particular fields only: title:foo; domain:example.org; nick:somebody; after:2016-11-23; before:2016-11-23; date:2016-11-23