Because webmentions are alive. Sometimes you need to re-visit and re-pack things to bring them back again.
Because webmentions are alive. Sometimes you need to re-visit and re-pack things to bring them back again.
Trackbacks are alive as well. But yes, they should be revisited and repackaged, I agree that they could need a popularity boost. But that is possible without breaking compatibility for no reason.
In fact I was reminded that originally webmentions were on top of pingbacks: http://tantek.com/2013/113/b1/first-federated-indieweb-comme...
As far as I understand that change is mostly for simplification, which always a good thing.
Webmentions are no simpler than trackbacks, and to have them diverge for no reason makes everything more complicated for the engine. It is no straight-forward simplification at all, thus no good thing.
I hope I did not just miss that (now again and when I saw it the last time), but this does not seem to capable of that.
So, it's not quite trackback, but hopefully it's more useful!
And something I would push into our html markup and debug (the service in the middle might make some origin checks fail), despite my concerns with webmentions as a spec and concept.
The main reason Webmention is less susceptible to spam than Trackback is, is because with Trackback, there is no requirement that the comment text have its own URL. At least with Webmention, a spammer has to create a URL for the spam comment.
The webmention.io service sends a secret token in the payload so you can verify the request came from there.
Thanks for opening the issue, I will add a comment and subscribe.