Use a third party interface which uses the API directly like YakGPT or the OpenAI playgrounds, and you can save some costs that way along with a local chat history that’s not shared with OpenAI.
Prior to releasing the chat history "feature" there was an opt-out form that could be submitted, which did not have any impact on the webapp's functionality. I'm not current enough to know if that form 1) ever had any effect, and 2) if a form-submitted opt-out is still valid given they now have the aforementioned in-app feature.
And you’re going to spend the time reviewing every single commit to make sure the dev didn’t sell out without telling anyone? Or risk running a potentially outdated and vulnerable extension?
The obvious point being that the “fork your own code and write your own kernel” attitude is simply unworkable for 99.999% of the population.
If we had to waste that much time re-inventing the loaf of bread, and then making sure that my neighbors didn’t decide to throw some raisins in my loaf, that we never get around to figuring out the next best thing: slicing it.
