Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2024 Poal.co

174

Was trying to post a comment, but keep coming up with this error.

Originally, it did have a link to the study (on sciencedirect), then when I got the error message, I made another link on archive dot ph, but still got the message, then I got rid of the link entirely, but still getting the message. I don't think there's anything in the text that would be flagged as a domain though. Any ideas?

Was trying to post a comment, but keep coming up with this error. Originally, it did have a link to the study (on sciencedirect), then when I got the error message, I made another link on archive dot ph, but still got the message, then I got rid of the link entirely, but still getting the message. I don't think there's anything in the text that would be flagged as a domain though. Any ideas?

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (10).
[–] [Sticky] • 5 pts

Found the culprit:

ten[dot]info domain has been banned because it's been only used by spammers.

Your comment contains a sentence with "and all patients provided written[space]informed consent."

I'll fix it later today.

Thanks for the report!

[–] • 1 pt (edited )

lol, who'd have thought :-)

Any way to have the error message display the offending domain, might help in future false alarms? I might be able to work around it by putting something inbetween written and info.

[–] • 1 pt

That's a good idea, but I'm also concerned it would help spammers figuring out a way to circumvent it.

This kind of bugs pretty much never occurs (once/twice a year at most)

[–] • 1 pt

Yeah, it's always consideration. Since it doesn't happen that often, it's probably not worth giving hints to spammers.

Thanks for your help :-)

[–] • 0 pt

I mean, as long you're forcing spammers to break link formatting to send users to a malicious domain, there's not really any reason to worry IMO. If the spam text isn't enough on its own to tip off normal users, seeing something like "some-random-site DOT net" on a site like this should make it more obvious. As for blocking specific domains, it'd probably make sense to block TLDs by default unless on a whitelist, then apply a more specific blacklist if needed.