Context Navigation

Changes between Version 1 and Version 2 of Ticket #16838, comment 30

v1	v2
4	4	Well, once [https://github.com/WP-API/WP-API WP-API] gets incorporated into core a continuously effective peer-to-peer plugin ''could'' be implemented that would not require such a service. The peer-to-peer service could have a set of 10+ volunteer central servers like how the 10 root DNS servers work. And such a plugin would also potentially enable trackbacks to be usable again by allowing site owners to validate legitimate trackbacks using oAuth and block spammy ones.
5	5
6		Such a plugin could even ~~allow similar sites to optimize for spam via outright blocking.~~ For example, I have a blog about WordPress plugin development and posters who use the author name ''"Hollister Outlet"'' or ''"Abercrombie"'' should be outright blocked vs. tagged as spam. However having 'WordPress"'' in the name should not be a concern per se on my blog. But for a fashion blogger, the reverse is probably true.
	6	Such a plugin could even optimize for spam by site topics/content and then outright block ''(vs. tag as spam.)'' For example, I have a blog about WordPress plugin development and posters who use the author name ''"Hollister Outlet"'' or ''"Abercrombie"'' should be outright blocked vs. tagged as spam. However having 'WordPress"'' in the name should not be a concern per se on my blog. But for a fashion blogger, the reverse is probably true.
7	7
8	8	A peer-to-peer plugin could even possibly orchestrate a denial-of-service attack on the spammer!