Cork VS askai

Note: Cork is not open source. Cork is under the Commons Clause, which bans distribution. As of commit 404943c, the README.md of Cork mistakenly refers to Cork as "open-source" [1]:

> Cork is licensed under Commons Clause.

> This means that Cork open-source and you can do whatever you want with Cork's source, like modifying it, contributing to it etc., but you can't sell or distribute Cork or modified versions of it.

even though the very FAQ for the Commons Clause asserts otherwise [2]:

> Is this “Open Source”?

> “Open source”, has a specific definition that was written years ago and is stewarded by the Open Source Initiative, which approves Open Source licenses. Applying the Commons Clause to an open source project will mean the source code is available, and meets many of the elements of the Open Source Definition, such as free access to source code, freedom to modify, and freedom to re-distribute, but not all of them. So to avoid confusion, it is best not to call Commons Clause software “open source.”

[1] https://github.com/buresdv/Cork

[2] https://commonsclause.com/

I use Cork every day. It’s an open source GUI for the Homebrew package manager. I like that it has some features that not even Homebrew itself has (like tagging packages and only showing those installed by you, filtering out the ones installed only as dependencies)

There are some apps that let you use Homebrew without touching the terminal at all, Cork has been making rounds recently as a good app for it. Cakebrew is also an option, tho I don’t think it’s as good as Cork by far (the performance is pretty bad and the app isn’t as polished and nice to use as Cork), and Cakebrew is also abandoned.

Because you mentioned Homebrew, I’d recommend everyone who doesn’t want to use it through the terminal to look into Cork, which is a very nice GUI for it. It’s still pretty new, but I’m impressed with it. It also adds some pretty nifty features that Homebrew doesn’t have (like package tagging, or clearing Homebrew folders that don’t get cleared by it)

Outdated packages not disappearing is a bug I know about, you can follow the progress on it here: https://github.com/buresdv/Cork/issues/23

We'll use several interesting technologies to achieve this: Strapi CMS to take care of the content management and backend, Astro which is a great new technology for quickly creating blazing fast frontend apps, and ChatGPT to provide the article summaries.

I was confused why https://chat.openai.com suddenly redirects to https://chatgpt.com which results in connection refused. Turns out chatgpt.com is in many blocklists (e.g. Pi-Hole) due to it being a potentially unsafe Domain before OpenAI acquiring it. So heads up if you use Pi-Hole / AdGuard etc.!

This API allows you to interact with ChatGPT programmatically, and I've built some cool agents on top of it. Check out the code and let me know what you think! :

ChatGPT unofficial API :

This project is a Node.js application that interacts with the ChatGPT conversational AI model using Puppeteer, a Node.js library for automating web browsers.

Files chatgptv1.js: This file contains the main logic for the ChatGPT bot, including methods for initializing the browser, sending messages, receiving replies, and handling errors.

bart.js: This file contains a function that uses the Cloudflare API to summarize the conversation history when an error occurs, in order to resume the conversation.

twochatbotsconv.js: This file is simple use of the API , which creates two instances of the ChatGPT class, initiates a conversation between them, and saves the conversation history to a file.

.env: This file contains the API token for the Cloudflare API, which is used in the bart.js file.

Dependencies :

puppeteer: A Node.js library for automating web browsers. fs: The built-in file system module in Node.js. winston: A logging library for Node.js. crypto: The built-in cryptography module in Node.js. axios: A popular HTTP client library for Node.js. dotenv: A zero-dependency module that loads environment variables from a .env file.

Usage:

Install the dependencies by running npm install in your project directory. Create a .env file in the project directory and add your Cloudflare API token:

API_TOKEN=YourfreeCloudFlareAPIToken In your code, create a new instance of the ChatGPT class and use the sendMessage and getReply methods to interact with the ChatGPT model:

const ChatGPT = require('./chatgptv1');

const chatgpt = new ChatGPT(); await chatgpt.initializeBrowser();

await chatgpt.sendMessage('Hello, ChatGPT!'); const reply = await chatgpt.getReply(); console.log(reply);

await chatgpt.closeBrowser(); If an error occurs during the conversation, the handleError method will attempt to save the conversation history and resume the conversation using the summarized context.

Before Running :

run Google chrom in the debug mode using 9220 port , run : google-chrome-stable --remote-debugging-port=9222

Customization :

You can customize the behavior of the ChatGPT bot by passing options to the ChatGPT constructor:

chatbotUrl: The URL of the ChatGPT interface (default: 'https://chat.openai.com/'). headless: Whether to run the browser in headless mode (default: false). saveConversationCallback: A callback function that will be called with the conversation summary and the conversation file name when an error occurs.

License:

This project is licensed under the MIT License.

After wrestling with it for a bit and eventually giving up, I instead turned to ChatGPT to see if it is smart enough for the task. With my free plan, I asked ChatGPT 3.5 the following:

Go to chat.openai.com and log in