Date and time in responses
Lumo doesn't give any indication of the time of the response. This is missing if one looks at later responses. And in general, it's good to time stamp events;-)
Marc Schulthess
shared this idea
-
Neko
commented
I want to add 4 more critical factos why this is critical to implement
1. reference number = we can clearly tell lumo "what i talked with you at x hour today" = lumo can more easilly tell where or what we are refering to
2. when lumo helps us with documents, emails, so on, a timestamp can be inserted
3. History log, as we all know Proton keeps working on Lumo and sometimes there are bugs, this can help keep track of dates, aka if some issues are actually new bugs that happened after an y new update. And of course this also means we can report more easilly bugs and similar.
4. websearch elements, since currently lumo, at least when i tested, is giving me mutiple random times, hours, timezones, even different dates. AND THE WORSE: if i check manually, all websites Lumo used as a source, are correct, meaning that lumo is reading an "old" entry or maybe there are anti bot mesurements? i am not sure honestly. Ideea is that due to cutoffs and similar, if lumo does web search, due to the time stamp, lumo will know where we are (time zone due to time VS randomly guessing), if a shop or somehting we plan is open, will close, etc, and of course, anything like outdated information vs up to date (websearch result that is not in the training data).
-
Raphael E.
commented
Timestamping can also solve problems with the AI model not having any idea what time it is currently or what date it is, provided that the AI model checks them before responding.