When I started this project 2 years ago, I envisioned that it would be a bot neatly packaged into an executable, perhaps similar to mIRC, and people could write simple python scripts which can be dynamically loaded and unloaded in order, without worrying about things like networking / AJAX loop.
However, various efforts to develop a fully functional bot seems to always be stalled for various reasons.
- https://drrr.com is closed source.
- The only way we can test our bot is against the running instance.
- There are obstacles to testing our bot against the running instance, in particular the rate limit and simultaneous connection limit and CloudFlare.
- There are many undocumented features of https://drrr.com such as game room, which we may or may never figure out.
- Programmers (myself included) are wary about spending time to come up with a well architected open source program for some closed source service which may not be maintained in the future.
I propose that we, as bot enthusiasts, consider developing a drrr-compatible server/website first, a clean room implementation of ajax.php, likely in something other than PHP, before we continue to work on the bot. With our own working open source server, I believe that we will not hesitate to put more effort into the bot, as well as come up with more enhancements between our server and our bot (such as using websocket instead of long polling), because our bot will no longer be tied to https://drrr.com , even though we will continue to support its protocol for the foreseeable future. I do not believe the effort will be too huge, think about it, there is very little/minimal logging at least for the frontend, no authentication (just a simple reimplementation of tripcode), only one person is room owner at any room at one time; it should be basic OOP.
Let me know what you think below.
When I started this project 2 years ago, I envisioned that it would be a bot neatly packaged into an executable, perhaps similar to mIRC, and people could write simple python scripts which can be dynamically loaded and unloaded in order, without worrying about things like networking / AJAX loop.
However, various efforts to develop a fully functional bot seems to always be stalled for various reasons.
I propose that we, as bot enthusiasts, consider developing a drrr-compatible server/website first, a clean room implementation of
ajax.php, likely in something other than PHP, before we continue to work on the bot. With our own working open source server, I believe that we will not hesitate to put more effort into the bot, as well as come up with more enhancements between our server and our bot (such as using websocket instead of long polling), because our bot will no longer be tied to https://drrr.com , even though we will continue to support its protocol for the foreseeable future. I do not believe the effort will be too huge, think about it, there is very little/minimal logging at least for the frontend, no authentication (just a simple reimplementation of tripcode), only one person is room owner at any room at one time; it should be basic OOP.Let me know what you think below.