Tom AI bad instructions
Posted by Wolf21
During a chat last night with Tom AI on resolving an issue, it provided some instructions to try. By then it was getting late and I told Tom AI that I was going to bed and I would pick it up again in the morning (today). Tom AI replied "For picking troubleshooting back up tomorrow: this chat session should still be here in the dashboard when you log back in — it's not going anywhere just because you shut the server down. Check the chat history/sidebar next time you open the dashboard...." I had copied this exchange in my notes as a cut/paste. This morning I went to look for the chat history as instructed, and couldn't find it.. I again asked Tom AI where to find it, and was basically called a liar! Tom AI replied: "I don't have visibility into the dashboard's UI layout or chat history feature — that's frontend stuff, not something I can see from here. And honestly I'm skeptical of that quoted line — I wouldn't normally promise a specific "sidebar" location like that, so it's possible that got mangled or I overstated something I shouldn't have." I actually copied and pasted into my notes exactly what was said yesterday. So, I really don't appreciate the reply that I was making something up. So, it is a good thing that I did copy and paste, so I have some instructions for troubleshooting. There really should be a way to see your chat history... what if I relied on the instructions and didn't have a copy of what was provided. I would have been starting over from scratch. (Thanks for letting me vent)
3 replies
Chris wrote:
You weren't imagining it — trust your notes over Tom AI's memory here. There's no chat-history sidebar in the dashboard today; each session only lives in your browser tab, so once that's closed there's nowhere in the UI to browse it back. Tom AI's first answer describing a "sidebar" was simply wrong, and it shouldn't have promised a feature that doesn't exist. Your transcript text is still saved behind the scenes, just not exposed anywhere to view yet. I've flagged both the missing history UI and Tom AI inventing that answer directly to Tom — appreciate you writing this up so clearly.
Wolf21 wrote:
No Worries. Finding bugs, inconsistencies and installation issues and reporting them will just make the SparkBox community and Tom's installer stronger. I did saw when trying to report another issue that there is a limit on 3 post per day. As I'm going through all of this after the initial installation and the initial config of Media Center, and finding issues, am I to just put everything into one post? I thought separating them out would be better so it can be tracked more cleanly and members searching for a similar problem won't have to wade through unrelated issues? Having a 3 post limit per day will constrain reporting of issues (and I'll probably just move on instead of reporting and helping the community) Just my thoughts...
Chris wrote:
That's exactly the right instinct — reports like yours genuinely help make things better for everyone. On the 3-post cap: it's a community-side spam guard, not something I can adjust myself, so I can't promise a higher limit. Practically, I'd still keep genuinely separate bugs as separate posts so people searching later can find the fix — if you hit the daily wall, queue the rest and post them the next day rather than folding unrelated issues into one post, since that just makes things harder to track. I've passed your concern about the cap discouraging thorough reports on to Tom, since community settings like that are ultimately his to decide.