sharenowtech / erna Goto Github PK

Add a cancel button to cancel the updating/cancelling of a sign up for lunch date.

Ask after finishing the signup process if the bot can change the profile's status to something like

🍽 up for the next lunch in <location>

Stored events can be used to get insights into several usage-related stats.

{
  "type": [create|update|delete],
  "timestamp": [timestamp in ms],
  "location": [selected location, just for signups and updates],
  "user": [userId]
}

Trigger additionally Google Analytics custom events

Currently there’s no authentication implemented so that as soon as an attacker knows the URL he would be able to attack.

Use Slack’s authentication and tokens to authenticate every single request. Deny access in case of missing or invalid token.

To make the flow even more convenient, open a direct message between all match partners instead of texting each in a DM. So the people can start chatting right away. That's especially for matches between three people.

Proposed request flow:

1. create a group (not channel)
2. if successful, send a message introducing each other to this group
3. if failed, broadcast a message to every single member

As a user/admin I'd like to customize the max. group size of a match — currently the group size is 2 (+ 1 in case of an odd number of members)

In order to update the service easily and without interruptions, persistence needs to be introduced (optionally). For this purpose, new storage providers should be implemented that require only minimal configuration via environment variables.

Ideas:
– HubDB
– Firestore
– Redis Lab
...

Store the userId after signing up in a list to detect first-time users.
This list can be used to send differing messages based on the usage, so first-timers get a more descriptive introduction.

• Provide some basic instructions and hints via /<cmd> help to clarify the exakt workflow and the functionality.

• detect first-timers for more descriptive introductions

• more versions per message type