> There is always a victim even if it is yourself.
That's simply nonsense, and incredibly authoritarian.
In any free society the state simply shouldn't be probing into the private lives and bodies of citizens. If an adult makes the informed decision to do something to their own body, they are not a victim. Thinking otherwise strips people of their agency.
Although I agree with what you're saying, the philosophy isn't so clear cut; even some strands of libertarian thought recognize harms against oneself, but the "oneself" is in the future, and could be considered a separate person. By an extension of the harm principle, it could be permissible to illegalize things which cause harm against people in future - the sale of cigarettes, for example.
By your logic the government should be banning sugar, forcing people to exercise, and on and on. Using the welfare state as an excuse for the government to control the private lives of citizens is pernicious to individual liberty at best, and totalitarian at worst. A safety nets don't exist to allow for the state to be an ever watchful and scolding parent, but rather to provide a floor so that people don't fall in to miserable situations.
Furthermore, the idea that one's actions in private, concerning only their own body, should make them a social outcast is laughably puritanical. Inclusion in society is about how one engages in the public sphere.
If the victim is yourself, either you were coerced (and the coercion should be the crime) or you consented (and it shouldn't be a crime). If I kick myself in the shin, is that battery, now?
Reminds me of something similar that happened to me once a long time ago.
I hacked into a server. I wanted to take a copy of everything so I made a tar of / to wget it to computer later. Only that the disk was at >50% usage so I filled it by making the tar file. Everything stopped to work with 0 bytes left of disk space (I wasn't root) so I kinda bricked the machine. I had to walk away in shame.
No, you'd have walked away in shame if you had walked away in handcuffs. Don't do stupid stuff. Imnsho you got lucky that disk filled up before you could notch up a(nother?) crime.
What happened is arguably more stupid: by filling up the disk, 1) they definitely noticed, 2) I couldn't get what I wanted, and 3) I couldn't clean up the logs after it. Thankfully I had covered up my steps (or, more probably, the sysadmin was ashamed to see he had been hacked and chose to fix it and say nothing).
When I was learning Microsoft Access, many years ago, I didn't really understand joins. So I did a cross join with no where condition. And the machine (Windows XP) just sat there, and eventually locked up.
