Chat with your own PDF

[cerulean lance]

https://github.com/bhaskatripathi/pdfGPT

[fair relic]

I am looking through the code as I was thinking about making something like this. The code looks quite neat. SciSpace (typeset.io) does that but the code seems to be closed and I wanted to see how chatgpt +embedding would compare.

I am concerned about asking for the user's openAI key on huggingface via gradio. I imagine that that information gets sent to both gradio and huggingface . Neither seems safe for saving very sensitive information. That is, both could be vulnerable to attacks.

[still mesa]

Is this to be used with flask? How does one use this script? Definitely like though I wish the prompt instructions could be shortened.

[fair relic]

Why does the code use text davinci (gpt 3) instead of the chatgpt api that is cheaper and apparently better from openAI's claim ?

[deep grotto]

Following

[still mesa]

Send in a PR @fair relic

[wild pendant]

Do you know of an good packaged for use with Nodejs?

[ripe parrot]

Good work @cerulean lance

[cerulean lance]

The key is in environment variables. That is the standard secure way of using it. Why do you feel it is unsafe?

[cerulean lance]

Written using python and uses hubspace for hosting.

[cerulean lance]

I am upgrading the code to chatGPT API now. Got busy in other things for a while

[gusty stag]

Nice

[fair relic]

cool I ended up using some of your prompt to write a version that explores scientific articles in LaTeX code (I decided to use LaTeX rather than pdf as ChatGPT can read LaTeX). Thanks.

[fair relic]

I was referring to the gradio demo interface on huggingface where users presumably enter their API key in plain text on the huggingface website.

[cerulean lance]

oh yes...that's true. It has to pass through the hub. I will use SHA or something similar to take care of that. It would be interesting to see LateX based sol'n.

[wooden briar]

explain “The Cryptographic Doom Principle” in depth with an analogy: The Cryptographic Doom Principle is a cryptographic principle that states that any system that does not check the MAC (Message Authentication Code) before anything else is doomed. An analogy that can be used to explain this principle is a bank vault. When a customer wishes to access the bank vault, the customer must first authenticate themselves by entering a key or combination. If the customer does not enter the correct key or combination, the vault should not open. This is analogous to the Cryptographic Doom Principle, as authentication must come before any other action. [48] Similarly, if a system does not check the MAC before doing anything else, it is similar to someone entering an incorrect key or combination and still being able to access the bank vault. [115] This principle is important, as it ensures that messages are not tampered with during transmission. [56] Impressive as nowhere in the book is that analogy to be found, and it really clarifies things -- but why you need to give ur api both in the code and later in the browser tho