brymastr / foobot Goto Github PK

Move the classification model (.json) to git large file storage. Once foobot starts training it's own model then we want to save it to a file instead of training each time the app starts. If there are 2000 classifications then this json file will get substantially larger and can't be trained every startup.

Enable users to subscribe to a "channel" with parameters. A channel can be anything foobot is updated about but doesn't tell users about unless they subscribe to the channel. Example: Weather updates. Example: Condo entries. Users can be automatically subscribed to a channel, for instance, if a user sets up condo entry then they will be notified when someone enters, however, a user can also unsubscribe from such notifications. Make this a button UX.

Subscribe to updates on a tracking item from Canada Post. Make this generic if possible so that other shipping services can be used.

Be able to ask foobot where the telegram webhook is set to

Facebook login so that we can have user accounts and store data against a specific user. Some things like rememberies and reminders can only work if there is a user attached to the account. This will also allow for users to talk to foobot on any platform and have all their rememberies accessible.

Ask foobot to show open issues for a specific project

Hey foobot, show me open issues for the current project

have foobot leave a chat if something negative is said about him

Recommend a whisky based on flavor preference and price range

hey foobot what whisky should I buy? I don't want to spend more than 30 dollars.

Have foobot be able to create new GitHub issues

Ask foobot questions and have wolfram answer them

The current username in Telegram is @dorsaydevelopment_foo_bot. I think that's ok to keep as is, but I'd like to rename him from FooBot to Mortimer (or Morty)

Google Assistant can remember things for you. You just say "Remember my bike lock code is 1234" and it will keep that info memorized for you. There are some security concerns here especially regarding group conversations and database encryption.

• Have users set an encryption key (hash salt) for their rememberies
• hash memory values in the database with the user's salt, don't encrypt keys (quick lookup)
• Store rememberies either in a new table called Memories, or on the user object
• Don't write rememberies to group converstations

Foobot to learn and classify messages as they come in.

Learn the message subject.
Create a new topic if the message doesn't apply enough to one topic specifically enough.
watch as foobot takes over the world.

When talking to a bot account one-on-one a user would likely expect a response from every single message. When talking in a group foobot should only jump in when addressed or when message content is applicable.

Interface with Mark's condo entry app to lock and unlock the apartment entry door

Make all foobot repositories public

• foobot
• foobot-web
• foobot-compose

Maybe use Hashicorp Vault? Or just environment variables. Or most likely just a child config.js file that isn't stored with the git repository that you can pass around between dev/test/prod environments

Get foobot access to the Questrade API. Teach foobot about high frequency trading. Firstly, learn about it yourself.

Foobot formulates a response by reading the message content. The response is created based on the topic. Write a bunch of unit tests to ensure topic classification is being done correctly. Don't test the response content, the goal is to have foobot write his own.

Redesign foobot to use RabbitMQ and separate service logic into its own containers.

Self explanatory

A generic endpoint to send messages to users from external sources. Good way to notify users of Condo entries