[BUG] Lame character limit that does not even work

MXXIV·2/24/2014, 6:46:08 PM·3 votes·463 views

Hi, judging from votes on this post*****, I believe I'm not the only one who suffers from 30 character limit in the poll question. However, what is really funny is that board developper was retarded enough to add that limit only to bother users without implementing on the server side.

What does that mean?
If you open a developper tool in your browser (Firebug for example), you may change the character limit for the field.

screenshot 1 Now change or remove the option: screenshot 2

Now why am I posting this?
Riot is consistently failing in making good community forums. While I do not agree with those, who liked the previous board more (I was just so fucking disoriented there) I think Riot team is not actually trying to convince those that this beta is better.
This bug is not a proof of that, it's just a random error. The real problems are things like horrible page speed and slow rendering speed too.

While many useful functions appeared (admit it, we missed updates back there) there are still many issues that a script kiddie like me can figure out.

So guys, please abuse this bug. I hope they'll increase the character limit instead of implementing it server sided - because that's what I don't want to happen.

Why such an angry tone?
I don't always post like this and I'm trying to restrain to hate on other programmers. But what enrages me to the top are those annoing, user-bothering limits that have no reason.
Really, when I found out I can't finish a short sentence in poll... Just why omg? This combined with the things on forums not working and slow loading made me use this tone instead of fair bug report. Sorry.

* So the permalink function does not work, so I can't link that post.

8 Comments

Bob LLama2/24/2014, 7:49:29 PM3 votes

Hey MXXIV,

Thanks for the feedback. We had to set a limit at something, so we looked at usage patterns and decided that, based on how most people had been using polls, a 30 character limit was sufficient. Our thinking is that the poll itself is really for casting a vote, and the body of the post can serve as the longer discussion on the matter.

The other consideration was aesthetic: we want to make sure that we don't overload the area with text and make it a visually confusing space.

As you may know, we're still in beta, which means we're still actively looking and working on things. We had to start somewhere, and we're learning from the feedback we get. We actually do already have the limits on the server, they're just disabled at the moment (since we're still working on all this).

If I may ask, what were you expecting the poll limit to be?

MXXIV2/24/2014, 7:04:11 PM1 votes

Some idea why permalink might not work:

            <a class='toggle-reply-form' href='javascript:;' data-bind='click: updateUrl, visible: !showConfirmDelete()'>
          Permalink
        </a>

I'm not sure how the templating stuff works, but maybe we might be happy that clicking permalink does not delete our post...