Title
Block IP
Short, concise description of the idea
A simple way to block spam or internet attackers who use the Anonymous feature, without having to block all Anonymous posting.
Full description of the ideaInstead of having a user block all Anonymous posts or having the user delete each spam or trolling post, create an option to block the
(
Read more... )
It would be also very useful if, when an IP address is blocked for anonymous commenters, any logged-in comments originating from that IP are flagged somehow (and the usernames listed in the banned IP list next to the IP). This obviously won't distinguish between moments when a so-called friend is being a dickwad anonymously but nice as pie when logged in and situations where an anonymous dickwad happens to have used the same IP as a friend (friend-of-a-friend being a dickwad on friend's computer is one scenario that springs readily to mind) ... but it would be a useful thing to know.
Say something like this:
Unblock?IPBlock DateBlocked FromUsers commenting with this IP since blocked
[ ]127.0.0.12001 May 02 11:21:05http://azurelunatic.livejournal.com/5848457.htmlNone
[ ]192.168.0.22001 May 03 15:30:59http://azurelunatic.livejournal.com/5844148.htmlexampleusername
frank
status
Reply
Searching through posts to find comments made with the IP address seems like it might be resource intensive. Perhaps it would be better to simply add "BLOCKED IP" after the IP address wherever the IP address would normally be displayed.
Reply
I wouldn't have it searching actively in past comments - I'd have it running all new comments made past the IP address block list -- perhaps in the same or similar part of the comment creation process where it checks for ban status from the journal? -- and then if the IP is banned for anonymous users, it appends the username creating the comment to the list. And possibly generates an event that one can subscribe to.
But putting "blocked IP" after the IP address is something like where I was going with the "flag comments" idea.
One could probably make a client-side script to note IP addresses of deleted anonymous comments and flag logged-in IPs based on that, though it would not be half so useful as an LJ-side tool.
Reply
Reply
I also like how you organized the management window for your example. As it stands right now, deleting a comment does not keep track of anything. I think that any additional benefits with minimal work would be is worth implementing.
Reply
I like that your suggestion here differs from most other ideas I've seen on the same lines in that it only affects people posting as anonymous. Most of the other ban-based-on-IP suggestions I've run into involve affecting logged in users based on their IP, which is completely not fair for the reasons mentioned above.
But between limiting the blocking to anonymous comments only, and tracking the logged-in usernames commenting from an anon-blocked IP, and having a new username pop up on that list as a subscribable event, and allowing the blocking of IPs without having an anonymous comment from the IP to delete, and having banning users as a tool, I think this would accomplish the same things that people who want wholescale IP blocking would want done, and neater.
Say you suspect exampleusername of being the one behind all those trolls you're getting. You already have anonymous commenting turned off. Additionally, you block the IP address that exampleusername has been using. You see that sure enough, when status trolls you, you've got a hit on that blocked IP. So you ban status. Then you get a trolling comment from frank. Same IP. Ban-time, and you may have enough ammunition to report the trio of usernames for possible ban evasion.
You won't wind up blocking trollish comments from the same IP before they start, you won't necessarily prove that the offender is one and the same person, but you won't wind up blocking unrelated logged-in users who happen to be on the same IP, although there's the potential for social stickiness should someone with the same IP show up in all good faith when you're watching that IP with murder in your eyes.
Reply
Reply
Leave a comment