/b/ - Random

>>76112(OP)

With that pic i thought this post was by the necrobumper.

Thanks for the thread sirs. Based on our conversation with esteemed members of bhach in the thread >>>/b/75921

We had few of the solutions to prevent necrobumpers or spammers,

1. Easiest Option: Cooldown

It's very effective that we know of, easy for mods and boards remain comfy. We are willing to reduce the timer down to minimum of 30 minutes if anons agree.

Problem: It affects new users, especially those who for some reason can't have a separate browser and instead want incognito.

2. Mix of Flood Prevention and Captcha Limitations

This means we can effectively reduce total number of posts by a given user in a certain time period. Which means like as minimum as 7 replies in 15 mins, 25 replies in 50 minutes etc. etc.

Apart from this, obviously not enough, would require -

>increase in captcha length - say 6 to 8.

>Increase in captcha timer duration - currently it's 5seconds, next at bare minimum of 15 seconds

Is this effective prevention? Not as much as cooldown but can reduce to an extent - though bump would happen still.

Problem: Max Experience worse for every poster - punishes everyone. Awful in many ways.

3. Middle Path - hard limitations on new users but no cooldown

This in theory can be effective which means for new users we will have

>captcha length of 7 at minimum

>captcha duration of 30 seconds at minimum

>posts per hour would be like 6 or 7

>threads per hour would be like 1

After say 4hrs limitations will be reduced, after 12hrs they will be reduced to pretty normal. Plus point is no old poster will be punished. It will be very effective yes.

Problem: I need few days to work this through - which means for few days (3 days max) we will have a strong cooldown of 30 minutes.

That's all.

>>76151

>ad banners

add into the middle path

farm this necrobumpers clicks and spammers clicks

>>76158

Kek...only if.

>>76176

>>76167

Cooldown earlier was for 15 mins. He created 4 separate instances all detected and banned.

That's one necrobumper. Other one was separate and has been dealt with too.

>>76210

Because he has few instances which were from before that time. Unironically you are batting for longer cooldown sirs.

Let's have this temporary and we will go with the middlepath with no cooldown but restrictions on the new users.

>>76160

4chan literally fingerprints the devices, uses sesisons, IPs to maintain ban throughout.

Second a slower board is easy to disrupt by spammers, usually active boards will result in eventually active threads coming on top - here it's not the case so spammer threads get bumped to the top.

>>76235

For now it's been pushed to 1hr.

Necrobumper, other than Duck's retardation, has been banned, all his instances. Let's see now sirs.

>>76246

he tried to aid them in the past, though there are not enough data on that - other than if you accept his own admission in the other thread - that he is a negrobumper.

>>76252

Working on the middle path sirs. In the meantime it should be slightly better currently.

>>76258

>I never aided any necrobumper, I just gave a non-virgin cookie id so normal people could post.

One thing i have learned from this drama is to keep records of spams - in case someone questions the actions. I do not have any issue with you per se but don't lie, pic related.

>Mazak kar raha tha sirs, maybe stop looking at fingerprint of every user in backend.

I have to work a bit - to prevent issues like these. I can't without looking through the patterns into what is happening. There's not much information than usual which was required in your case.

>>76257

kek

>>76265

yeah i get it, though overall i saw three instances by you

>2 for these - different threads

>1 when you shared your credentials - account was already banned so ig no action was taken against you for that.

anyway nvm.

>>76266

absolute state desu.

i think one mod shared it earlier.

I was not available for moderation yesterday since at all cost i wanted new update out - it was occupying my mind space and i had one issue at office which had literally me working late 1am in the night - just when i pushed the update i see mods and anons everyone is cribbing and painted me villain.

>>76267

Well there were certain limitations on mods part. But they do help out a lot sirs. Now they should be more capable in their actions after new updates.

>>76271

kek

>>76276

true

>>76112(OP)

7 people voted for 30 mins timer

2 for 4hrs timer

1 for 6hrs and 2hrs respectively

>>76717

>>76718

literally wrote about it here in detail >>76151

Stop gaslighting.

>>76739

>tracking through IPs, Sessions as well as device fingerprinting

>maybe ip ranges, location information too

I don't want to collect this much information at all. IP range limitation won't work. Location info too.

>also flood detection - based on number of posts per hour, or in a given time, media hash checks etc.

We already have flood detection to a limit.

Some of the things like ip range, location information and device fingerprinting is out of the question.

That leaves us to work with IP, session, flood limits - that is actually more than enough that we need. Before the new things are implemented i need a temporary solution - hence session thing for just few days.

>>76746

Not a bad idea desu, in theory it can be done - let me look into it sirs. Thanks.

>>76756

yeah the new user thing is retarded methinks

>>76756

>>76765

sou desu

>>76771

bad japanese

but meant - sure.

>>76776

brootal

>>76778

its ok we still love u

>>76794

me_irl