Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

BotD is blocked by Easylist #66

Closed
zoontek opened this issue Sep 2, 2022 · 3 comments
Closed

BotD is blocked by Easylist #66

zoontek opened this issue Sep 2, 2022 · 3 comments

Comments

@zoontek
Copy link

zoontek commented Sep 2, 2022

Hi 馃憢
Since a few days, we notice BotD domain is blocked by Easylist: https://github.com/easylist/easylist/blob/master/easyprivacy/easyprivacy_trackingservers.txt#L78

Screenshot 2022-09-02 at 10 38 06

Is it because BotD script is served on the same domain as Fingerprint? Because BotD is not a tracker.
Would it be possible to use a different domain / a custom domain (this setting is available for Fingerprint in the dashboard)? We had to fallback on captcha, it makes user experience horrible 馃槙

@Romchela
Copy link
Contributor

Romchela commented Sep 5, 2022

Hi @zoontek,
We are going to make BotD fully open source project without backend (see #65), ETA of the first version 1 month.
It should aggregate all basic bot detection techniques. So, we don't support old BotD version right now.

Also, we will have PRO version that includes advanced detectors and you will be able to activate it in our Dashboard. In this case you can use subdomain integration to be safe from any blocking.

@zoontek
Copy link
Author

zoontek commented Sep 5, 2022

Hi @Romchela,

I saw that after opening the issue, asked the support to activate BotD product on our account.

I also have a quick question: since the verify counter seems to have be removed from the API response, how to be sure that a requestID is not re-used multiple time? Do we have to setup a cache on our side to perform a similar check?

@Romchela
Copy link
Contributor

Romchela commented Sep 5, 2022

I also have a quick question: since the verify counter seems to have be removed from the API response, how to be sure that a requestID is not re-used multiple time? Do we have to setup a cache on our side to perform a similar check?

Checking timestamp of the request is actually enough.

@zoontek zoontek closed this as completed Sep 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants