I agree, with the caveat that "most" must be referring to the larger number of visitors posting questions, not the larger number of answers posted by a smaller number of contributors, nor the even larger number of readers who find an existing question and answer, read the answer, and leave with minimal interaction.
Most question-askers - who actually post a question - want to have a response customized to their exact problem. ChatGPT is infinitely patient, if a million users give it the same prompt a hundred times a day it will provide each of them an answer. They want to interact with it like a Discord chatroom - post a question, get answer.
Most answer-posters want to avoid posting the same response over, and over, and over. They want other users to interact with it like an encyclopedia of FAQs - or rather, questions frequently pondered but only asked once.
I'd argue that most answer-seekers probably want a single, high-ranking canonical question and answer as well; they don't want low-quality copy-pasted single-line responses in a chatroom. Maybe they upvote the pre-existing question, maybe they're just anonymous viewers. Stack Overflow the organization, like this group, wants the best-written, researched, articulated response to any particular question to rank highly on Google.
What's for sure is that no one looking for an answer ever wants to see "Closed as duplicate". The question is how you keep that from happening, unfortunately it's probably untenable to do anything but have a small cadre of community moderators (with all the self-selection trouble that causes) closing questions subjectively marked as duplicates and intensely frustrating the people who posted those questions. Nor does anyone want to (nor are they able to) scroll up through 500GB of chat logs to find a prior Q&A by someone else.
Most question-askers - who actually post a question - want to have a response customized to their exact problem. ChatGPT is infinitely patient, if a million users give it the same prompt a hundred times a day it will provide each of them an answer. They want to interact with it like a Discord chatroom - post a question, get answer.
Most answer-posters want to avoid posting the same response over, and over, and over. They want other users to interact with it like an encyclopedia of FAQs - or rather, questions frequently pondered but only asked once.
I'd argue that most answer-seekers probably want a single, high-ranking canonical question and answer as well; they don't want low-quality copy-pasted single-line responses in a chatroom. Maybe they upvote the pre-existing question, maybe they're just anonymous viewers. Stack Overflow the organization, like this group, wants the best-written, researched, articulated response to any particular question to rank highly on Google.
What's for sure is that no one looking for an answer ever wants to see "Closed as duplicate". The question is how you keep that from happening, unfortunately it's probably untenable to do anything but have a small cadre of community moderators (with all the self-selection trouble that causes) closing questions subjectively marked as duplicates and intensely frustrating the people who posted those questions. Nor does anyone want to (nor are they able to) scroll up through 500GB of chat logs to find a prior Q&A by someone else.