-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add data from Slack to Wizard News #3330
Comments
On the cost side, I don't see the cost increasing that much. Even if it was 10x, it'd still cost less than 5$ per day. But maybe I'm missing something, and it could be a larger increase? |
I have no idea to be honest, I was just surprised that just github PRs cost $0.35. I expect that Slack contains much more information (that doesn't have to translate into size though). |
@Marigold From what I quickly inspected, the current system prompt includes much of our documentation (e.g. docs for |
Could be a good cooldown project, or something for over Xmas. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The News app in Wizard provides a summary of key events in the ETL repository over the past 7 days. This summary is generated from all PRs stored in MySQL.
It would be interesting to apply this concept to all communication in Slack and see if we can generate useful summaries. For example, we could track dataset updates, article or insight changes, projects, bugs, and more. Since many of our apps already send data to Slack (e.g., GitHub updates, bug reports), Slack essentially functions as our communication "data warehouse."
Risks
This could become pretty expensive. We pay $0.35 for News summary which includes just Github activity. We should think carefully about what to include there and what not.
If we store Slack data in MySQL, we have to make sure it's excluded from Datasette public.
The text was updated successfully, but these errors were encountered: