Chatgpt.js: An open-source, powerful client-side JavaScript library for ChatGPT | Hacker News Reader

Chatgpt.js: An open-source, powerful client-side JavaScript library for ChatGPT

github.com

9 pointsadaaaam14 comments

Open articleView on HN

First issue I randomly clicked is a somewhat unhinged interaction with the author being threatening or abusive.

https://github.com/kudoai/chatgpt.js/issues/34

It looks like it needs treatment. I hope he's getting support.

What is the 'it' you refer to?

It's rather amusing to see people fighting over copyright on an AI tool.

I find it sad, especially over Javascript that use an API. I hope the author get some help with managing all of that anxiety.

I am one of the authors, there is no API used...

How come?

What a wild thread. Author claims to be in they mid 30s, then says they wrote JS since the 90s (back when they were what, less than 10 years old?) then uses LinkedIn connections with lawyers to make a point.

So weird. This reads like a thread between two bots trained with content from chats between 12 years old pretending to be adults.

Thank you for posting it though, it was an amusing read.

This was a fun read for sure. I wasn't expecting to find comedy in HN.

> What a wild thread. Author claims to be in they mid 30s, then says they wrote JS since the 90s (back when they were what, less than 10 years old?)

I am the author. You are correct I wrote JS since the 90s, however your math is incorrect as I was 12 in '96 (but less than 10 when using my first language, AppleSoft BASIC)

> uses LinkedIn connections with lawyers to make a point

And the point you are making is..?

Why would I use this instead of some minimal implementation of the official OpenAI packages?

Looking at the chatgpt.js file in the repo, a great deal of the code revolves around manipulating UI elements. What does any of this have to do with interacting with an API, and why would I use your UI, baked into this script, outside of something I control myself?

Then, the Usage section shows a few commands, completely unrelated to any UI elements.

I'm not sold on this; seems like a wrapper around something that is much simpler in practice.

> Who has time for docs?

Perhaps you could... I dunno, use an AI or something to generate those for you?

I'm an author so I can address some of your concerns

> Why would I use this instead of some minimal implementation of the official OpenAI packages?

If you're looking to use API, you wouldn't (this is client-side not server-side library)

> Looking at the chatgpt.js file in the repo, a great deal of the code revolves around manipulating UI elements.

Yes that's what this library is for

> What does any of this have to do with interacting with an API

Nothing... (who said it interacts with API?)

> why would I use your UI, baked into this script, outside of something I control myself?

The same reason authors of award-winning apps that use chatgpt.js do... to write less code (literally anyone uses libraries). Why do you need to control a library's code?

> I'm not sold on this; seems like a wrapper around something that is much simpler in practice.

It doesn't wrap anything it's original functions...

> "Who has time for docs?" Perhaps you could... I dunno, use an AI or something to generate [docs] for you?

A human wrote them already @ https://github.com/kudoai/chatgpt.js/blob/main/docs/userguid... the quote refers to users not me

OpenAI's developers knows of its existence already and follow many apps that use its code (for example, they copied the full-window functionality from the award-winning https://chatgptwidescreen.com powered by chatgpt.js)

Reply on news.ycombinator.com