potato tv

[mwarkentin]

Provide a hero view for recent gibben potatoes for display on a TV in the office (taco example):

[cleptric]

I'm actually a big fan of this feature 🙂
Right now, we tried to stick with the principle of data minimization, so we only store the sender, receiver and amount in the DB.

id	sender_user_id	receiver_user_id	amount	created
01fcde6e-2cfa-41d3-83b2-b7c6d9d8992b	c0eeecae-424b-442b-976a-583e0d105e3d	6a65f938-6910-485e-b2a8-2f9481bf29e9	1	2022-08-26 13:20:03

[mwarkentin]

Could we set a retention limit for data that matches our Slack expiration time?

[cleptric]

That's actually a very good idea!
We could just drop the content of a new "message" column for records older than 30 days.
This would still allow us to build Potato TV and be in sync with the Slack retention policy.

[0Calories]

Another option might be to store the Slack message ID in the DB, and then fetch it via the Slack API to get the message content?

[cleptric]

@0Calories That's a great idea as well! 🥔