# Dupe ban accts with same IP not being auto caught anymore

**URL:** https://meta.discourse.org/t/dupe-ban-accts-with-same-ip-not-being-auto-caught-anymore/94510
**Category:** Support
**Created:** [August 12, 2018, 7:05am UTC](https://meta.discourse.org/t/dupe-ban-accts-with-same-ip-not-being-auto-caught-anymore/94510 "2018-08-12T07:05:41Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![Ubik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ubik/32/89095_2.png) [@Ubik](https://meta.discourse.org/u/Ubik)
#### Post date: [August 14, 2018, 7:33am UTC](https://meta.discourse.org/t/dupe-ban-accts-with-same-ip-not-being-auto-caught-anymore/94510/7 "2018-08-14T07:33:57Z")

</div>

> [@codinghorror](#):
>
> Note that there are zero other topics complaining about this – that suspended users must be automatically IP banned as well – in the last 5 years, that I can recall. So you might want to reconsider whether what you view as so “urgent” … is in fact an urgent issue 😉

Moderator on a Discourse forum since Spring 2017 here: I also longed for a single-click function on the user’s admin page to block their IPs (Last & Registration) for that member _every single time I had to ban someone_, but I kind of assumed no-one else minded having to go to burger \> Admin \> Logs \> Screened IPs, paste it in, get [that OK dialogue](https://meta.discourse.org/t/blacklisting-ip-has-no-feedback/94513), have to click reload if the person displays 2 IPs…

It seemed too whiny and lazy and time-consuming to me to bother logging in here, and posting about it, basically requesting people put in hours of work to save me seconds of copy-paste, on at most a few occasions a month; also, I felt I should run searches and see if it had already been addressed and nixed, so never bothered. 🙂

Urgent? Maybe not, though again it depends on how many of your staff are volunteer moderators, enthusiasts on the forum’s topic who are fitting in forum checks between work, family, other commitments, and how they may experience the added workload of the extra steps needed each time.

Especially because when you copy the IP straight off the member’s admin page it carries a space at the start (which copies elsewhere as a linebreak, not sure what that’s called), and that has to be manually deleted from the field before the IP can be blocked.

In the busyness of handling things after someone has had to be banned, maybe sending PMs and also trying to log everything relevant, it’s the most annoying thing in the universe in the 3 seconds it takes to be told

 ![dementor](https://global.discourse-cdn.com/meta/original/3X/8/b/8bf46d79d85a4192316216572c5661113fefed34.jpeg)

… but then, I backspace it and do the block, and forget about it until next time. 🙂

But it’s all worth it, because IP blocks are still an amazingly useful tool even now, and even with quite serious trolls.

While I have the list open, other things that would be nice on the same theme:

- single click to copy their IP and information on Location and Organization to my clipboard, so when I add this to Staff (where I am logging who was banned and why) I can paste it in one step. These have had proven value identifying grudge-bearing people who try to return.

- option to automatically add Banned as a title, so valued members don’t PM them/try to get into conversation, and feel upset to not get a reply.

> [@codinghorror](#):
>
> There is an official browser fingerprinting plugin we’re working on with @udan11 but it’s still got some bugs to work out.

That does have the same arguments against as IP address, this was what my computer showed me just now:

 ![fingerprinting](https://global.discourse-cdn.com/meta/original/3X/c/b/cb988be6145eaf52bffd682450abf004f5da1bd3.jpeg)

And the add-ons that did this are free, unlike a decent VPN. 🙂

---

_[View the full topic](https://meta.discourse.org/t/dupe-ban-accts-with-same-ip-not-being-auto-caught-anymore/94510)._
