We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
beesbuzz.biz is accessible from both http://beesbuzz.biz and https://beesbuzz.biz. People subscribe to the Atom feed both ways, so I need to send WebSub notifications for both schemes. But this means that WebMentions get sent for both as well (see http://publ.beesbuzz.biz/blog/730-v0-3-12-now-we-do-Windows for example).
Possible solutions:
The text was updated successfully, but these errors were encountered:
nah, people can filter this out receiver-side, as I do in webmention.js
Sorry, something went wrong.
This turns out to still be a problem with fed.brid.gy so I guess I should actually fix this.
No branches or pull requests
beesbuzz.biz is accessible from both http://beesbuzz.biz and https://beesbuzz.biz. People subscribe to the Atom feed both ways, so I need to send WebSub notifications for both schemes. But this means that WebMentions get sent for both as well (see http://publ.beesbuzz.biz/blog/730-v0-3-12-now-we-do-Windows for example).
Possible solutions:
The text was updated successfully, but these errors were encountered: