Great job, guys.

In case you're looking for additional ideas, I was wondering if you might consider something. If users are writing software that repeatedly polls the server with time-consuming requests (e.g., retrieve all recent posts in channel x), it may increase system-wide performance if we offered an API to register for notifications (e.g., the user's software registers once for notifications upon start-up, and then the server sends it a notification when there is a new post). This would cut down considerably on server network traffic, web service requests, database requests, and CPU cycles).

Please understand that my goal is not to make bot development more convenient. Rather, my goal is to avoid situations where several bots are making repeated server requests, only to dump most of the retrieved data on the floor, and then repeating that over and over.

One idea would be to make a list of the typical bots that people are using (I've seen quite a few in tutorials written in user posts), and then perform an analysis to see which type of server request is wasting the most resources. That would be the best candidate for developing a notification.

It's just a suggestion. I've seen some serious performance issues over the last couple of days, so I think it might be a good idea to start a conversation on ideas to improve.