[Johnny555]

What's the point of the NTP pool providers making their concerns public when consumers like you, who apparently are aware of the issue and what it means, don't care because TP-Link makes a "good product"?

Your attitude kind of reminds of the people that toss their cigarettes out their car window. When confronted they'll say something like "But my car doesn't have an ashtray, this is easier" or "But I don't want used cigarette butts in my car" or "What am I hurting? It's only one cigarette, and there are volunteers that clean up my cigarette butts from the roadside" or "If it was really a problem, they'd enforce it better, I've never been given a ticket for it"

[cthalupa]

Because I'll be more concerned if the NTP pool providers say "This is detrimental to our services" than if a random 3rd party blog (that has apparently not even checked their math) says I should worry about it.

[dsharlet]

TP-link is clearly ignoring many of the instructions from NTP: http://www.pool.ntp.org/vendors.html

Notably, they are ignoring the ones that make it possible for NTP to be aware of the problem in the first place. Right now, TP-link's traffic probably just looks like millions of unrelated devices misconfigured. NTP wants vendors like this to make requests to a particular subdomain so they can identify problematic vendors in the first place.