You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why:
Prevent alt accounts much better without exposing the IP of the user.
Feature:
An extension of #88 or a separate thing but to allow /api/users/compare/ip?user1=1231231&user2=87778877 to return a boolean of true or false.
Basically, a way for a trusted/verified bot to check if a user in a server/guild has the same IP as another user in the server. Either both users must be in the server or 1 user must be in the server. An example of why you want a 1 person requirement and not a 2 person requirement is checking if a global ban user matches anyone in the server such as enforcing ip bans.
Additionally having the ability to compare a user against an ip/hash would prove beneficial. Again this can be requested(see #88) but you have Alex's little Minecraft server. Little Johny starts to grief, Minecraft allows server owners to view the ips of their players, Alex can now use Johny's IP to run an automated scan through his server members(without exposing their current and past ips) to check which users could be alts of him.
Again there would be no way of finding out someone's ip by comparison unless you physically visit and use every network in someone's country. Which if you managed to do that and you had beef with that person. Then there is no point to have an IP.
The checking against a given ip can prove beneficial for other types of member verification. You could run an automated check on someone's ip to see if they are using a VPN and to kick them for it. Or optionally allow an option to check against known VPN ip addresses.
The text was updated successfully, but these errors were encountered:
Why:
Prevent alt accounts much better without exposing the IP of the user.
Feature:
An extension of #88 or a separate thing but to allow
/api/users/compare/ip?user1=1231231&user2=87778877
to return a boolean of true or false.Basically, a way for a trusted/verified bot to check if a user in a server/guild has the same IP as another user in the server. Either both users must be in the server or 1 user must be in the server. An example of why you want a 1 person requirement and not a 2 person requirement is checking if a global ban user matches anyone in the server such as enforcing ip bans.
Additionally having the ability to compare a user against an ip/hash would prove beneficial. Again this can be requested(see #88) but you have Alex's little Minecraft server. Little Johny starts to grief, Minecraft allows server owners to view the ips of their players, Alex can now use Johny's IP to run an automated scan through his server members(without exposing their current and past ips) to check which users could be alts of him.
Again there would be no way of finding out someone's ip by comparison unless you physically visit and use every network in someone's country. Which if you managed to do that and you had beef with that person. Then there is no point to have an IP.
The checking against a given ip can prove beneficial for other types of member verification. You could run an automated check on someone's ip to see if they are using a VPN and to kick them for it. Or optionally allow an option to check against known VPN ip addresses.
The text was updated successfully, but these errors were encountered: