Phil Lilley Posted November 2, 2021 Posted November 2, 2021 (edited) When temporarily banning a member for 7 days, I mistakenly banned his IP. When his time was up, I found out what I had done because the member as well as other members with overlapping IP's were turning up banned still. The member I banned had just over 1,000 IP's (40 pages @ 25 each page). He's been a member for 17 years. I had to delete them all one at a time. That's on me... my mistake. It would be nice if there were an option to mass delete. Just a thought... Thanks Edited November 3, 2021 by Phil Lilley
Management Charles Posted November 3, 2021 Management Posted November 3, 2021 We have considered deprecating IP-based banning because, in 2022, it is really not very useful. Unienc 1
OctoDev Posted November 3, 2021 Posted November 3, 2021 1 minute ago, Charles said: We have considered deprecating IP-based banning because, in 2022, it is really not very useful. Perhaps add improvements to the banning system, such as storing hidden cookies, or generate an unique device that is accurate? I.e fingerprintjs support. ZLTRGO 1
Randy Calvert Posted November 3, 2021 Posted November 3, 2021 Cookies are used as part of banning. However they MUST be associated to the domain to be accessed so you can’t truly “hide” them. Just popping cache would remove them. Banning the username is typically much more effective than banning an IP, especially in the days of iCloud Private Relay, VPNs, mobile networks etc. In this case it does sound like an evasive member but instead a situation where existing tools would have been more simple to use and work effectively.
Recommended Posts