Have you used ChatGPT? Your conversation history is on the left rail
Have you used ChatGPT? Your conversation history is on the left rail
I can search the logs I keep without decompressing
Every user is different and each is free to use whatever software they want
No
Large number of upvotes on the quoted comment however. Maybe some of those voters are ChatGPT users
I do searching from the command line in text mode. The script I use keeps a "log" (a customised SERP) of all query strings and search result URLs. I also have these URLs stored in the logs from the forward proxy. These are compressed using RePair. I can search the compressed logs faster this way than with something like
ztsd -dc log.zst|grep pattern
or rg -z pattern log.zstGiven that, I'd suggest not offering "alternatives" to the features described in TFA for a service you've never used. There are people here talking about oranges, a lot of them with domain expertise, and you're not just talking about apples, you're talking about bird migrations.
Okay well it's a chat app where you chat directly with an LLM. The way LLMs work is you feed the entire chat history into it, and it generates the next message. Therefore, there's no way you can chat with it without storing the history. It's impossible
Sure, and also downvotes - that measures factionalism, not correctness.
But tech wise, you're confused. Functionally speaking chatgpt is a shared document editor - the server needs to store chat histories for the same reason Google Docs stores the content of documents. Users can submit text to chatgpt.com from one browser, and later edit that text from the app or a different browser. Ergo the text is stored on the server, simple as that.
3 versus 190+, so far
Many commenters cannot distinguish rhetorical questions from questions that seek an answer
By attempting to answer a rhetorical question one may only strengthen the point being made by the question, for example, poor decision-making, and may reveal an absence self-awareness
To do this, I first insert a blank line at the top of each log file before adding to the tarball
IME, RePair is faster than compressing with zstd and the size reduction is almost the same
The only "catch" is that RePair requires more memory during compression
Unfortunately, different searches for this RePair you mentioned have only revealed links to resources for repairing broken air compressors, damaged compressed files, spinal injuries, etc.
Instead of writing open letters they could of course do something about it. Even Google stopped storing your location timeline on their servers and now have it per-device only.