-
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
Subspace should be a hash value #82
Comments
I'm personally in favor of this change. This would just require one small additional check inside the
This can be easily done using the following RegEX:
|
This makes sense, also because with only strings we can have users writing "deSmOs", "desm0s" and so on..We will provide a better order using hash so I totally agree with implementing this. |
I have one comment in the PR #84 (comment) |
subspace
inPost
is better in hash value so that it can be verified by the users by comparing the hash value instead of relying on comparing with a string.Consider an imposter is trying to build an app and put
subspace
asC0SMOS
to pretend to be an app discussing things onCOSMOS
.But I don't have an idea of how the UX can be done to let normal endusers to verify this yet. @RiccardoM @bragaz please comment.
The text was updated successfully, but these errors were encountered: