[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/jp/ - Otaku Culture

View post   
  [?]In ghost mode, only threads with non-archived posts will be shown
File: 166 KB, 600x811, 1230369094700.jpg [View same] [iqdb] [saucenao] [google]
1974090 No.1974090 [Reply] [Original]

If /jp/ hasn't figured it out yet, someone on /a/ posted the new timers on various types of post.

Regular post: 35 seconds
Image post: 1 minute
Thread post: 5 minutes
Sage post: 10 minutes
Same post: 15 minutes

Don't forget to e-mail moot.

>> No.1974112

/r/ bypass-scripts-in-one for all of them.

>> No.1974123

So saging a post puts you on a 10 minute timer? I have mixed feelings about this.

>> No.1974131

worthless shit like this is for IRC

>> No.1974134

OP of the thread here, it's actually 30 seconds.

Moot has also reenabled cross referencing between /a/ and /jp/.

>>>/a/18319568

>> No.1974139

I, for one, welcome those changes. Sage has been used in increasingly retarded ways.

>> No.1974142

I find all of these timers acceptable and reasonable and I applaud Moot for his policies.

>> No.1974143

>>1974090
ARGH! 5 minutes in between new threads?! I love making threads continuously while watching j-drama. Fuck you for ruining my hobby Moot. Asshole.

>> No.1974145

>>1974134
So I see.

>> No.1974148

>>1974134
>reenabled
reenabled? It was enabled before?

>> No.1974149

>>1974143
It's been that way on /prog/ forever, except that you can't post any replies for five minutes before posting a new thread. It's not that bad actually.

>> No.1974150
File: 37 KB, 263x239, 1232916274442.png [View same] [iqdb] [saucenao] [google]
1974150

>>1974143
It's always been 5 minutes, though.

>> No.1974152

>>1974139
He essentially just killed sage, even though it wasn't even the real problem. The real problem was spamming, and it could have simply been fixed with the 35 second timer. Also, testing.

>> No.1974156

Great introduction, spam shit will hopefully diminish now

>> No.1974159

>>1974149
Why are you responding to a shitty troll poster?

>> No.1974163

It just means people won't use sage when spamming.

>> No.1974167

There is no 35s regular post timer. Sage post isn't 10 minutes.

>> No.1974171

There is no 35s regular post timer. Sage post isn't 10 minutes.

>> No.1974178

>>1974150
No. It was less before. I used to have the three 3-4 top threads on the front page of /jp/ - after teh sage function got killed and 5 minutes breaks were made I can barely hold a single thread on the front page.

>> No.1974179

>>1974152
I don't think spamming was the only real problem. It was also people using sage for things it was not meant for. Sage was never intended to be used to solely show your dislike for a thread, and yet that was it's most frequent use.

>> No.1974181

>>1974152
But the people spamming are still posting at the same rate as the people that aren't.

There's no improvement there.

>> No.1974188

>30 seconds

>> No.1974190

>>1974152 here

It's been 5 minutes and I still can't sage. Yeah, I'm definitely e-mailing moot about this.

>> No.1974191

>>1974179
How does increasing the timer stop that?

>> No.1974199

>>1974191
If one reduces the total amount of sage used, then the amount of retardedly used sage is also reduced.

>> No.1974201

>>1974179
Now people will just bump the thread while registering their dislike, as opposed to just ignoring it like moot thinks will happen. Goddam is moot stupid.

>> No.1974210

>>1974179
Again, who cares if someone improperly uses sage. The thread is still there. It's still in the same position, board-wise. It's only 0.5% closer to the bump limit. As long as there aren't sagebots (/a/), then there's nothing to be concerned about.

>> No.1974211

>>1974199
But sage will still be used retardedly.

>> No.1974213

>>1974152 here

Testing.

>> No.1974224

>>1974218
Multiple sages are allowed. Whoever told you otherwise is lying.

>> No.1974218

>>1974190
1 sage per thread. Sage another thread.

>> No.1974220

>>1974152
>>1974190
>>1974213
Yup, the timer is 10 minutes.

>> No.1974228

>>1974210
But at least I won't be so annoyed from seeing sage being misused.

>>1974211
It will, but on lesser amounts. It's only a slight improvement, but I find it better than before. Nothing of value was lost by adding the timer, so any gain is good enough.

>> No.1974227

>>1974218
I mean, 1 sage/10 minute/thread.

It's 30s if it's in another thread.

>> No.1974229

I, for one, am going to just reset my connection after every sage.

>> No.1974232

>>1974201
>while registering their dislike

don't register your dislike then, going into a thread and posting shit sux does nothing except incite trolling

>> No.1974233

>>1974201
This.

>> No.1974234

>>1974218
I tested it with another thread too, and it didn't work.

>> No.1974238

>>1974201
The new limits will stop people who don't know how to fix the scripts they use. This will help a lot for a while at least.

>> No.1974241
File: 119 KB, 600x750, 1232917173157.jpg [View same] [iqdb] [saucenao] [google]
1974241

>> No.1974251

>>1974201

But they can't post a blank sage or just write "sage for faggotry". At the very least, even someone just putting "That's fucking stupid" instead contributes more and is less disrupting to the thread.

>> No.1974257

>>1974228
And misuse matters because? Do you get angry when someone misuses age by bumping some thread with a retarded comment that contributes nothing? Sage is just like any other post. The only difference is whether or not it bumps the thread.

>> No.1974258

>>1974251
What you've just described is "spamming", which can be done without sage.

>>
Reply to thread [?]Don't expect anything heroic. Your post will not be uploaded to the original board.
Name
E-mail
Subject
Comment
Action