A way to check whether account IPs match (NOT VIEW IPs)
-
Although you said that is isn't viewing IP's, it still sounds like a sketchy suggestions. Plus most of the time, people use VPNs for their alts, so it wouldn't really work.
-4 -
This would be totally flawed by a situation such as public places / university dorms. Generally they all have a small amount of public IP addresses and everyone inside is behind those few address meaning that you could easily end up ID-ing someone as an alt of someone else when in reality, they are not.
4 -
why do you want to see the alts
-3 -
For security reasons, this should never happen. 0 -
There is always the AltDentifier bot for reasons like this. By letting owners see IP it jeopardizes the security of individual users.
0 -
This is actually a good suggestion. If it doesn't show up IP it isn't sketchy. It could simply show something that says "this user also has these accounts and list off the other user IDs attached to the device/IP" it would help fight alts
-2 -
Literally the only bad thing about discord is this
0 -
Even with my highly featured Moderation bot with global ban list. I still can't keep raiders out
1 -
This is a standard Admin feature with TeamSpeak. It's been available to admins for YEARS. All it does, it tells you if an IP has been shared, then what Accounts on YOUR server have used it.
If someone is at school with limited IP's....it doesn't matter. It simply tells you who has shared IP's...and means nothing. However, if you have a user that is being disruptive and you know they live nowhere near the person they are trying to hijack their identity, you as an admin will know.1 -
Capt_Bon could you elaborate?
1 -
Yes, I'd like to know more about that.
0 -
Yes me too.
But I also want to know how to create a system where you can know who joined using whose invite (if this exists. If not, then it's a suggestion).This might also prevent alts.
0 -
Agree
0 -
Apologies to Mystique for not catching the request.
The clan I run has around 150 members. A few years ago, we used Teamspeak and we had a member under the guise of "desktop support", use Teamviewer. This member then learned the Teamspeak login of that member, and use his credentials to impersonate that member...basically lurking and pretending to be AFK to listen.
As admin of Teamspeak, I could look at the offending member activity and see his IP was used to log in as HIS account and the LURKING ACCOUNT. Teamspeak said this IP has been used to log in as 2 accounts.
If Discord had this same information, as admin I would be able to know Account A, B and C with 3 different user names are all the same person. I wouldn't actually know their IP (Discord or Teamspeak would be the "escrow holder" of the IP address), I would only know which users are using the same IP..thus either the same person or Person A has compromised Person B's account.0 -
I had the same issue. A user was breaking rules one after the another and no one liked him which is why he was banned. But then he made another account and started trolling people as if he was someone else. Thank god I figured it out that it was him after others told me that he messaged them.
Having alt accounts to talk with while banned or muted is illegal and there should be a way to prevent it. I know this sounds kind of impossible, but some steps can be taken. There should be an option to see users that don't have their accounts verified. Not sure if this can be done with bots, but there should be some sort of verification required when making a discord account, i.e. adding an email id or a phone number should be necessary to make an account.
People know that they can just make an alt anytime so they aren't afraid of mutes/bans.
0 -
Guys i would like to mention, Users that share the Same IP doesnt have to be Alts, it could be a public IP (for example a restuarent wifi) or people that live together and have one wifi in their house which they use. so this way is not Accurate enough to find Alts.
2 -
Ok...that's potentially possible. Likely that a clan of 40 gamers will have members that share an IP is..well....super remote.
0 -
You realize that NAT is a common thing in networking and therefore users will inevitably share IP's in apartments and other residential places or businesses that don't have a dedicated IP address on a per-user basis. It's pretty common practice, and using a method like this would throw false positives often. I think a solution your looking for would be MAC address logging, seeming as MAC addresses are really only relevant to local connections, and don't pose as much of a privacy issue. Another thing is MAC addresses are hard baked into the hardware, and although can be spoofed, don't change like IP addresses do.
0 -
So, on point (arbitrarily numbered) one that Capt_Bon mentioned: TeamSpeak servers function differently from discord on the backend. Yes, from the user side, its much the same (by design, I imagine); text and voice chat rooms in categories with permissions etc. However, on the backend, discord describes the entirety of the hosting service as a whole, whereas TeamSpeak represents a single server instance that must be hosted. Granted there may be TeamSpeak service providers which make spooling a new server as simple as discord does. You must keep in mind that while TeamSpeak exists as independent instances on the server hardware (like running multiple apache web servers with their own unique URLs and content), discord on the other hand operates more like, say facebook or deviantart where you can create groups that users can join with permissions to view certain content and such, but it is all running under discords services umbrella. Their central database keeps track of the organized chaos that is managing all those different ID associations. User IDs with server IDs, user IDs with other user IDs for DMs and then searches their associated server IDs for ones that match to show you mutual servers (the same for friends lists which in the database is just a list of user IDs, if any match it adds them to the mutual friends tag to be displayed in the client app). So when you say "YOUR server" in discord you are simply referring to a server where a certain list of actions are allowed to be requested by specific user IDs, but in TeamSpeak, as it literally is an individualized program running a unique config file on the server hardware (like running the same program twice just set up differently), it literally is YOUR server. As opposed a services portal you have access too. Its the difference between renting space on a server, being given login credentials from which you must install and configure your own website server programs, and simply clicking "yes I would like a webpage please" and being given a blank canvas to add html to with all the actual complicate stuff in the background already taken care of. TeamSpeak is the former (where one has access to the access logs containing IPs of requests because it is literally your program running on your resources), and discord is the later (where one has access to whatever the service hosting entity allows you to have because you are interacting with a platform that provides these services, but the resources remain theirs). This is not unfair, nor is it shady. This is simply how the internet works, and has done for a very long time. Ask your older siblings about geocities, or angelfire some time…
Anyhoozle, this is why on TeamSpeak you can view which IPs are connected to your server instance, and why on discord you cannot. They are entirely different topologies and methods of operation.
And point two brought up by uqyahsgeog: the only way to detect the MAC address of the device end point is for the program to request it from the network driver, package it up,and send it to the central database. I honestly have no idea if discord does this, they probably do, as do many programs which take liberties with access to users internal networks. Fortunately most of us are too ignorant of how the internet works on the mechanical level and thus sufficient profit threatening stink is not raised over it, while another tiny bit of our privacy is eroded away (dont believe me? Look into wifi localization coming in the next generation of routers. It wont matter if you dont have one, as long as your neighbors do the synthetic aperture radar data containing your living space will be shipped off to AI in the ‘cloud’ (which just means a computer you do not own nor control) anyways. Because what is privacy?).
Anyhoozle again, the MAC address of the sending device is only pertinent to the routers in-between. Once a packet passes through a routing device the MAC is swapped out for the routers MAC and forwarded on. The routing devices keeps a table in memory of who requested what so that as data comes back it can find its way back to the original device. The device MAC shouldnt ever leave the local area network. Besides, MACs are easily spoofed. Oh, and services such as discord tend to focus on user agent fingerprinting and the associated UUID generated from it.
0
Log ind for at efterlade en kommentar.
Kommentarer
19 kommentarer