gempesaw / flowbot Goto Github PK

A command that lists day-specific lunch deals we know about.

Example output:

User: .lunch
flowbot: Lunch deals for today:

• Double Stamp Tuesday at Fado's
• $3 discount on pies at YourPie!

Data could be stored in a local database, a service like contentful or a plaintext file on the filesystem.

.alias 'minhEmail=[email protected]'

so if someone does .enhance at 1AM, then yesterday's cupcake will be cached for the new day

i don't know your gmail acc or phone number so this is an instant message

https://discord.gg/3k9X2At

@weirdwater

Right now data is stored within the application. I think it would be more convenient to store data in a separate data-source. That way content could be updated without restarting the application.

I suggest using contentful. It's free and pretty easy to set up. Also there is a Javascript API.

A few other ideas:

• Local database
• Other database service like firebase, etc.
• JSON files in a /data directory

Hosting our own service (with a service like Digital Ocean) would be another option, but too much work. 💩

• .set commandName response: After anyone runs this command, .commandName becomes a valid command, and flowbot should return response to it. Rerunning this command with a different response should overwrite the previous value, allowing for maximum troll. Additionally, these should be available via 1-on-1 chat, so that things can be really confusing.
• .unset commandName: This should delete the .commandName user defined command. It should not be able to delete a hardcoded commands. If .commandName doesn't match an existing user defined command, no-op.
• .help: The .help command should have a new section for user defined commands

Probably the thing most of interest here is where to store the commands. See #7. Writing them all to one json file seems okay, except then we'll get simultaneous read/write issues, so maybe each command is a separate file? (name of file is command, file contents is response?). Or, contentful/firebase/what have you...

node-flowdock currently depends on buffertools which doesn't install on windows and I'm too lazy to figure out why. BUT! we can make a branch on our fork of node-flowdock, merge the two outstanding PRs, and reference our fork branch directly in package.json and hopefully circumvent the dependency issue entirely.

also then @mnguyen36 won't have an excuse not to test c: