Stefan Kalscheuer

+1 for both Storage limit is a valid point. But there is no real benefit in storing old spam on low-traffic sites, as patterns change. 100 comments should not yield...

The behavior shown above is intentional, I’d say. `--iterative` Just enables iterative mode. By default this starts from the well-known root servers. If name servers are specified, they are used...

For JS tracking a delay would be easy to add, just another parameter to the JS arguments and wrap the call into a `setTimeout` block. Adding a "scroll" event listener...

Just checked with your UA extension, the hook is fired correctly when AJAX tracking is active. Didn't investigate yet, why it's not with the 1.6 default version.

OK, now I tested with vanilla 1.6.3... To be honest, I cannot reproduce the problem, hook is fired. :neutral_face: Tested with WP 4.9.8 and 5.0-alpha-43673, both PHP 7.2.10 FPM handler...

Potentially related to #105 (Database error for MySQL InnoDB database without innodb_large_prefix extension). > And I also have found an issue on a client website: > The table is set...

Both `?amp` and `/amp` are potentially AMP requests, but you're right, not in this scenario. `/amp/` with trailing slash is likely to be always wrong. We already do assume a...

Apparently we do some cleanup that removes a trailing `?amp` from the target variable: https://github.com/pluginkollektiv/statify/blob/23f9e3648957b17bb91cba77419e043ed87098bd/inc/class-statify-frontend.php#L94-L100 Original: `/root/my-page/?amp` After "generation of relative target URL" including `user_trailingshashit()`: `/my-page/?amp/` Then, if permalink structure...

The reference commit fa211b4 should solve the issue. But as stated before, I’m not entirely happy with the solution, because all 3 variants are potentially valid. No feedback so far....

I think that's what I actually wanted to check in this line :see_no_evil: ` $parsed_target` is accessed a couple of lines before and probably never unset.