41–50 of 126 posts
I'd say "just chatgpt it"? is closer to being in the lexicon and this url just doesn't roll off the tongue
>"here let me search.chatgpt that for you"
There I was hoping sama-gpt5-chatbot had some creativity chops for naming new things but they must have decided not to use it this time.
Search chatgpt ah but you repeat yourself, we already use LLMs to replace this antiquated notion of loading webpage snippets and pointing me in 5 different directions. I'd say "just chatgpt it"? is closer to being in the lexicon and this url just doesn't roll off the tongue >"here let me search.chatgpt that for you" There I was hoping sama-gpt5-chatbot had some creativity chops for naming new things but they must hav…
I'm taking this opportunity to once again ask for the widespread adoption of the Name Constraints extension in x509, and subsequent roll-out of constrained intermediate CA certs signed by a publicly trusted root. Would be so convenient to have an intermediate CA cert constrained to *.my-name.com to avoid situations like this. Being forced to either use a private PKI infrastructure or using wildcards to not leak host…
If your organisation is competent enough to handle an intermediate CA certificate safely, you're certainly competent to handle a wildcard cert safely which is a much easier task.
Sadly it's unlikely you'll ever see the Name Constraints extension adopted. All it takes is one model of 15 year old smart TV failing to respect it, and the CA/Browser Forum will consider it too dangerous to allow.
Earlier quoted context omitted.
Unless this is the Microsoft deal, and they're using Bing as their indexing backend.
"chat gee pee tee search" is a terrible name. In comparison, bing is genius
I am guessing that this falls under the "we will steamroll" clause of OpenAIs gradual move towards AGI.