Assuming most sites do not use comprehensive browser fingerprinting, it's not any different from having a dynamic ip and wiping cookies periodically. In both c

Assuming most sites do not use comprehensive browser fingerprinting, it's not any different from having a dynamic ip and wiping cookies periodically. In both cases, assigning this data to a unique identifier that can be later tied to your name is pretty hard. If your ultimate goal is avoiding this I'd actually advise against self hosting one of these solutions if you are planning it using alone. Either get more people to use your instance, making your usage "fingerprint" harder to correlate or use a service hosted by someone else for the same reason. The latter of course hinges on trusting the webmaster of that service.