zlacker

If there is an incident where people can see other's people chats there are two possibilities:

-It's a server issue, meaning someone fucked up their javascript and cached a session key or something. It's a minor thing; could get the specific dev fired in the worst case, and it is embarrassing, but it is solvable.

-it's inherent to how the AI works, and thus it is impossible to share a ChatGPT server with someone else without sooner or later leaking knowledge. It would mean the company cannot scale at all cause they'd need to provide each client their own separate server instance.

If this was something Sam knew and kept it from the board, that'd be fireable. And it'd be catastrophic, cause it'd mean no useable product until a solution is found.

I'd somehow doubt it is something like this, but if we see security issues and private chats that keep leaking, it is a possibility.

>>elfly+(OP)
It's inherent to how it works, it is known and had always been known that nothing you type into these chats is private and there is nothing whatsoever fundamentally to stop the AI from just handing your chats to somebody else or dumping them out to the internet. They aren't even able to theoretically describe a mechanism by which you could provide a kind of memory protection for these models. And of course we have seen real examples of this already. Only a matter of time before the completely and totally insurmountable problems or scaling AI become clear. Sam is and has always been a conman in my view.

>>elfly+(OP)
It was absolutely, incontrovertibly the former. The go misstates the issue- users saw other people’s chat titles, not chats. It was just a web server thing.