Automatically remove carriage returns in these use cases

ThrillingHuman

always be casual, never be careless
Joined
Feb 13, 2019
Messages
4,738
Points
183
Just for the record, It's 2024 and the 420 character limit on profile posts is ridiculous. Add to it the fact that we can just comment under our profile posts as many times as we want basically, it honestly is not just pointless but harmful to the user experience.

But what boggles me far more is that this 420 character limit counts carriage returns!

'aight, I get it, in some cases (when separating paragraphs) it makes sense, but why does it have to count the carriage returns between command blocks?

Like, for example, just now (as of the moment of writing this feature request) I wrote a profile post with four images put inside a spoiler each.

It really doesn't make a difference if I write
[.SPOILER][.IMG]etc.
or
[.SPOILER]
[.IMG]
etc.
The end result will look absolutely the same. I feel that of the site is SO concerned with saving space it might as well automate removing carriage returns in such cases.
 
Last edited:
D

Deleted member 76176

Guest
I don't think anybody here likes the 420 character limit. I suppose I can understand the desire to limit the number of attachments, but often the character limit leads to reply spam.
 

Ruti

Your toes are now forklift. Get licensed now!
Joined
Jan 5, 2022
Messages
289
Points
133
Maybe its a packet issue? Since bigger messages = more data to be sent at once, and with a site as big as Scribblehub that's also active, with I think just one person working on everything, they don't want to risk it? there is prob a way to make it bigger risk free, but that would take away time from bug fixes and the like. Yeah, it makes annoying reply chains, but it does also help make sure packets get sent in a timely order, and not like, lag for two minutes not getting sent
 

ThrillingHuman

always be casual, never be careless
Joined
Feb 13, 2019
Messages
4,738
Points
183
Maybe its a packet issue? Since bigger messages = more data to be sent at once, and with a site as big as Scribblehub that's also active, with I think just one person working on everything, they don't want to risk it? there is prob a way to make it bigger risk free, but that would take away time from bug fixes and the like. Yeah, it makes annoying reply chains, but it does also help make sure packets get sent in a timely order, and not like, lag for two minutes not getting sent
These messages get sent just fine.
And regardless, the request is not about increasing the limit. It's about removing unnecessary carriage returns which shouldn't be that hard and would probably take a js function on client side anyway
 
Last edited:
Top