Version: 1.00, by Zzed
Developer Last Online: Feb 2012
Version: 2.2.x
Rating:
Released: 03-07-2003
Last Update: Never
Installs: 151
No support by the author.
This hack is an alternative to banning a user. As the name suggests a user who
gets hit with this hack will become truly miserable while trying to access
your board.
So here is what really happens to a miserable user:
- There is a random 60-120 second delay each time they click on a link.
- 90% of times they have no search engine acccess.
- 75% of the times they get the server too busy error.
If they don't get the server too busy error:
- 50% of the times they may get a blank page
- 30% of the times they may get forwarded to the forum main page
- 20% of the time they may be able to see the page they asked for.
after doing all the math in actuality they have only a 5% chance of seeing the
page they clicked on. What kills them is the time they have to wait before
anything happens.
I actually once tracked a miserable user and watched him suffer for 2 whole
hours before he was able to make a simple post.
This hack is considered one of the most sadistic hacks on my board.
The hack allows you to make your user miserable via the admin CP. It also
allows you to search for all miserable users through the admin CP as well.
Also in showthread.php, it appends a red status that is only visibly to admins
and mods stating that a user is miserable.
Tables affected by this hack: user
Files affected by this hack: global.php, showthread.php, admin/user.php
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I'm not sure if anyone has suggested this yet, but...
it would be an even more useful hack if it would also (optionally) let you make certain IP-addresses be miserable, instead of users/usergroups.
Why? Suppose you have 2 members, who live in the same building. One of 'm is an ass, the other is fine. If you only block one user, they're likely to figure out that you made *some* sort of change to his/her account. If you block their ip address(es), they'll not know why and reckon it's an ISP/routing problem instead (because that's far more likely then).
I'm not sure if anyone has suggested this yet, but...
it would be an even more useful hack if it would also (optionally) let you make certain IP-addresses be miserable, instead of users/usergroups.
Why? Suppose you have 2 members, who live in the same building. One of 'm is an ass, the other is fine. If you only block one user, they're likely to figure out that you made *some* sort of change to his/her account. If you block their ip address(es), they'll not know why and reckon it's an ISP/routing problem instead (because that's far more likely then).
I'm not sure if anyone has suggested this yet, but...
it would be an even more useful hack if it would also (optionally) let you make certain IP-addresses be miserable, instead of users/usergroups.
Why? Suppose you have 2 members, who live in the same building. One of 'm is an ass, the other is fine. If you only block one user, they're likely to figure out that you made *some* sort of change to his/her account. If you block their ip address(es), they'll not know why and reckon it's an ISP/routing problem instead (because that's far more likely then).
Can be WAY more effective, that way ^_^
I have the IP based misery working in my forums. In fact I have applied it to most of the anonymizers and a few users. It is working like a charm. But I never did an Admin CP interface for it and I enter the information into an array of IP addresses in the php source.
I am not sure if this would interest anyone. I suppose I can make an Admin CP interface for it as well.
I have the IP based misery working in my forums. In fact I have applied it to most of the anonymizers and a few users. It is working like a charm. But I never did an Admin CP interface for it and I enter the information into an array of IP addresses in the php source.
I am not sure if this would interest anyone. I suppose I can make an Admin CP interface for it as well.
Would be nice. If you could send it to me I could also do it for vB3, but that's up to you
After playing around a bit, I installed this in VB3... it wasn't a full hack though. I just added the miserable code to global.php and then added the miserable column to the user table.
To make it work you have to run the query manually for each user that you want as miserable.
Here's my implementation:
Open miserable.txt and run the query
Apply the first modification to global.php ONLY and upload it
For each username you want miserable, run this query
update user SET miserable="1" WHERE username="xxx";
replace xxx with username
Not the cleanest hack in the world but we were desperate for it, :P
djnoz, it can be done a lot easier than that on vB3
For this to be applied on a vB3 board, you really should just make a new (secondary) usergroup called "Miserable Users", make it non-public and put people in that group (along with their normal group, ie. the Miserable usergroup has no additional permissions anywhere, it's just important to note the usergroupid). Then in global.php, put the Miserable code and make it dependant on the usergroupid of the Miserable usergroup, check for it in $bbuserinfo[usergroups] (iirc)
An alternative to banning: Miserable Users Details »»
About Developer
Visit Web Site
No support by the author.
10-22-2003, 02:18 PM
