Live data from Hacker News

ChatGPT Launches 'Company Knowledge'

openai.com

71–73 of 73 posts

Re: ChatGPT Launches 'Company Knowledge'

#71

Earlier quoted context omitted.

Definitely. AI sex puppets would kill online porn faster than Betamax killed the XXX movie theater.

So actually I did not care about online porn. Was referring to actually the whole non-innovation of generative AI finally finding its niche in the very profitable sex-market and disappearing from other domains.

Ah, yes I understand. But wouldn't it be great if AI and online porn disappeared from the public domain together?

Re: ChatGPT Launches 'Company Knowledge'

#72

Earlier quoted context omitted.

So actually I did not care about online porn. Was referring to actually the whole non-innovation of generative AI finally finding its niche in the very profitable sex-market and disappearing from other domains.

Ah, yes I understand. But wouldn't it be great if AI and online porn disappeared from the public domain together?

I am not sure - online porn satisfies a market demand, and it's not like it is absolutely everywhere - you have to deliberately search for it. The so-called AI is omnipresent, but its not clear what actual problem it is solving, unless we count helping the Joe Bullshit in performing his bullshit job.

Re: ChatGPT Launches 'Company Knowledge'

#73

They still don't have any scoping for the connectors. There's ZERO way our legal team will let us connect ChatGPT to Google Drive for example. ALL of our GDrive. Specific directories, sure. But there's no way to do it.

mirror those directories to a different namespace or location let GPT drink it up obliterate the new namespace until you need to train it again; wash, rinse, repeat

Now do this for 300+ employees constantly. It's not sustainable.

We need scoped MCPs before any of this is viable.

The receiving end needs a setting that "user X's ChatGPT MCP can access directories [x,y,z] in Google Drive. This wouldn't require any changes to the MCP protocol in general.

OR the whole spec must be changed so that when an MCP is connecting, there is a negotiation about the scope (select which directories are shared) AND that list is checked on the receiving end against a whitelist of allowed directories.

Post reply on HN