Like duplication

[vandie]

Currently, it is possible for the same domain to send multiple likes to the handler and them both be processed. While this is perfectly acceptable, they can also be from the same author which can lead to multiple likes from the same user appearing next to one another.

This is especially an issue when using Bridgy to handle social media likes where a user can like the page using multiple sites that link back to their primary web domain. That web domain then provides an author object which is the same for both likes. This can happen (in an even more troubling manner) when receiving likes from Twitter as these can be duplicated due to the same user liking multiple tweets that act as substitutes for the same web page. In this case the likes are almost identical but still have a different source and therefore cannot be de-duplicated.

While the official web mention spec doesn't offer a solution to this issue, and therfore it may be out of scope. It seems like this should be handled or at very least, documentation should be added that explains the limitation and offers suggestions on how to solve it.

[vandie]

I'm leaning towards making documenting this as won't fix. Its expected functionality according to the webmention spec and I'm hesitant to deviate from spec.

I'll add an explanation on how to fix it for a given site though as it can be fixed in a single line (which I have done over on mikevdv.dev)