"Read More" on Posts

Morimop

Sometimes, we see very very long posts. It is hard to read, it is hard to scroll down. It just makes page longer.

To prevent this, I'm suggesting a “Read More” post. It can appear on posts which have 30+ lines.

What do you think? Should it appear on posts which have more lines or less lines? Should it has “Close it”?

(also i dont have a idea about “read more” jokes)

Nambaseking01

Agreed, because the current character limit is 200,000 and that's a lot of characters that one can use. To prevent people from taking this as an advantage, we could have this button as a layer of…protection from going crazy about reading (is that a thing?)…

coder2045

Support. Once, in the old scratchblock testing topic, I saw a post with boolean blocks in other boolean blocks about 800 times in the same post. It made the page crash.

Nambaseking01

coder2045 wrote:
Support. Once, in the old scratchblock testing topic, I saw a post with boolean blocks in other boolean blocks about 800 times in the same post. It made the page crash.

There's also been a trend going on in the Announcements forum that people keep putting forever loops inside forever loops, and this system could prevent that as well.

Morimop

myeh bump

coder2045

Nambaseking01 wrote:
coder2045 wrote:
Support. Once, in the old scratchblock testing topic, I saw a post with boolean blocks in other boolean blocks about 800 times in the same post. It made the page crash.

There's also been a trend going on in the Announcements forum that people keep putting forever loops inside forever loops, and this system could prevent that as well.

I never saw that.

Nambaseking01

coder2045 wrote:
-snip-
I never saw that.

Me and a couple of other Scratchers saw it, so you can't possibly find a blame.

Morimop

hee-bump

Dragonlord767

This is a duplicate, I remember making a topic on this, however, I can't find the link.

Morimop

Dragonlord767 wrote:
This is a duplicate, I remember making a topic on this, however, I can't find the link.

Oh, I'm sorry then. Please report this topic if you find it.

60 seconds yeeeee
small little pains

Morimop

bumğ

Nambaseking01

Morimop wrote:
bumğ

what for an alphabet is that

(Excuse me for derailing this topic, but I need to investigate as I want to become a writer when I'm big)
(Seems like the 60-second rule doesn't want me derailing anything…)

Morimop

Nambaseking01 wrote:
Morimop wrote:
bumğ

what for an alphabet is that

(Excuse me for derailing this topic, but I need to investigate as I want to become a writer when I'm big)
(Seems like the 60-second rule doesn't want me derailing anything…)

it is…
s o f t g

Nambaseking01

Morimop wrote:
it is…
s o f t g

Noice

Morimop

heey b

Morimop

Morimop wrote:
heey b

Morimop

bump

-ShadowOfTheFuture-

coder2045 wrote:
Support. Once, in the old scratchblock testing topic, I saw a post with boolean blocks in other boolean blocks about 800 times in the same post. It made the page crash.

To be honest, I'm not sure if a Read More tab would solve this problem. Unless the Scratchblocks spam is buried under 30+ lines of text, which usually doesn't happen, the Scratchblocks would still be clearly visible. Correct me if I'm wrong here, but if each line of Scratchblocks counts as one line of text, booleans within booleans would only count as one line per nest. Even if you instead cut the post off at 30 lines' worth of space instead of at 30 lines, I feel like you'd still have to load in all the blocks, since once again they would all still be in one line.

One way you could fix this would be to prevent excessive Scratchblocks from loading before Read More is clicked. Maybe if the post is long enough to merit a Read More, any Scratchblocks within it would be initially replaced with labels stating "click Read More to view these blocks" or something like that. You could even have the posts display individually in a separate tab, though I'm not that sure about this since it would probably be inconvenient.

fdreerf

No support. There really isn't a point, like yeah, you have to *gasp* turn the scroll wheel or press “page down” one more time, but clicking read more is that 0.1% more inefficient and cumbersome than doing something you were already doing, and how would a button prevent spam? Sweeping something under the rug and concealing it does not solve it.

Morimop

bump
my last bump..

Discuss Scratch