I was very confused by the behavior of the images browser because I expected the action of adding to favorites to be similar to the "save" button on the txt2img page, where the image is copied to the log/images folder rather than moved. I prefer this because I'm inconsistent about flagging good images, so I am often looking through the original generation folder to find good images, and they are missing if I moved them to the favorites folder. Also, this causes errors in the image browser because the thumbnail for the moved image stays visible in the image browser, but throws an error if you click on it again because it is no longer present in the expected location. Some people may prefer the current behavior (moving rather than copying) to save space, but I would greatly prefer the option to just copy rather than move.
I was very confused by the behavior of the images browser because I expected the action of adding to favorites to be similar to the "save" button on the txt2img page, where the image is copied to the log/images folder rather than moved. I prefer this because I'm inconsistent about flagging good images, so I am often looking through the original generation folder to find good images, and they are missing if I moved them to the favorites folder. Also, this causes errors in the image browser because the thumbnail for the moved image stays visible in the image browser, but throws an error if you click on it again because it is no longer present in the expected location. Some people may prefer the current behavior (moving rather than copying) to save space, but I would greatly prefer the option to just copy rather than move.