Facebook would file a counter-claim, project would be reinstated by GitHub (in 10-14 days as required by law) and OP would have to sue Facebook to escalate. DMCA is of little use to smaller entities without money for litigation.
Yes, Gmail aliases are supported and automatically synced (e.g. I have my old ISP email address set up as an alias). G Suite accounts on custom domains are also supported.
This might be a bit of a different take than the other comments here, but I highly enjoyed reading Things to Make and Do in the Fourth Dimension by Matt Parker when I first became interested in maths.
The IndieWeb[0] community has come up with a protocol called AutoAuth[1]
that solves this exact problem.
It's only a rough draft at the moment and it is built upon the IndieAuth[2]
protocol (which, in turn, is based on OAuth 2), but I think the way it works is highly fascinating.
Pingbacks I understood, xmlrpc was a mistake. Trackbacks on the other hand... That's the FAQ that annoyed me the most (just didn't see it again when writing the comment above), as if trackbacks had no link verification in modern blogging engines.
It's great that the pingback conversion exists now, one issue less :)
Not quite true, Webmentions are used extensively by the IndieWeb[0] community (which is where the Webmention spec was born).
It's unfortunate that the author linked to the Wikipedia page instead of the Webmention page on IndieWeb wiki[1], which I'd argue is the canonical point of reference, since it has a lot more information and various examples.
It's arguably a niche feature used by a niche community, but it doesn't have to stay that way! Adding Webmention support to your website is actually quite easy since there are free hosted services[2] that let you receive Webmentions to any URL on your (static) site without having to run any code yourself.
> These are not leaked medical records. In a way these abilities are like a person saying "hmm isn't that the guy from that thing a while back?"
That's why I don't think there is much of a point in trying to prevent people (e.g. by law) from crawling and using data in this fashion.
I feel like the only reasonable solution here would be to force these companies to rebuild their databases by legally limiting the lifetime of such data.
That way people have a chance to remove themselves from the database by changing/deleting their online profiles without having to use legal measures like GDPR requests. People wouldn't even have to be aware of any individual database they might be part of; they would be removed from it automatically at some point.
Another benefit of this would be that the pure cost of constantly re-crawling a giant dataset could act as a limiting factor and therefore prevent abuse.
Is you are going to play the "is it legal" game, then it's illegal bulk copyright violation.
I gave Facebook a license to make copies of my data for use in its website. I didn't give Clearview a license to make copies to give out to it's customers.
