4 ms·

I think you might want to correct ChatGPT to just GPT. As far as I know, there is no public API access point for the ChatGPT. OpenAI davinci model that you're l

by rnosov 4y ago

I think you might want to correct ChatGPT to just GPT. As far as I know, there is no public API access point for the ChatGPT. OpenAI davinci model that you're likely using is based on InstructGPT ( a different GPT based beast ). Also, I would be somewhat worried about this thing racking up massive bills for the larger files. EDIT: okay, according to replies there is more than meets the eye

eterps 4y ago
> Also, I would be somewhat worried about this thing racking up massive bills for the larger files. Looks like the amount of data that is sent is capped: https://github.com/jjuliano/aifiles/blob/main/.aifiles.sample#L16 https://github.com/jjuliano/aifiles/blob/main/.aifiles.sampl...
- jjuliano 4y ago
  The more words you sent, the better understanding the AI about the file. HOWEVER, it also comes with privacy concerns. You can choose to rather sent a few words for AI to figure out your file. Also, take note, the maximum payload for OpenAI is 4kb, so the app will just throw an error when it exceeds 4kb.
simse 4y ago
Looks like it actually _is_ using ChatGPT: https://www.npmjs.com/package/chatgpt https://www.npmjs.com/package/chatgpt
- jclem 4y ago
  This package is using GPT-3 via the “ChatGPT” export from that module, which is—somewhat misleadingly—not ChatGPT, but GPT-3.
  - simse 4y ago
    Ahh you're right. I've been fooled.
  - survirtual 4y ago
    That package recommends using a ChatGPT proxy. This proxy has the ability to access ChatGPT in a way that OpenAI hasn’t been able to stop, but it requires a configuration file that is not open source. Everyone using this proxy needs to provide an OpenAI ChatGPT access token to the server. Let me break this down: Using the ChatGPT npm package enables an opaque third party access to your credentials to use ChatGPT — or exactly what a botnet / social media manipulation operation would need / want for a convincing bot. They just have to distribute load among all the active access tokens they’ve collected from users. DO NOT use this library. DO NOT trust code from authors who either don’t see this obvious vector or are in on it. To recommend using an opaque third party proxy with no encryption is not acceptable. This lets someone peep into your conversations with the bot on top of the other malicious uses with credential hijacking. And while OpenAI is peeping as well, they are at least using the data to advance AI and most researchers have a deep relationship with the ethics of their field. Here is the repo in question: https://github.com/transitive-bullshit/chatgpt-api https://github.com/transitive-bullshit/chatgpt-api
    - jjuliano 4y ago
      You are right. However, nothing is really secure. As Emails still operates on a store-and-forward model, where your message, jumps from server to server (akin to UUCP in the 60s). Even SMTP is not secure in itself without authentication layers. And also HTTPS is still sent as plain-text. Cert authority in itself doesn't have the keys to decode the text, it just an authority to show the plain-text, but all along, it was a plain-text.
      - survirtual 4y ago
        HTTPS is not plain text. Only the initial DNS resolution is (www.google.com). Everything after that is encrypted — address, payload, etc. The cert authority simply signs a cert saying “this public key belongs and is controlled by the owner of this domain name”. Since we both trust the cert authority, that signature allows us to prevent mitm attacks. From there, we can do a Diffie-Hellman key exchange and derive our secret key for encryption / decryption. That is secure and is the backbone of the internet today. It allows all of us to send messages to an intended recipient without worrying about other parties prying into our business. A proxy introduces an unnecessary and unvetted third party into an exchange. There is significant financial and political motivation for hijacking sessions for higher access to the chatbot & future versions of it. It is not a good pattern to make a habit of.
  - jjuliano 4y ago
    While there is currently a waiting lists to use the official ChatGPT API, the package uses an unofficial ChatGPT API. Surprisingly, the unofficial libraries are much more stabler (not much dropping of requests or timeout issues) than the official libraries from OpenAI.
