Ryan Barrett

For the record, Bridgy does currently detect and resend _recent_ webmentions when they change. For example, if someone comments on a GitHub issue, and then edits their comment, Bridgy would...

I was wrong, this wouldn't go in `follow_redirects`, since that only makes HEAD requests, which wouldn't see the HTML contents. From #1322: > Great! [I think it would probably go...

Thank you for the details! And for noticing the overhead. Webmention endpoints are indeed cached, but per domain, and Bridgy regularly runs `get_webmention_target` on 10-20k+ domains. That's currently ~2qps steady...

I've also asked on #indieweb-dev if anyone else has experience or thoughts: https://chat.indieweb.org/dev/2022-10-19#t1666148871932600

Hmm! `discover` already makes a GET request, and parses the HTML contents if there's no webmention endpoint in the headers, so it shouldn't need any additional HTTP requests or expensive...

Right! One other thing, this should probably go behind a new boolean kwarg in `discover`, maybe `follow_meta_refresh`, that defaults to `False`.

Woo, awesome, glad to hear it! Thank you again!

Good follow-up! This can definitely be an awkward surprise, but it's actually intended webmention behavior. As part of receiving a webmention, the receiver [fetches the source page and checks that...

(Oh btw, with your client side redirect change, the `requests.Response` that `discover` returns will now contain the final redirected URL, so users can get it if they do need it.)

You're welcome! Glad this is still working out ok. Feel free to jump into chat or https://github.com/w3c/webmention/issues to discuss more, eg https://github.com/w3c/webmention/issues/103 or others in https://github.com/w3c/webmention/issues?q=is%3Aissue+redirect !