@dgerard
Shouldn’t this be linking directly to
https://pivot-to-ai.com/2024/10/26/whoops-google-copilot-perplexity-push-scientific-racism-in-search-results/
?
…
By the way, re the subheading “It can’t be that stupid, you must be prompting it wrong” -
I saw that comment made here on Mastodon in al seriousness just the other day, with a sample of the “correct” prompt that included a misprint rendering much of it meaningless.
According to the poster, he’s been using it regularly with satisfying results (or “satisfactory,” but that seems less plausible).
this is a Lemmy thread, and the behavior you’re seeing is a mismatch between how Lemmy and Mastodon handle links. on our end, it’s a direct link to the pivot-to-ai url. the version of this post federated to Mastodon links to our Lemmy instance’s thread instead, presumably to drive engagement (note that that’s not my decision as an instance admin, and I’d probably have it federate differently given the option)
probably some whacky shit with how it emits the AP Post object
it’s been a while since I looked into that code but I remember it being a bit weirdly trampolined for how it pulls fields together for the final emitted object/blob
this seems more like a Mastodon thing, considering that if I curl the post with Accept: application/activity+json it doesn’t have a link to the Lemmy thread, it has the link actually embedded in the post
I think Mastodon does this for other AP object types (like articles, e.g. if you put a link to a WriteFreely article into Mastodon it’ll just show the title and a link to the original post)