Originally Posted by
bigboy
At this point, this new security setting on StackPath may very well kick in at the start of every month. I got suspicious when I thought to get some last minute trophies and found they ramped up security late on the 28th. Curious. í*¾í´ Some testing on TNT's end?
My theory is StackPath is using the device fingerprint of StealthCORE's internal Firefox browser to block traffic, which I suspect is the same across all copies of the program. They can do that by reading your OS, browser of choice and a slew of unique identifiers tied to it. I figure this is the case since clearing my cache and cookies did nothing to stop it, which is typically the fix for some. It might also flag users based on that fingerprint, given the site verification problem persist between browsers.
Of course the problem may instead lie in the internal browser's own cache and cookies, but it seems unlikely given there's not much in cookies and caches tying us all together, besides StealthCORE's device fingerprint. I'm not even sure if StealthCORE stores cookies and caches beyond the current login session. Because of this, one solution may lie in programs such as MarketerBrowser which can actually randomize your browser fingerprint. I'm sure one of them can be integrated into the StealthCORE suite with some of Joe's elbow grease í*½í¸ Highly recommended.
My advice is don't expect them to lay off StackPath completely because of this issue, since they might learn to be more precise with what activities they target. This could very well be an example of TNT learning to pin down automated users. Look out for outages during Altador Cup and Daily Dare (if they ever bother to reintroduce it), and especially look out on March 31st. That could confirm this recent spike in StackPath activity was intended to target trophy hunters using Majin.