askai VS obsidian-releases

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

The closest editor that follows our first principle is Obsidian editor:

The solution was already installed on both my computer and my phone: Obsidian.

> why does open source need to "win"

Open source does not need to win.

But your ability to be in control of your computer needs to be preserved. A proprietary fridge cannot control your diet, while a proprietary App Store can control what software you install on YOUR phone (unless you live in EU, hello DMA!). The tail wags the dog, so to speak. Proprietary software has also been shown to break user workflows or remove functions in an update while leaving users with no choice whatsoever.

One alternative to having open source win is to ensure software must come with a robust warranty and other assurances you expect from the things you buy. EU's CRA will make software vulnerabilities in WiFi routers covered by warranty, for example.

You can also ensure robust and interoperable data storage options. For example, https://obsidian.md/ stores all notes in Markdown, not holding the data hostage in case users will not like how future versions will work. GDPR actually has a provision for data portability (Art. 20), but it does not seem to have a requisite effect on the industry yet.

And until the above issues are solved, open source remains the best way to ensure that a software tail cannot wag your computer dog.

[2] https://obsidian.md/

So I've had my fair share of personal websites and blogs. I have built them on stacks ranging from the most basic HTML and CSS, to hosted frameworks like Wordpress and Laravel, to the more modern single page applications built in Vue and React. For a simple content blog I think you can't go wrong with a Static Site Generator though. These days I am almost exclusively writing everything in Obsidian. Which is great because its all in standard markdown format. This allows for a really neat and easy content publishing workflow.

Consider making an Obsidian[^1] plugin, or writing to Obsidian-compatible Markdown files :)

[^1]: https://obsidian.md/

Obsidian is a writing application created to allow for offline / private note taking in markdown format, in an interface that looks a lot like our regular programming IDE. It is very flexible, with a good collection of community plugins that you can use to customize Obsidian to your heart contents.

Obsidian support via our Obsidian Plugin