charcircuit 4y ago
>there is no public API access point for the ChatGPT There is an undocumented model name that you can use to access it via the API.
jjuliano 4y ago
Author here: It currently uses ChatGPT. While ChatGPT is currently free, the use of REPLICATE API for describing images will have an incurred costs. At the moment, if you opt-out of this feature, you can skip Images for now. However, future updates will have a configuration to be able to skip REPLICATE, or choose to use a paid OpenAI model.

by rnosov 4y ago

eterps 4y ago

> Also, I would be somewhat worried about this thing racking up massive bills for the larger files. Looks like the amount of data that is sent is capped: https://github.com/jjuliano/aifiles/blob/main/.aifiles.sample#L16 https://github.com/jjuliano/aifiles/blob/main/.aifiles.sampl...

jjuliano 4y ago
The more words you sent, the better understanding the AI about the file. HOWEVER, it also comes with privacy concerns. You can choose to rather sent a few words for AI to figure out your file. Also, take note, the maximum payload for OpenAI is 4kb, so the app will just throw an error when it exceeds 4kb.

simse 4y ago

Looks like it actually _is_ using ChatGPT: https://www.npmjs.com/package/chatgpt https://www.npmjs.com/package/chatgpt

jclem 4y ago
This package is using GPT-3 via the “ChatGPT” export from that module, which is—somewhat misleadingly—not ChatGPT, but GPT-3.
- simse 4y ago
  Ahh you're right. I've been fooled.
- survirtual 4y ago
  That package recommends using a ChatGPT proxy. This proxy has the ability to access ChatGPT in a way that OpenAI hasn’t been able to stop, but it requires a configuration file that is not open source. Everyone using this proxy needs to provide an OpenAI ChatGPT access token to the server. Let me break this down: Using the ChatGPT npm package enables an opaque third party access to your credentials to use ChatGPT — or exactly what a botnet / social media manipulation operation would need / want for a convincing bot. They just have to distribute load among all the active access tokens they’ve collected from users. DO NOT use this library. DO NOT trust code from authors who either don’t see this obvious vector or are in on it. To recommend using an opaque third party proxy with no encryption is not acceptable. This lets someone peep into your conversations with the bot on top of the other malicious uses with credential hijacking. And while OpenAI is peeping as well, they are at least using the data to advance AI and most researchers have a deep relationship with the ethics of their field. Here is the repo in question: https://github.com/transitive-bullshit/chatgpt-api https://github.com/transitive-bullshit/chatgpt-api
  - jjuliano 4y ago
    You are right. However, nothing is really secure. As Emails still operates on a store-and-forward model, where your message, jumps from server to server (akin to UUCP in the 60s). Even SMTP is not secure in itself without authentication layers. And also HTTPS is still sent as plain-text. Cert authority in itself doesn't have the keys to decode the text, it just an authority to show the plain-text, but all along, it was a plain-text.
    - survirtual 4y ago
      HTTPS is not plain text. Only the initial DNS resolution is (www.google.com). Everything after that is encrypted — address, payload, etc. The cert authority simply signs a cert saying “this public key belongs and is controlled by the owner of this domain name”. Since we both trust the cert authority, that signature allows us to prevent mitm attacks. From there, we can do a Diffie-Hellman key exchange and derive our secret key for encryption / decryption. That is secure and is the backbone of the internet today. It allows all of us to send messages to an intended recipient without worrying about other parties prying into our business. A proxy introduces an unnecessary and unvetted third party into an exchange. There is significant financial and political motivation for hijacking sessions for higher access to the chatbot & future versions of it. It is not a good pattern to make a habit of.
- jjuliano 4y ago
  While there is currently a waiting lists to use the official ChatGPT API, the package uses an unofficial ChatGPT API. Surprisingly, the unofficial libraries are much more stabler (not much dropping of requests or timeout issues) than the official libraries from OpenAI.

charcircuit 4y ago

>there is no public API access point for the ChatGPT There is an undocumented model name that you can use to access it via the API.

jjuliano 4y ago

Author here: It currently uses ChatGPT. While ChatGPT is currently free, the use of REPLICATE API for describing images will have an incurred costs. At the moment, if you opt-out of this feature, you can skip Images for now. However, future updates will have a configuration to be able to skip REPLICATE, or choose to use a paid OpenAI model.