383524 results for ""a""

  • Looks like a delete is notified by sending a webmention and then returning a 410 Gone when the receiver checks the source during the asynchronous step
    autumnlilybug at 2025-11-13 21:35
  • My comment section is streamed from the backend which parses content out of webmention sources on the fly (with a 48hr cache so as not to hammer sites during high traffic)
    autumnlilybug at 2025-11-13 21:35
  • I just looked up the webmention updates spec, it looks like it's intended to be used to notify a receiver of changed content yes?
    autumnlilybug at 2025-11-13 21:32
  • [snarfed]: I have seen that but I wanted a system that integrates into my existing website rather than relying on an external service. My website isn't *strictly* static, I'll spare the details but essentially a given route is static unless explicitly configured otherwise (so my webmention endpoint has a backend that is called at runtime but my blog posts are static pages generated at build time).
    autumnlilybug at 2025-11-13 21:31
  • [edit] Script to take pieces from the Met museum in NYC and turn it into a painting in Animal Crossing: https://github.com/metmuseum/Blathers
    capjamesg at 2025-11-13 21:30
  • Script to take pieces from the Met museum in NYC and turn it into a painting in Animal Crossing: https://github.com/metmuseum/Blathers
    capjamesg at 2025-11-13 21:30
  • Hm, perhaps? But in order to be coached they would have to be requested at least once, no? Caching further requests would actually be a benefit I think
    autumnlilybug at 2025-11-13 21:23
  • at minimum, make sure you include a header like Cache-Control: no-cache on your GET webmention responses
    [snarfed] at 2025-11-13 21:23
  • 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
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
Powered by phinde, the self-hosted search engine. status