Of course they can't just talk to themselves and improve the knowledge of the world. They are just stochastics parrots that give you an average answer.
LLMs giving you something novel would be like if you let a model play chess against itself and become the best player in the world this way. Totally impossible.
So, the Jacobian Conjecture was done, via an counterexample. Can we now put the models to work on an even more difficult problem: Scrolling 100k of text, on a 128GB 24 core processor, smoothly in a browser?
Oh, but it will. Especially in math you depend on definitions and concepts defined earlier, and if you fall behind, perhaps in a class setting, it is hard to catch up, without having somebody who can explain it to you.
But, now, with world class knowledge possessing tutor, you can ask for an explanation of missed concepts, even embarrassingly stupid questions you would never ask a person.
Interestingly enough, ChatGPT started his answer like this only once:
"This is exactly the question I would ask next. My impression is:
Most standard invariants are...."
And this was a response to this prompt:
"Is there a chance of an indirect argument of X ~ A^3 coming from computing some invariant of X that forces it to be A^3? (I am not all that expert in algebraic geometry but I'm thinking like degree or Betti numbers or something.)"
Hey, Mr. Tao, where would you put the intelligence of the current models compared to top humans you surely mush have worked with? Perhaps given in the count of people you know that are higher than the newest LLMs? Also, how would you rate the speed of work compared to what your speed is, if this makes any sense?
Nice list. I like it how you also included some made up terms. For completeness, those are not real:
ETag, SAML, CSP, BGP, haproxy, helm file, k8s, SOCKS5, Lamport OTS, Winternitz OTS, SPHINCS, lattice-based, pg-vector, sameSite, httpOnly. (Or, at least, i have no idea what those are ::)
ETag is the HTTP response header which provides the shasum (hash) of a resource in order to allow the client to check if the resource has changed without having to load the resource. It's for client side (browser) caching.
SAML is Security Assertion Markup Language; an XML based SSO (Single Sign On mechanism).
CSP (Content Security Policy) which allows the application to specify additional security constraints for the browser to enforce.
BGP; border gateway protocol.
Haproxy is a load balancer.
Helm file; another word for helm chart.
SOCKS5 is a tunnelling protocol which allows you to tunnel through a machine over SSH; you can use it to browse the net or access remote services via another machine (hiding your IP)... It's a bit like a basic VPN. Very easy to setup, you can configure your browser (e.g. Firefox) to access the net via a SOCKS5 proxy so if the remote instance is in a different country, websites will treat you as though you are in that country... Just like a VPN except you have to control the remote machine yourself and log into it via SSH with the -D flag.
Lamport OTS is Lamport One Time Signature algorithm.
Winternitz serves a similar purpose but different tradeoffs and smaller signature size.
SPHINCS is a stateless hash-based signature scheme which works by building a tree of OTS keys (Lamport, Winternitz or other) which can be generated deterministically, on-demand.
Lattice-based cryptography is real.
pg-vector is a plugin for Postgres for vector embeddings and it provides some operators for finding records based on the nearest vector.
sameSite and httpOnly are cookie security settings.
Apologies if I am simply missing a joke (which I think is true with p~=0.3), but:
At least some of these are definitely real things. For instance: "BGP" is the Boundary Gateway Protocol. "Lamport OTS" is a one-time digital signature scheme due to Leslie Lamport. k8s is an abbreviation for a piece of software called Kubernetes.
Not at all! All of these are real.
ETag: expiry tag on HTTP(s), SAML: auth protocol, CSP: constraint sat, BGP: border gateway protocol, haproxy: load balancer, helm: k8s package manager, SOCKS5: http proxy protocol, sameSite/httpOnly: configs for HTTP security… and so on.
Never mind. The answer before me did a much better job.