Is it actually an error to not find an interned message in our db? I would expect that to be relatively likely, although I guess the live websocket connection would probably do that before a scrape.
Yeah this clearly seems like a bug. Seems like we should be setting this, or perhaps even storing this value in the database...let's just set it here for now though.
If we're going to be manually resetting the ticker after every tick, it might as well not be a ticker.
What happens if the user updates a message to remove a tag? Is there any path that will un-tag the snippet? Do we want that?
Do you want to handle that in this first pass? Seems like we should do something if the user does something that causes the message to be deleted - but would that cascade through this snippet elsewhere?
Random thought based on usage I saw on HMN - we need to make sure the tag parser can recognize tags in situations like:
If we think we might add more to this chain in the future, maybe we should add a setup like
Do we want to include application commands here? Seems maybe wrong. We probably won't be able to respond inline in the channel without the response getting nuked...