It's mentioned in the second demo video that they have a strict process to prevent cases like yours. I think Descript started asking for identity verification after its service was abused. This one probably has a similar process too.
If you're using a third-party UI for ChatGPT, it might as well be a browser extension [0] or a native app [1]. It really shines when you break it out of its website interface and start using it like a command palette/context menu.
I'm beginning to think there's one too many of these kinds of apps, but if anyone is interested in a cross-platform (Mac, Linux, Windows) alternative, I've built a command-palette type interface [1] to GPT that supports code blocks/LaTeX too.
Agreed! I've found that staying in my workflow leads to fewer inadvertent context switches (like ChatGPT in-browser -> HN -> ... -> rabbit hole). MacGPT looks great. I created a similar plugin for my Windows keystroke launcher (think Alfred/Spotlight) for the same reason. If anyone's interested, you can check it out here: https://github.com/dkgv/pinpoint
It's a userfriendly web client for the latest OpenAI chatCompletion API with additional features compared to the official chat.openai.com client (mainly: "Share chats" & better param customization), it's Open Source and can be run locally or self-hosted easily. It's built in one of the most popular frontend tech stacks of the last years. Not more and not less than that.
> It is possible to use these unreleased plugins by setting up match-and-replace rules through an HTTP proxy. There are only client-side checks to validate that you have permission to use the plugins and they can be bypassed.
I wonder if this is intentional. A lot of browser extensions including mine [0] take advantage of their "loose" endpoints to enhance the functionality of ChatGPT. I feel that this has definitely helped them.
