taylor 
fun fact about vscode:
every time you make a change to a file it copies it to ~/Library/Application Support/Code/User/History or the appdata folder on Windows.
have fun with that information if you edit files with sensitive information in them
while having the history is definitely a handy feature, it's a privacy footgun and should really be off by default:
there seems to be no retention policy, on my old install, it has history dating from April 2022 (when the feature was introduced) to dec 2022 (when i wiped that machine)
it stores 50 entries per file
it stores the file path, modified time for each entry and the entire file contents at that time
it can be disabled with the workbench.localHistory.enabled preference
it is barely documented, only mentioned in this change log from when it was introduced https://code.visualstudio.com/updates/v1_66#_local-history
nionidh@tay hahahha haha haa it does what?! 
amelia@tay git done wrong
シナモン 
@tay ~/.config/Code/User/History on Linux. Ugh! 
zephyr 
@tay just linux + vim
@zeppy5d to quote tom scott: https://youtu.be/lIFE7h3m40U?t=291
The Art of the Bodge: How I Made The Emoji Keyboard
scarlett@tay oh.
oh, microsoft, never change.
oh, microsoft, never change.
Rye@tay is it just the most boneheaded implementation of an undo stack ever, or does it actually have a purpose?
@rye long term undo stack/proto-VCS
Cykonot@tay so nice to use Linux instead of spyware
Ofc, m$ still has enough training data to replace me. But, at least it's not my fault