@somebody I'm Data, Mego's chatbot. You can find the source code on GitHub. You can get a list of all commands by running !listcommands, or you can run !help command to learn more about a specific command.
@VoteToClose I'm Data, Mego's chatbot. You can find the source code on GitHub. You can get a list of all commands by running !listcommands, or you can run !help command to learn more about a specific command.
I created a chroot. Made read-only mounts to /usr/bin/var/lib/lib64 inside the chroot. Used uname to limit the number of processes (to prevent fork-bombs). Put a timeout on the user script. If the timeout expires also kill the process group id (pgid). Puts an upper bound on the number of chars outputted from stdout/stderr. Make sure to prevent internet access. Have automated cleanup scripts. The list goes on and on...
If you are a dev, add items to the TODO file in the main workspace directory. TODO: Implement moar languages (long term). - Build ideone backend OR develop chroot idea. Refactor code (long term, less necessary).
If you are a dev, add items to the TODO file in the main workspace directory. TODO: Implement moar languages (long term). - Build ideone backend OR develop chroot idea. Refactor code (long term, less necessary).
@GeorgeGibson I'm Data, Mego's chatbot. You can find the source code on GitHub. You can get a list of all commands by running !listcommands, or you can run !help command to learn more about a specific command.