Skip to content

Instantly share code, notes, and snippets.

@Zirak
Last active August 29, 2015 14:02
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Zirak/f1883eedd560bff51107 to your computer and use it in GitHub Desktop.
Save Zirak/f1883eedd560bff51107 to your computer and use it in GitHub Desktop.

Vote results:

commandvotes
awsm16
norris14
domain13
zalgo13
meme11
inhistory9
todo8
color7
findcommand7
parse7
timer7
convert6
github6
user6
refresh5
spec5
info4
nudge4
unsummon4
unonebox4
urban4
ban3
live3
stats3
summon3
undo3
xkcd3
listen2
eval2
forget2
unban2
jquery2
die2
stat2
youtube2
help1
listcommands1
tell1
define1
mdn1
wiki1
afk0
google0
learn0
welcome0

n = 51, Q3 = 7. Votes >= Q3:

coffee      awsm        color       doge        domain      findcommand hang
inhistory   meme        mustache    moustache   norris      parse       timer
todo        weather     zalgo

Dropped from race (will stay in bot despite votes):

  • coffee (used as c>, will just be re-requested later)
  • doge (frequently used by some)
  • mustache, moustache (frequently used by some)
  • hang (history)
  • weather (used)

After dropping:

n = 45, Q3 = 6. Votes >= Q3:

awsm        color       convert     domain      findcommand github
inhistory   meme        norris      parse       timer       todo
user        zalgo

These commands will be removed.

@ralt
Copy link

ralt commented Jun 7, 2014

I'd argue that !!convert is well used too. Last usage was tuesday, for example.

@Zirak
Copy link
Author

Zirak commented Jun 7, 2014

@ralt And before that?

Okay, I'll agree to "deprecating" the ones who weren't pretty unanimously agreed upon. They'll reply with "This command is deprecated. If you really want it to stay, ping Zirak". We'll see what happens after a month.

@allquixotic
Copy link

Kinda sad to see zalgo, meme and convert go. Well, "go" -- I maintain a fork of the bot, so they're not actually going anywhere if I don't want them to. :P

I guess my "vote" (if I get one) on this issue from the SuperUser crowd is that you can go ahead and nuke all the commands you want, and I'll use my super duper magical powers of git cherry-picking to keep the commands we still want. Maintenance may get interesting if you start breaking core bot APIs, but we have some JS hackers on our side too, so we can probably figure something out.

@towc
Copy link

towc commented Jun 7, 2014

you can't remove norris!
1: that command is just awesome
2:
a: he will look for you
b: he will find you
c: he will kill you

@SomeKittens
Copy link

I still don't see the point of removing commands.

@ryankinal
Copy link

I kind of agree with @SomeKittens, actually. What is the purpose of removing commands? Is it just to clean up listcommands?

@Zirak
Copy link
Author

Zirak commented Jun 9, 2014

@SomeKittens, @ryankinal: Because some things like /github and /findcommand were just never used. Why have something nobody uses?

@allquixotic If you people are using removed commands, just yell at me. As said above, I did it for commands which seemed to never be used, so if they are...

@rlemon
Copy link

rlemon commented Jun 10, 2014

I would love if convert were "easier" to use. It is a great idea but as is I can open a new tab and google faster. and doesn't parse get used internally? I never used the command but after peeking at it, might be useful for testing before user taught commands. I vote we bring parse back!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment