News for hackers. Stuff that matters.
Re:Google I/O and the Coming AI Battles by sillysaurusx on Monday May 15, 2023 @08:27AM (#35947108)
Dude, or ma’am, thank you for mentioning these obviously-sponsored tweets.

How do they guarantee hundreds or thousands of likes? Presumably the only reason the algorithm keeps showing them to me is that they’re popular. Otherwise they’d be labeled “sponsored”.

The points are always so bad, too. I asked Bard to summarize one of my repos, and it hallucinated that it was an http server written in Go. My repo didn’t have a single .go file. “Internet-connected AI” is just mistaken.

Re:Google I/O and the Coming AI Battles by trasz4 on Monday May 15, 2023 @08:45AM (#35947289)
Twitter doesn't mark bot accounts as sponsored.

As to how - many ways, some of them really creative. One that I remember was an account that's reposting stuff that I genuinely liked, some left-wing activist content, and only now and then they would push something different, like a message about how this one time brand X turned out to be crap during a manifa.

Re:Google I/O and the Coming AI Battles by pclmulqdq on Monday May 15, 2023 @09:04AM (#35947495)
Most of the hype bots aren't labeled as bots. They are run covertly, and replaced when they get burned.
Re:Google I/O and the Coming AI Battles by jeroenvlek on Monday May 15, 2023 @08:52AM (#35947369)
Had a similar experience. Asked Bard to generate a Firefox plugin and it responded that it was a text-based assistant and couldn't comply [1] whereas ChatGPT just did it. It didn't work, but it still generated it.

[1] https://twitter.com/jeroenvlek/status/1657195209686683648

Re:Google I/O and the Coming AI Battles by trasz4 on Monday May 15, 2023 @09:21AM (#35947718)
>It didn't work, but it still generated it.

So neither could generate the plugin, it's just that one of them lied about it.

Re:Google I/O and the Coming AI Battles by jeroenvlek on Monday May 15, 2023 @09:45AM (#35948048)
No, I suspect it's more the case that ChatGPT could generate it anno 2021, but can't anymore due changes in Chromium (I switched to Edge ultimately) and the Gmail API and Google Cloud Credentials workflow that I tried to add to it later.

It was interesting to see that ChatGPT annotated its code with pitfalls to avoid, that it actually didn't avoid in the code.

Re:Google I/O and the Coming AI Battles by disgruntledphd2 on Monday May 15, 2023 @10:30AM (#35948757)
Just like a real human;)
Re:Google I/O and the Coming AI Battles by trasz4 on Monday May 15, 2023 @09:47AM (#35948077)
>No, I suspect it's more the case that ChatGPT could generate it anno 2021

Why? I mean, why does it sound more plausible to you that it ever could, when we have countless examples of models lying (or rather hallucinating)?

Re:Google I/O and the Coming AI Battles by jeroenvlek on Monday May 15, 2023 @10:11AM (#35948409)
Because it was trained on old documentation, but I see your point. My original point was also not necessarily that ChatGPT was correct, but that ChatGPT at least gave something to work with, whereas Bard simlly refused.
Re:Google I/O and the Coming AI Battles by badrequest on Monday May 15, 2023 @11:15AM (#35949539)
The company I work for is building a browser extension that involves ChatGPT, and we can unfortunately confirm that it is, in fact, not capable of writing browser extension code.
Re:Google I/O and the Coming AI Battles by throwwwaway69 on Monday May 15, 2023 @09:48AM (#35948090)
They carefully flood their tweets with likes from bot farms and once there’s a lot of inorganic activity it leads to a ton of visibility and therefore further organic activity