New issue
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
cross-origin resource sharing #28
Comments
i'm going to pretend this is a democracy and cast a yes vote for this. :P |
Feel free to send in a pull request for this. |
Should we "recommend" or "require" it??? |
Do you have a reason to "require" it? |
As i said... To enable mentions via JavaScript... |
I meant something along the lines of "Considering the increasing popularity of static sites/blogs these days, it might make sense to require cors. Although this will allow the ability to send webmentions via JS, they'll still require a third party service to accept webmentions. Which means if you decide to accept webmentions via JS you cannot respond back to them." Then we can talk about the pro/cons about allowing people to talk without giving us the ability to talk back to them. |
@sandeepshetty that sounds perfect! |
Based on my comment above about the asymmetry, I'm leaning towards a SHOULD or MAY, unless someone has a strong reason for a MUST. |
Should we require the cors header (Access-Control-Allow-Origin: *) to enable webmentions via javascript?
The text was updated successfully, but these errors were encountered: