You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At IndieWebCamp Düsseldorf we discussed the issues around receiving Webmentions and GDPR. Users need to be informed how their data is used. With a Webmention from a personal site, we can assume that the person has installed or is aware of that functionality.
However, services like brid.gy crawl content silos send Webmentions for users that are not intending to be re-published somewhere else. Of course as the site owner, I can attempt to anonymize such Webmentions. But I think it would be appropriate if brid.gy Webmentions would include header information like 'source-type: crawled' that I can then handle accordingly.
The text was updated successfully, but these errors were encountered:
I am not sure if this is something for the spec, because it is a very specific (not directly intended) usage of Webmentions and the spec says not much about the handling of Webmentions. I would prefer to discuss this for implementations of the Webmention spec.
At IndieWebCamp Düsseldorf we discussed the issues around receiving Webmentions and GDPR. Users need to be informed how their data is used. With a Webmention from a personal site, we can assume that the person has installed or is aware of that functionality.
However, services like brid.gy crawl content silos send Webmentions for users that are not intending to be re-published somewhere else. Of course as the site owner, I can attempt to anonymize such Webmentions. But I think it would be appropriate if brid.gy Webmentions would include header information like 'source-type: crawled' that I can then handle accordingly.
The text was updated successfully, but these errors were encountered: