I already find original ChatGPT (free version based on GPT-3.X) being "smarter" than Bing's one based on GPT-4. The latter much easier gives up just saying that it could not find anything, while ChatGPT replies based on its "knowledge" even on quite advanced science questions. Having a LLM trained on content generated by other LLM may be a way for disaster in future: filtering true from false (but convincing) information on scale would be hard to say the least. In light of recent troubles with Internet Archive, AI companies, like OpenAI, are of the beneficiaries of the Internet history "made on Earth by humans" :)
Well, this could be close to what I dreamed off when I did the GDPR takeout two years ago! Haven't used Spotify since, so the data should actually still actually be up to date. :)
Never used Spotify on a mobile device though, so the location scripts will likely not be interesting at all.
Oh hell yes! I downloaded my GDPR dump a few months ago with the intent of analyzing it like this but never got around to it. Gonna fire this up now.
On the topic of ChatGPT code projects, way I recently made another evening side project[1] using ChatGPT. I found a really nice pattern to use with it is to use one commit per ChatGPT iteration (including commits where it breaks the program, just don't push to main until it's good again). And in each commit, I store the full prompt or reply I said to ChatGPT as a prompt.txt[2]. I'll probably tack it onto the commit description next time for ease of reading. But other friends have found this really useful to be able to see exactly how I+ChatGPT evolved the software with each commit, and I can look back and reference useful prompting patterns I used.
punnerud|2 years ago
nuccy|2 years ago
mikae1|2 years ago
Never used Spotify on a mobile device though, so the location scripts will likely not be interesting at all.
dag11|2 years ago
On the topic of ChatGPT code projects, way I recently made another evening side project[1] using ChatGPT. I found a really nice pattern to use with it is to use one commit per ChatGPT iteration (including commits where it breaks the program, just don't push to main until it's good again). And in each commit, I store the full prompt or reply I said to ChatGPT as a prompt.txt[2]. I'll probably tack it onto the commit description next time for ease of reading. But other friends have found this really useful to be able to see exactly how I+ChatGPT evolved the software with each commit, and I can look back and reference useful prompting patterns I used.
[1] https://github.com/dag10/timelapse [2] https://github.com/dag10/timelapse/commits/e77d11baaaf4e2a5f...
rickdeveloper|2 years ago
amrb|2 years ago
hoffs|2 years ago
Also it's pretty apparent since Spotify suggests different playlists depending on time of day, weather, etc.
pdubouilh|2 years ago
cynicalsecurity|2 years ago
philshem|2 years ago
nemof|2 years ago
rvcdbn|2 years ago
grogenaut|2 years ago
seism|2 years ago
[deleted]
vrglvrglvrgl|2 years ago
[deleted]