Important design consideration for bots (summarizing)

[mochet]

There have been multiple new developments with bots which are great, however there are two aspects that should be considered when designing them. I mention these because the current scale of the testnet is small, with a lot more activity they may need to be changed to address these.

1. Summarizing multiple events. The bots currently show every required chain event, like adjusting a worker's payments or every forum post. If we start having many more workers or much more forum activity the bots will probably need to change to a system of summarizing events over the past hour or few hours in order to reduce spam.

2. Screen real estate. This is probably a decision that needs to happen on each individual bot, but here are some basic notes:

• Council election stage events (such as new election started). This event happens once per week (or whatever council duration is), its a highly significant piece of information so the message for it can be quite large and detailed.
• Salary updates. These are infrequent right now, but in a scenario where a working group has 100 workers it would mean that there current use would involved many notifications as well as each notification containing quite an amount of detail.
• Forum posts. These may happen 20-30 (or even 100+) times per hour. Depending on how many there are the detail of each notification may need to be scaled back in order to minimize their space.

[mochet]

One alternative approach is that all the bots are combined into one, and an hourly summary or something is put wherever it is needed and customized for that area.