Wetfish Online
Discussion Forums => Shitpost Central => Topic started by: nicefish on July 26, 2017, 01:47:47 pm
-
All wetfish members get to push code to a repository. If it builds and passes some unit tests, the bot will automatically reload with the new code. If not, the commits will be reverted.
-
If it builds and passes some unit tests, the bot will automatically reload with the new code.
do you have any idea what that means
-
If it builds and passes some unit tests, the bot will automatically reload with the new code.
do you have any idea what that means
I'm not sure what you mean.
-
If it builds and passes some unit tests, the bot will automatically reload with the new code.
do you have any idea what that means
I'm not sure what you mean.
>people on the internet will get to push actual code onto a shell owned by whoever decides to host this
-
yeah Idk if "anyone can make the bot do whatever they want as long as it works" is a great idea. Maybe if we could vote on them or something before they're implemented. Otherwise seems like a great way to invite tons of channel flood at the very least.
-
If it builds and passes some unit tests, the bot will automatically reload with the new code.
do you have any idea what that means
I'm not sure what you mean.
>people on the internet will get to push actual code onto a shell owned by whoever decides to host this
but we'll know who did it, b/c only wetfish members would be allowed to push code.
-
yeah Idk if "anyone can make the bot do whatever they want as long as it works" is a great idea. Maybe if we could vote on them or something before they're implemented. Otherwise seems like a great way to invite tons of channel flood at the very least.
you can undo their changes. :)
-
yeah Idk if "anyone can make the bot do whatever they want as long as it works" is a great idea. Maybe if we could vote on them or something before they're implemented. Otherwise seems like a great way to invite tons of channel flood at the very least.
you can undo their changes. :)
yeah I'd rather have a system in place to prevent malicious changes in the first place rather than having to undo them
assuming someone notices the second channel flood starts, the channel is still flooding before the changes revert.
assuming said changes are as benign and noticable as channel flood.
-
rather have a single person (like, rachel) with power to commit and revert. automating human trust is seldomly a good idea.
-
rather have a single person (like, rachel) with power to commit and revert. automating human trust is seldomly a good idea.
then at that point it's just a collaborative IRC bot project
and that's not fun
-
rather have a single person (like, rachel) with power to commit and revert. automating human trust is seldomly a good idea.
then at that point it's just a collaborative IRC bot project
and that's not fun
everyone knows it's not fun unless it's ~*risky~*
(http://lessguide.com/wp-content/uploads/craigslist_guy.jpg)
-
rather have a single person (like, rachel) with power to commit and revert. automating human trust is seldomly a good idea.
then at that point it's just a collaborative IRC bot project
and that's not fun
everyone knows it's not fun unless it's ~*risky~*
(http://lessguide.com/wp-content/uploads/craigslist_guy.jpg)
did he shave hearts into his body hair
-
I'll make sure to change everything so it's only on one line
-
did he shave hearts into his body hair
he kinda reminds me of adrian xD
-
everyone knows it's not fun unless it's ~*risky~*
(https://scontent.fapa1-1.fna.fbcdn.net/v/t1.0-9/20525902_10159168595770224_8627773144164020036_n.jpg?oh=0935eb3fa15f504ec40052a8cb2c7657&oe=5A264A04)