GuillaumeRossolini

@Maroon no it just wasn’t verifying anything at all, but now it’s fixed. Thanks

@Maroon FIY the security verification for my not being a bot failed

@Dust0741 you could also get each container to access the other by specifying the stack prefix

Say you have stack1 and stack2

Stack1 can have

networks:  stack2_default:    external: trueservices:  foo:    networks:      - default      - stack2_default

@mfed1122 yeah that is my worry, what’s an acceptable wait time for users? A tenth of a second is usually not noticeable to a human, but is it useful in this context? What about half a second, etc

I don’t know that I want a web where everything is artificially slowed by a full second for each document

@Passerby6497 yes I’ve been told as much 😅

https://lemmy.world/comment/18919678

Jokes aside, I understand this was the point. I just wanted to make the point that it is feasible, if not currently economically viable

@rtxn all right, that’s all you had to say initially, rather than try convincing me that the network client was out of the loop: it isn’t, that’s the whole point of Anubis

@rtxn validation of what?

This is a typical network thing: client asks for resource, server says here’s a challenge, client responds or doesn’t, has the correct response or not, but has the challenge regardless

@mfed1122 @tofu any client-side tech to avoid (some of the) bots is bound to, as its popularity grows, be either circumvented by the bot’s developers or the model behind the bot will have picked up enough to solve it

I don’t see how any of these are going to do better than a short term patch