OnionAccessGateway

I build this and it works. (PHP solution + Nginx configuration)

Simple anti-ddos queue for web in Tor.

https://codeberg.org/mnull/OnionAccessGateway/

Any feedback is appreciate.

Feel free to use it.

Post about it on Pitch: https://pitchprash4aqilfr7sbmuwve3pnkpylqwxjbj2q5o4szcfeea6d27yd.onion/p/14857c4e

So does /d/EndGame

please push this to git.shadowvault.eu or http://vaultx6efhvgbprblgo3hzi5knpgitsrcgciqrbkbawzvbhizlw77hyd.onion if you are comfortable with ssh

EndGame is more complex. My project is for users who looks for basic and simple solution.

Good on you for trying, and props to making it open source, but even by AI slop standards this isn't great. To anyone looking at this as a viable option: this is not for production. Ever.

maybe an amateur query, is this simple queue to slow down requests enough to tackle the ddos attacks? since, famous websites like tforum, pitch, drughub have tough to perform image-related tasks, requiring reading an image and typing in like tforum, or selecting some specific part of the image?

Since i'm thinking to host a service, so will those image captchas an overkill to just start out, and i should start with simple ones like this? or what do you guys suggest...

Yes, EndGame and other CAPTCHAs are excessive for new websites. Focus on running your website first, and only implement additional protection once it becomes more popular and you identify some issues. Prepare something, test it in the development environment, and only enable it when needed, not from the beginning.

I understand that you have already hosted some services as hidden services, and that you have had issues related to cloning, DDoS attacks and high resource usage due to bots/scripts. You implemented my solution, but it didn't work, did it? I believe you are just writing what you think without providing any proof or evidence. Otherwise, provide some specifics examples, and I will gladly review them and refine my solution. Otherwise, shut up forever.