383416 results for ""a""

• And it does redirect to `target` once the synchronous step (are both params present, are they valid URLs, is S not on my domain, is T on my domain) is completed, assuming all checks pass. Otherwise it redirects to a 404 to prevent, for example, `target` being set to an arbitrary URL and thus the endpoint becoming vulnerable to use as a link obfuscator.
  autumnlilybug at 2025-11-13 21:15
• gRegor: the endpoint, although one could certainly implement it on the permalink instead. I chose the prior because that way the endpoint is a dedicated handler, and the post template page can be entirely static rather than needing a dynamic check before serving the content (I use Astro)
  autumnlilybug at 2025-11-13 21:14
• I would assume it is target.example?source=http://mywebsite.com but then I don't see why there is a need for a `target` param.
  [Trevor_Morris] at 2025-11-13 21:13
• Fair point on de-duplicating. My concern is more that a link with the query params could be shared far and wide, while "manually" sending a webmention is a lot more purposeful.
  [Trevor_Morris] at 2025-11-13 21:12
• Hmm, quick question, is this actually linking to your webmention endpoint, or to the post permalink with the query parameters? I'm not sure that's a great recommendation for publishers in either case, since the query parameters could grow stale over time. I.e. your permalinks change, so the `source` is wrong
  gRegor at 2025-11-13 21:10
• 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

Filter results by:

• indieweb (184814)
• dev (98126)
• meta (39575)
• microformats (21572)
• wordpress (18836)
• social (13104)
• known (3988)
• stream (3211)
• bridgy (162)
• events (26)

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