We haven't linked to the chatbot because it's at an adult domain name (but has no adult content), but you can find a link to it on the GPT4Free GitHub page. On Sunday, Xtekky made an announcement on the project's Discord channel (opens in new tab), saying that he's making some changes to his chatbot, which lives apart from the GitHub repo but serves as a working example of what you can do with it. "Deletion of my repo will be insignificant."
"Users are sharing and hosting this project everywhere," he said. Even if GPT4Free had never existed anyone can find ways to use these sites' APIs if they continue to be unsecured.
#REMOVE NETATALK 3 CODE#
"But the right way should be an actual official DMCA, through GitHub."Įven if the original repo is taken down, there's a great chance that the code - and this method of accessing GPT4 and GPT3.5 - will be published elsewhere by members of the community. "I believe they contacted me before to pressurize me into deleting the repo myself," he said. However, several hours after this story first published, we chatted again and he told me that he plans to keep the repo up and to tell OpenAI that, if they want it taken down, they should file a formal request with GitHub instead of with him. Xtekky initially told me that he hadn't decided whether to take the repo down or not. "I do not really know, but it looks like if a site use OpenAI's API, it has OpenAI's legal protection and OpenAI is liable for the damages the site gets." "OpenAI could also reach out to the sites and warn/notify them and in collaboration come to me and do a takedown, but it seems that this solely comes from OpenAI and they basically claim that I am directly attacking them," he said. The developer said that he doesn't believe he's liable for what others do with his script and that OpenAI should not be targeting him for using other sites' APIs, which are available unsecured on the open web. So, even if he takes the scripts down from his repo, any other developer could do the same thing. Xtekky said that he has advised all the sites that wrote to him that they should secure their APIs, but none of them has done so. One of many methods that sites like You.com could use is to block API traffic from any IPs that are not their own. Perhaps more importantly, Xtekky noted, any of these sites could block external uses of their internal APIs with common security measures. He said that he has already taken down scripts that use, ora.sh and. Xtekky said that he is more than happy to take down scripts that use individual sites' APIs upon request from the owners of those sites. If those sites are relying on ad revenue from their sites to offset these API costs, they are losing money because of these queries. So when you use the scripts, those sites end up footing the bill for your queries, without you ever visiting them.
"My repo just does it in a simpler way."Īll of the sites GPT4Free draws from are paying OpenAI fees in order to use its large language models. on my browser and spam requests," Xtekky said. "One could achieve the same just opening tabs of the sites.
Any enterprising developer could use these simple scripts to make their own bot. The GPT4Free repo also has scripts that grab data from other sites such as Quora, Forefront, and TheB. For example, the main GPT4Free script hits the URL, feeds it various parameters, and then takes the JSON it returns and formats it. On the backend, GPT4Free is visiting various API urls that sites like You.com, an AI-powered search engine that employs OpenAI's GPT3.5 model for its answers, use for their own queries.
0 kommentar(er)
