Commit Graph

1336 Commits (cadc507fad2fee59b23d1d8e73c472c077f468fc)
 

Author SHA1 Message Date
Heiner Lohaus 3ae90b57ed Improve get_cookies helper 10 months ago
abc d185488b2b ~ 10 months ago
abc ff88afa1da ~ | g4f `v-0.1.7.4` 10 months ago
Tekky d1eaa46360
Merge pull request #1118 from hlohaus/fake
Add FakeGpt Provider
10 months ago
Luneye a8841088a9
Update requirements.txt for Bing update 10 months ago
Heiner Lohaus fc15181110 Fix ChatgptAi Provider 10 months ago
Luneye c400d02024
Major Update for Bing - Supports latest bundle version and image analysis
Here it is, a much-needed update to this service which offers numerous functionalities that the old code was unable to deliver to us.

As you may know, ChatGPT Plus subscribers now have the opportunity to request image analysis directly from GPT within the chat bar. Bing has also integrated this feature into its chatbot. With this new code, you can now provide an image using a data URI, with all the following supported extensions: jpg, jpeg, png, and gif!

**What is a data URI and how can I provide an image to Bing?**

Just to clarify, a data URI is a method for encoding data directly into a URI (Uniform Resource Identifier). It is typically used for embedding small data objects like images, text, or other resources within web pages or documents. Data URIs are widely used in web applications.

To provide an image from your desktop and retrieve it as a data URI, you can use this code: [GitHub link](https://gist.github.com/jsocol/1089733).

Now, here is a code snippet you can use to provide images to Bing:

```python
import g4f

provider = g4f.Provider.Bing
user_message = [{"role": "user", "content": "Hi, describe this image."}]

response = g4f.ChatCompletion.create(
    model = g4f.models.gpt_4,
    provider = g4f.provider,  # Corrected the provider value
    messages = user_message,
    stream = True,
    image = "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEASABIAAD/4RiSRXhpZgAASUkqAAg..."  # Insert your full data URI image here
)

for message in response:
    print(message, flush=True, end='')
```

If you don't want to analyze the image, just do not specify the image parameter.

Regarding the implementation, the image is preprocessed within the Bing.py code, which can be resource-intensive for a server-side implementation. When using the Bing chatbot in your web browser, the image is preprocessed on your computer before being sent to the server. This preprocessing includes tasks like image rotation and compression. Although this implementation works, it would be more efficient to delegate image preprocessing to the client as it happens in reality. I will try to provide a JavaScript code for that at a later time.

As you saw, I did mention in the title that it is in Beta. The way the code is written, Bing can sometimes mess up its answers. Indeed, Bing does not really stream its responses as the other providers do. Bing sends its answers like this on each iteration:

"Hi,"
"Hi, this,"
"Hi, this is,"
"Hi, this is Bing."

Instead of sending each segment one at a time, it already adds them on each iteration. So, to simulate a normal streaming response, other contributors made the code wait for the next iteration to retrieve the newer segments and yield them. However, this method ignores something that Bing does.

Bing processes its responses in a markdown detector, which searches for links while the AI answers. If it finds a link, it saves it and waits until the AI finishes its answer to put all the found links at the very end of the answer. So if the AI is writing a link, but then on the next iteration, it finishes writing this link, it will then be deleted from the answer and appear later at the very end. Example:

"Here is your link reference ["
"Here is your link reference [^"
"Here is your link reference [^1"
"Here is your link reference [^1^"

And then the response would get stuck there because the markdown detector would have deleted this link reference in the next response and waited until the AI is finished to put it at the very end.

For this reason, I am working on an update to anticipate the markdown detector.
So please, if you guys notice any bugs with this new implementation, I would greatly appreciate it if you could report them on the issue tab of this repo. Thanks in advance, and I hope that all these explanations were clear to you!
10 months ago
Heiner Lohaus 78f93bb737 Add rate limit error messages 10 months ago
Heiner Lohaus 13b496afd5 Improve readme 10 months ago
Heiner Lohaus 63cda8d779 Fix increase timeout
Add Hashnode Provider
Fix Yqcloud Provider
10 months ago
razrab ecad7a4ac8 Added code to ignore certain providers in the API 10 months ago
Heiner Lohaus 4225a39a49 Enable Liaobots and ChatForAi again 10 months ago
Heiner Lohaus 13e89d6ab9 Fix MyShell Provider 10 months ago
Heiner Lohaus a3af9fac3e Add FakeGpt Provider
Update providers in models
10 months ago
Tekky f125f714fb
~ | Merge pull request #1112 from lategege/main
fix bug - Cannot assign requested address
10 months ago
late 0e93d841ba fix bug - Cannot assign requested address 10 months ago
abc 2ac711ed89 ~ | g4f `v-0.1.7.2`
fix tiktok not found error
10 months ago
abc ae8dae82cf ~ | g4f `v-0.1.7.2`
patch / unpatch providers
10 months ago
abc 29e2302fb2 ~ | g4f v-0.1.7.0
quick fix
10 months ago
abc d01c2afe47 ~ | 0.1.7.0 10 months ago
abc 603b5b85a4 ~ | g4f v-0.1.6.9 10 months ago
abc dad69d24ce ~
minor changes
10 months ago
abc 0ddfe57431 ~ | quick fix 10 months ago
abc 2a52d844f3 ~ 10 months ago
abc 8e7e694d81 ~ | updated g4f.api
new api and requirements
10 months ago
abc 04edb66065 ~
fix gui errors on iOS
10 months ago
Tekky 7637ab34ed
~ 10 months ago
abc 5b52d5a2ee ~ | g4f `v-0.1.6.8`
some quick fixes
10 months ago
abc 32c55a2fc2 ~ | g4f v-0.1.6.7 10 months ago
abc d4ab83a45b ~
automatic models fetching in GUI.
10 months ago
abc 76083c5a17 ~ 10 months ago
Tekky 7c410b7d21
~ | Merge pull request #1101 from suravkshrestha/patch1
docs: fix typo in README.md
10 months ago
Surav Shrestha ecc0d2aa90 docs: fix typo in README.md 10 months ago
Tekky 4c72acca7b
~ | Merge pull request #1098 from Lin-jun-xiang/show_retryProvider
Fix: debug.logging not work in retry provider
10 months ago
hs_junxiang 042ee7633b Fix: debug.logging not work in retry provider 10 months ago
Tekky cb3677a3e2
~ 10 months ago
Tekky 591e60e748
~ | Merge pull request #1092 from ostix360/main
Add timeout
10 months ago
ostix360 24f7495f24 Add timeout 10 months ago
abc 2e68a4b1d4 ~ 10 months ago
abc 55f772c0bc ~ 10 months ago
abc 9776545ab0 ~ | g4f `v-0.1.6.6` 10 months ago
abc 6c424ce5fe ~ 10 months ago
abc c1fbb13edc ~ | update working providers list & gpt-4 providers 10 months ago
abc 5b240665fb ~ | add `g4f.Provider.GeekGpt` 10 months ago
abc 8bce9ace2d ~ | new providers test 10 months ago
abc d9b1fa6429 ~ 10 months ago
abc d93b0fe7eb ~ | g4f `v-0.1.6.5` 10 months ago
abc 4a3b663ccd ~ | remove non-working providers 10 months ago
abc 46398e8ac6 ~ | new `test_providers.py` 10 months ago
Tekky 1168d66115
~ | Merge pull request #1081 from hlohaus/son
Add Llama2 and NoowAi Provider
10 months ago