-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Obfuscating the /home/username path with system variable for user path #141
Comments
APPENDIX 1: Maybe only use relative path in output rather than full path? |
The output directory can virtually be everywhere!! |
This is going to be a nightmare to write because of the cross-platform (*nix, macOS, windows, ...) support but there has to be a way to do this. The reason, I had that path explicitly, is because I'm thinking a bit ahead of what is coming. For example: How to know which data are from a single file in the filesystem the day we will have to play with an API that virtually anybody can use to retrieve its own data. |
I really don't want to force everyone to use a special PyFunceble directory location in their filesystem. By the way: In a traceback, we can't change the full path (at least not without heavy computation). |
I know, that's why I was a bit un-precise in my suggestion, as this need to be thought throug before programming |
Closing because of #215. |
Is your feature request related to a problem? Please describe.
See title
Describe the solution you'd like
Obfuscating the
/home/SomeRealUserName
with default system variables as$HOME
in log outputsThis will help protect the real identity of a user, hence lift the level of privacy from a copy/paste interaction
The text was updated successfully, but these errors were encountered: