> the extended jurisdiction of the GDPR, as it applies to all companies processing the personal data of data subjects residing in the Union, regardless of the company’s location
> Bad keyword in body, bad keyword in title, bad keyword in username, numbers-only title, phone number detected in title ---------- Title - Position 1-14: 2348147745661 Title - Phone number: 2348147745661 Title - Position 1-14: 2348147745661 Body - Position 1-14: 2348147745661 Username - Position 1-14: 2348147745661
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-20: errorsolutions.tech Body - Position 1-20: errorsolutions.tech Username - Position 1-20: errorsolutions.tech
> Blacklisted website in body, blacklisted website in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 5-24: errorsolutions.tech Title - Position 1-24: www.errorsolutions.tech Body - Position 5-24: errorsolutions.tech Body - Position 1-24: www.errorsolutions.tech Username - Position 5-24: errorsolutions.tech
Currently listening to: {'110-question-296701': ('296701', 'wordpress.stackexchange.com', 'question', '//wordpress.stackexchange.com/questions/296701', [])}
Not our problem. While it's likely not an on-topic question in it's current form, that's something for the site to deal with. Basically, it's not spam.
@ArtOfCode Maybe add in something about potential future swag: "keep an eye out, as this was successful... we plan on something more in the (near) future"
Yep, that doesn't make sense. We'll stop tracking referrals to deleted posts in the next build. Thanks for the heads-up.
