Due to the recent forum outages, it may be useful to close the [scratchblocks] testing topic, as it would put a lot less strain on the forums. Additionally, most posts on that topic are by users who already know how to use the [scratchblocks] tag basically “blockspamming”. If someone wants to test out the [scratchblocks] tag, they can do it the same way they use to test out any other type of BBCode: the green preview button.

support. it also encourages people to block spam. because often times the posts are block spam not posts that should be posted.

Support. Useless.

It looks like it gets about 33 posts per day averaged out over the time the current topic has been open, while the last week on the forums as a whole has averaged about 2000 per day. That means posts to the scratchblocks testing topic form less than 2% of all forum posts. While I think there are plenty of legitimate reasons to close the topic (including ones identified in the OP), I don't think it really contributes much to the forum outages.

jvvg wrote:

(#4)
It looks like it gets about 33 posts per day averaged out over the time the current topic has been open, while the last week on the forums as a whole has averaged about 2000 per day. That means posts to the scratchblocks testing topic form less than 2% of all forum posts. While I think there are plenty of legitimate reasons to close the topic (including ones identified in the OP), I don't think it really contributes much to the forum outages.

What about loading the darn thing? One less mega-topic eating server time every time somebody wants to load it. It takes me around ten seconds at least to load it when most threads take one or less.

kkidslogin wrote:

jvvg wrote:

(#4)
It looks like it gets about 33 posts per day averaged out over the time the current topic has been open, while the last week on the forums as a whole has averaged about 2000 per day. That means posts to the scratchblocks testing topic form less than 2% of all forum posts. While I think there are plenty of legitimate reasons to close the topic (including ones identified in the OP), I don't think it really contributes much to the forum outages.

What about loading the darn thing? One less mega-topic eating server time every time somebody wants to load it. It takes me around ten seconds at least to load it when most threads take one or less.

I'm pretty sure that's on your computer's end, not scratch servers. I'm pretty sure all the servers send is the bbcode, which is just as much as a moderately long post, and then it takes time for your computer to render all of the scratchblocks. I could be completely wrong though.

undeterministic wrote:

support. it also encourages people to block spam. because often times the posts are block spam not posts that should be posted.

It's literally a place made to absorb the blockspam that would go on other topics. If anything, the existence of a topic makes people less likely to blockspam on other topics since they know they're supposed to do it there. Plus, it's a good way to learn scratchblocks tricks.

MythosLore wrote:

they can do it the same way they use to test out any other type of BBCode: the green preview button.

Well given the existence of blockspam, people evidently don't do that.

portal power wrote:

It's literally a place made to absorb the blockspam that would go on other topics. If anything, the existence of a topic makes people less likely to blockspam on other topics since they know they're supposed to do it there. Plus, it's a good way to learn scratchblocks tricks.

Mose users that don't know about the topic typically make a blockspam topic or blockspam on a constructive topic, and then get redirected to the testing topic by other users. Couldn't the users just redirect them to the green check button instead?

The best thing they can do for the forums is update them.
Although, for the time being, perhaps dustbinning every post made in them at the end of a day could help. It addresses the issue in the post while also allowing users to test out blocks.

GlitchedThrough wrote:

The best thing they can do for the forums is update them.
Although, for the time being, perhaps dustbinning every post made in them at the end of a day could help. It addresses the issue in the post while also allowing users to test out blocks.

Or maybe that you can delete the current topic and create a new one which gets deleted every week, replaced with a new one.
—
I wouldn't advise deleting the topic as a whole as there would be more blockspam since they probably do not know what the preview button is and if one user accidentally posts, than it might be accidental spam.

dont support i love block spamming there

Partial support, but you might not know all the features of this* feature


*

this one :: grey :: cap

jvvg wrote:

(#4)
It looks like it gets about 33 posts per day averaged out over the time the current topic has been open, while the last week on the forums as a whole has averaged about 2000 per day. That means posts to the scratchblocks testing topic form less than 2% of all forum posts. While I think there are plenty of legitimate reasons to close the topic (including ones identified in the OP), I don't think it really contributes much to the forum outages.

i'd love to discuss this but i feel like it might play a fair part. after all, even opening large topics can cause djangobb to have a small fit. besides, we also have a github.io website for scratchblocks, https://scratchblocks.github.io

Banana

Bump

Bump

jvvg wrote:

It looks like it gets about 33 posts per day averaged out over the time the current topic has been open, while the last week on the forums as a whole has averaged about 2000 per day. That means posts to the scratchblocks testing topic form less than 2% of all forum posts.

Yeah, and it's not like the traffic created from people posting there contributes to any server strain either, considering the overall traffic. For the first time in a while, semi-support

banana439monkey wrote:

(#12)
i'd love to discuss this but i feel like it might play a fair part. after all, even opening large topics can cause djangobb to have a small fit. besides, we also have a github.io website for scratchblocks, https://scratchblocks.github.io

Banana

I honestly believe that the github page could just be linked, though it's much simpler to do scratchblocks here because of the preset catalogue thing rather than doing it text based by yourself.

ajskateboarder wrote:

Bump

jvvg wrote:

It looks like it gets about 33 posts per day averaged out over the time the current topic has been open, while the last week on the forums as a whole has averaged about 2000 per day. That means posts to the scratchblocks testing topic form less than 2% of all forum posts.

Yeah, and it's not like the traffic created from people posting there contributes to any server strain either, considering the overall traffic. For the first time in a while, semi-support

I will report to close scratchblocks part 8

support! i feel this is required after how much the forums have been down recently!

WE'RE ON TOPIC 9 BABY!!!
yeah this is getting out of hand

Banana

I rarely post there, and there is a bunch of spam, blockspam, and spam posts, so um… yeah, I agree.

It's getting so out of hand that I don't eve post there anymore.

That forum just seems unnecessary. If you want to test scratchblocks, just go to a random forum, put in all of the scratchblocks you want, click the green check, and don’t click Submit. I agree.