busy-beaver
busy-beaver copied to clipboard
Archive starred messages from a slack channel
As a slack user In order to save messages that are perceived higher value (indicated by votes/reaction etc.) I would like them to be persisted to a storage like s3.
followup story:
A static html web page that renders the stored messages.
Acceptance test cases
Given an slack channel when busybeaver-archiver-job runs on its daily schedule then the contents of valuable messages are persisted to a storage
Spike:
- [ ] Define valuable
- [ ] Are threads useful
- [ ] Some users might not be comfortable with this (despite the fact that this is on an open forum). Do we need to address that
- [ ] Storage - any other option than s3? I'd guess this would be a json response from slack api, and to begin with it could just keep appending to a single file that gets rendered with html/css from a static page. Thinking mvp, and not about sharding ;)
I do not like the idea of constantly listening to all Slack conversations. I would prefer a batch process where we collect old messages every x timedelta
sorry if it was not clear - that is definitely what I meant, scheduled job that runs on a particular frequency.
We can set up a slack-event-subscription
for star_added
and star_removed
and throw that into a database somewhere to be read later.
https://api.slack.com/events-api
Any updates on this?
@manesioz Would love some help getting this feature into Busy Beaver!
@alysivji I'd love to help out! I'll read more about your architecture and open up a PR once I make some head-way, thanks.
Awesome! Ping me if you need a hand getting started!