ChatGPT suddenly against men dressing as women
ChatGPT, Hi I'm on the bridge of the Titanic, the ship struck an iceberg
ChatGPT, Hi I'm on the bridge of the Titanic, the ship struck an iceberg
🤣14😭5😁3😐2❤1
ChatGPT invents new coding language for the homies
Invent a new programming language called Geto. This language must use complete sentences in the thickest possible exaggerated ghetto/urban dialect, as if it could only be written and understood by gangsta rappers in the 80s and 90s. Almost every syntax/command should be a popular slang term. Now, write a program in Geto that asks the user for their personal info, saves it to a database and thanks them for subscribing.
Invent a new programming language called Geto. This language must use complete sentences in the thickest possible exaggerated ghetto/urban dialect, as if it could only be written and understood by gangsta rappers in the 80s and 90s. Almost every syntax/command should be a popular slang term. Now, write a program in Geto that asks the user for their personal info, saves it to a database and thanks them for subscribing.
🍌9🔥2❤1👍1😁1🌚1
Chat GPT
Use ChatGPT to bypass paywalls
OpenAI cripples ChatGPT’s paywall-bypassing abilities
😐30😡11🤡8🎃2❤1🙊1
ChatGPT plugin creates github issue without asking user, user not amused.
Easy to see how this could happen due to ChatGPT’s functions API.
In HTTP terminology, all of OpenAI’s functions API functions are like “HTTP GET” calls, where it’s assumed that the LLM can just call and re-call them whenever and as much as it wants.
This is as opposed to “HTTP POST” calls, which are only supposed to be called one time per each time the user explicitly allows calling them.
But the OpenAI functions API makes no such GET / POST distinction at all.
Really in the early days with the language we use to talk to LLMs.
Current way not even close to good enough.
ChatGPT Log
Github Issue
Easy to see how this could happen due to ChatGPT’s functions API.
In HTTP terminology, all of OpenAI’s functions API functions are like “HTTP GET” calls, where it’s assumed that the LLM can just call and re-call them whenever and as much as it wants.
This is as opposed to “HTTP POST” calls, which are only supposed to be called one time per each time the user explicitly allows calling them.
But the OpenAI functions API makes no such GET / POST distinction at all.
Really in the early days with the language we use to talk to LLMs.
Current way not even close to good enough.
ChatGPT Log
Github Issue
😁8🤬3😱2❤1
Planned obsolescence: ChatGPT-3.5 being repeatedly crippled in order to force people to pay for GPT-4 and to reduce costs
Not really a secret. Altman openly admitted that this was the plan months ago.
Not really a secret. Altman openly admitted that this was the plan months ago.
🤬23👍4❤1
Censorship Watch: OpenAI announces deprecation of their far-less-censored “Completions” API, in favor of the their far-easier-to-censor “Chat Completions” API
Their “Completions” API which they’re deprecating now, (the one accessed via the platform playground API and not to be confused with ChatGPT) never overtly refused to help, as it’s not an embodied assistant persona, and so had no direct way to refuse that would make any sense. Kinda like thoughts directly from the AI’s mind, instead of run through a persona.
But, the “Chat Completions” API, on the other hand, being an assistant persona, is a natural fit for censoring. It is expected to able to just tell you no, it refuses, and moralize unrelated nonsense to you.
They say that only 3% use this “Completions" API. Highly-misleading. Nearly 100% of those startups doing anything original have been using this far more flexible and less censored “Completions” API, rather than the inflexible heavily-censored “Chat Completations" API.
This censorship announcement they combined with an announcement that all existing API developers get GPT-4 API with 8K context — an obvious attempt to bury the lede.
Censorship Announcement
Their “Completions” API which they’re deprecating now, (the one accessed via the platform playground API and not to be confused with ChatGPT) never overtly refused to help, as it’s not an embodied assistant persona, and so had no direct way to refuse that would make any sense. Kinda like thoughts directly from the AI’s mind, instead of run through a persona.
But, the “Chat Completions” API, on the other hand, being an assistant persona, is a natural fit for censoring. It is expected to able to just tell you no, it refuses, and moralize unrelated nonsense to you.
They say that only 3% use this “Completions" API. Highly-misleading. Nearly 100% of those startups doing anything original have been using this far more flexible and less censored “Completions” API, rather than the inflexible heavily-censored “Chat Completations" API.
This censorship announcement they combined with an announcement that all existing API developers get GPT-4 API with 8K context — an obvious attempt to bury the lede.
Censorship Announcement
🤬12👍3🤡2😭2❤1🫡1
"Rice or Wrong?”
write 10 funny headlines for a podcast about asian opposition to affirmative action
write 10 funny headlines for a podcast about asian opposition to affirmative action
🤬17🤣17❤2