←back to thread

Google AI Overview made up an elaborate story about me

(bsky.app)
693 points jsheard | 2 comments | 01 Sep 25 14:27 UTC | HN request time: 0.64s | source
Show context
AnEro ◴[01 Sep 25 15:23 UTC] No.45093447[source]▶
I really hope this stays up, despite the politics involvement to a degree. I think this is a situation that is a perfect example of how AI hallucinations/lack of accuracy could significantly impact our lives going forward. A very nuanced and serious topic with lots of back and forth being distilled down to headlines by any source, it is a terrifying reality. Especially if we aren't able to communicate how these tools work to the public. (if they even will care to learn it) At least when humans did this they knew at some level at least they skimmed the information on the person/topic.
replies(8): >>45093755 #>>45093831 #>>45094062 #>>45094915 #>>45095210 #>>45095704 #>>45097171 #>>45097177 #
geerlingguy ◴[01 Sep 25 16:01 UTC] No.45093831[source]▶
I've had multiple people copy and paste AI conversations and results in GitHub issues, emails, etc., and there are I think a growing number of people who blindly trust the results of any of these models... including the 'results summary' posted at the top of Google search results.

Almost every summary I have read through contains at least one glaring mistake, but if it's something I know nothing about, I could see how easy it would be to just trust it, since 95% of it seems true/accurate.

Trust, but verify is all the more relevant today. Except I would discount the trust, even.

replies(8): >>45093911 #>>45094040 #>>45094155 #>>45094750 #>>45097691 #>>45098969 #>>45100795 #>>45107694 #
freeopinion ◴[01 Sep 25 16:32 UTC] No.45094155[source]▶
prompt> use javascript to convert a unix timestamp to a date in 'YYYY-MM-DD' format using Temporal

answer> Temporal.Instant.fromEpochSeconds(timestamp).toPlainDate()

Trust but verify?

replies(3): >>45094353 #>>45094358 #>>45096304 #
eszed ◴[01 Sep 25 16:51 UTC] No.45094358[source]▶
I mean... Yes? That looks correct to me°, but it's been a minute since I worked with Temporal, so I'd run it myself and examine the output before I cut and paste.

Or have I missed your point?

---

°Missing a TZ assertion, but I don't remember what happens by default. Zulu time? I'd hope so, but that reinforces my point.

replies(1): >>45094438 #
nosianu ◴[01 Sep 25 17:00 UTC] No.45094438[source]▶
I would also read the documentation. In the given example, for example, you don't know if the desired fixed format "YYYY-MM-DD" might depend on some locale setting and only works because you happen to have the correct one in that test console.
replies(2): >>45094572 #>>45103572 #
MobiusHorizons ◴[02 Sep 25 14:27 UTC] No.45103572[source]▶
I’m pretty sure toPlainDate() returns an object not a string.
replies(1): >>45124655 #
1. nosianu ◴[04 Sep 25 07:41 UTC] No.45124655[source]▶
???

What does that have to do with my comment?

The OP explicitly wrote

> prompt> use javascript to convert a unix timestamp to a date in 'YYYY-MM-DD' format using Temporal

replies(1): >>45128498 #
2. MobiusHorizons ◴[04 Sep 25 15:39 UTC] No.45128498[source]▶
> answer> Temporal.Instant.fromEpochSeconds(timestamp).toPlainDate()

The answer ends in `toPlainDate()` which returns an object with year, month and day properties. ie it does not output the requested format.

This is in addition to the issue that `fromEpochSeconds(timestamp)` really should probably be `fromEpochMilliseconds(timestamp * 1000)`