Honestly, this is my first macOS app and I'm a bit out of ideas when it comes to performance. If anyone has tehcnical knowledge about SwiftUI and how I could improve performance, please do contact me ! ([email protected])
My experience has been that the SwiftUI Profiler shows that almost all processor time is spent deep inside SwiftUI/AppKit primitives, despite there being close to no updates to view properties.
I'm glad HN is enjoying the app despite those issues. I promise I'm doing my best !
> You agree that this license includes the right for us to make your Content available to other users of Service, who may also use your Content subject to these Terms.
I'm curious as to why this appears in your ToS, as this is quite a deterrent for many.
When I publish an update, I can push an email to those who downloaded the app. I'll probably end up adding some opt-in auto update feature in the app at some point
I've used the API extensively over the last few weeks, and I have yet to go above $1. It's still technically more than the free ChatGPT web interface, but doesn't suffer from load balancing constraints.
My experience has been that using it this way is fairly inexpensive. You can track your expenses in real time and put spending limits on OpenAI's dashboard, so you don't get a bad surprise at the end of the month.
Through the app, none. The app uses your OpenAI API key and your Gumroad license key to verify access to both of those services.
License management is handled via Gumroad, their privacy policy might enlighten you further. My impression is they only require an email and some billing info (Paypal or Credit card)
It most likely won't work on OS 10.13. I've looked at this issue earlier today and I'm relying on libraries that require macOS ≥ 13.0. I might look into it if there is demand for it though, but this will probably require leaving out some functionalities for older OSes.
As for audio integration, this in not on the to-do list, as I am looking to keep the client lightweight.
The UI sure needs a bit of work. I'll try to add more information about the different models.
As for the default temperature, 0.0 is actually a bug ! I'll definitely fix that in the next release. The default intended value is 1.0. The API reference [1] describes what the temperature parameter does in more detail.
While doing some testing, I also noticed that the app disables streamed responses by default. Make sure to check the appropriate checkbox in the settings to get token-per-token answers !
Yes. The new ChatGPT Plugins are not yet supported outside of the official web interface.
Other than that, most third party client actually allow more customization (custom system prompt, temperature adjustment, ...)
Depends on your usage, I guess. I personnaly couldn't justify it. In the last few weeks, I've used the API extensively and total cost comes to a few dollars max.
Admittedly, the API doesn't provide nearly as many features as ChatGPT Plus does. To each their own !
- ChatGPT Plus is crazy expensive, and the free tier is often down. I found it especially frustrating to not get access to my chat history when ChatGPT's load was high. Since alternative clients go through the API, their are exempt from load balancing.
- A native client is lightweight and doesn't rely on web technologies. This is a matter of personal taste, but I like the look and feel of native apps better than web pages.
- Current native clients are both very new and ill-fitted to my needs (I really like the LaTeX rendering feature and I want to be able to browse my chat history)
Nothing can feel slow to me anymore after dealing with emerge on gentoo, spending close to 20min solving dependency requirements. Surprisingly, compiling everything was the quick part, the frustration came from dependency resolution