General > General Technical Chat
Should the EEVblog Forum go private to prevent the robot uprising?
T3sl4co1l:
No, but an automatic check feature would be nice -- "this post flagged as xx% likely AI generated" or a "check this on IsPostAIGenerated.com".
I suppose it'll be some months (years?) before such a service trickles down to a forum plugin (and/or is affordable enough at scale?), but, well, to say I can envision such a feature I guess.
I would guess it needn't be burdensome on the server(s) if it's just an async request and the result gets chucked into the database (post has not been reviewed / post reviewed as x). And maybe a button to queue a recheck / increase priority, but not actually force a request since that would be easily abused. Or maybe by then, a suitable IDing model will be available that runs on the server without slowing things much.
Tim
ejeffrey:
I've been a regular form user for over a decade, but I still often follow search results here. Having the form private would be a pretty big negative impact for me. The forum search is... bad to terrible, and even if it wasn't, I don't want to separately search multiple forums and stack exchange.
Also, as someone who does provide answers to questions free of charge here and other places, I don't really care if AI bots ingest that and then spit it back to other people. It's not a business for me, and if a computer program can organize what I said along with others and make it more useful and accessible that's fine with me. This depends on the nature of the form -- like if this were a photography or creative writing forum where people were soliciting feedback on their craft I would 100% make it private to avoid that being ingested into GPT-N. But a forum primarily focused around providing information and knowledge doesn't seem like it should get locked up.
In the other poll I am in favor of banning AI posts, just not making the foum members only.
EEVblog:
Might as well lock this thread as the discussion should move to the bot banning thread.
Navigation
[0] Message Index
[*] Previous page
Go to full version