To @IzzySoft

[drogga]

@IzzySoft - Hi, there are no PMs or DMs here, so I decided to mention you here, so I can report that your repo site's anti-spam or whatever is there protection mechanisms are very strict and sensitive, for instance it sometimes cuts me off, just because I'm using 1DM's (IDM) Browser on Android or if I browse it a bit with JS off, maybe you can adjust that a bit...?

[IzzySoft]

No idea what exactly you mean, sorry. There's rarely any JS on any of my sites, so that part cannot be the problem. If you're looking for DMs: there are confidential issues in the GitLab repo I use for maintaining. If that's still too "public" (after all, GitLab is run by… well, on…), there's always the imprint with my mail address. To investigate I'd need some more details, like the exact time and IP address used and which of my sites you were on (the repo is included with 2 of them).

The only thing I could imagine hitting you is the "invasion filter" (to protect against massive scrapers). If it's that I can just suggest a slower pace, there's not much I can adjust there anymore without making it useless.

[drogga]

@IzzySoft I'm not looking for different site in order to reach\contact you, I don't use any other similar sites as GitHub, via E-Mail was a option, but you wouldn't know that it's me, the same dude that tagged you recently in the SkyTube repo and we did some conversation in a PR there.

It's probably the invasion filter then, which is too sensitive in my opinion, when it hits me I have to use a VPN. Purposely I just forced it by viewing couple of app's details and doing some unnecessary refreshes, the message I get in the Bromite Browser is:

This site can’t be reached

apt.izzysoft.de refused to connect. Try: Checking the connection

ERR_CONNECTION_REFUSED

IDK how much time it takes to clear this and become accessible to me again. I did go to /fdroid, but haven't to /redhat, /ubuntu & /ark.

[IzzySoft]

That definitely sounds like the one, yes. Every 2..3 years someone ends up there. But every day so many bots end in there which otherwise wouldn't. I fine-tuned it many times – so apologies, but I reached my limits there. Loosening the filter more would practicably rendering it useless.

[drogga]

If I message you my current IP, with which this happened, to info@izzysoft.de, would you be able to whitelist it or do something, or there's no point at all ?

At least it's static v4 (forever the same on that network), if it was dynamic - no chance \ point.

[IzzySoft]

I've asked for that to find the reason – but it seems we already found that. And no,I don't maintain a "personal whitelist", sorry – that would too soon become too messy. It's a personal site, not a corporate thing which generates income. And I won't communicate the exact settings here in an open Github issue. Yes, the "lock" is timed– that much I can say (all else would not make sense with dynamic IPs). But if you can tell me which of my sites you access (e.g. apt.* or android.*) I can take one more look at how I've configured that and if I can see a parameter which might help you without losing protection on my end.

[drogga]

It's apt.izzysoft.de, which is shown \ written in bold in the browser's message that I quoted earlier^, since you told me in the SkyTube PR to use that one, also because android.izzysoft.de/repo has no search field anymore, on which I told you that you can just kill it if you want to, when you shared that you are considering it.

[IzzySoft]

written in bold in the browser's message

Aw, missed that, apologies! Lemme see then… OK, adjusted a bit (this server did not yet have specific settings, now it has). Please see if this helps you, but don't exaggerate or it will still hit you :wink:

[drogga]

Thank You. Let's hope that it will be fine from now on, I browsed it a bit, but it will really show up when I have to actually digg \ search for something more extensively.

[IzzySoft]

Yupp, that's clear. The protection you triggered is the one against "mass-scraping" – normal use shouldn't have triggered it. And it should be a little more relax now (though not much). And reading your previous comment again in this context: Yes, android.* had a fine-tuning for that in place already (which I thought I had done for the other domains as well – turns out I did not).