I found a binary file with a gibberish name in my home directory. Its content seems to be just hex zeroes when I open it in an online binary viewer. It doesn’t have execute permissions. It seems I accidentally ran spotify --uri= around the time the file was created (I could not replicate).
Can I safely ignore this as some bug with a program that tried to write to a file?
I do this every now and then by hamfisting a dd or curl command. The most irritating thing about it is the need to open a GUI in order to delete the file since I can’t reference the garbled filename from the CLI.
Yes, that was annoying. Especially because I didn’t have a GUI file manager installed.
I use the fish shell and it can usually autocomplete all manners of strange file names in a way it can understand
Make a directory with 256 files, each filename starting with a different byte, and see how it does.