Board Thread:Internal management/@comment-5079138-20170520052701

There are actually some flaws in the chat section of the rules page, which is why I brought this thing here.

Here they are:

The "no doorspamming rule"
There is a problem with implementing this thing: sometimes the doorspam is caused by a slow connection, though the user doesn't actually refresh the page (apparently the chat tries to reconnect after it detects it's been disconnected, hence the "leaving and reentering chat" messages showing up). Now, I feel like it's kinda inconvenient to kick the user all of the sudden, since they probably won't know why they're kicked in the first place anyway, but there are few solutions:

1. Ask the person to see whether their connection is indeed slow. This could be a decent solution but there's a catch: what if the user is AFK and doesn't respond to the questions?

2. Tell the person that their connection's slow and it causes the doorspam, so they should leave the chat if AFK to prevent further doorspams. Same problem as above.

3. Add exceptions for the rule for those that indeed have a slow network by making a thread and put a list of the exceptions somewhere, which could seem weird at first glance. Problem is, it looks pretty clumpy and anyone can just add their names to the list. I think forcing them to post their speedtest results can be decent sometimes (also check the ISP name and confirm that it's from the same country as the user), but still, some people can just use someone else's results and put their names into exceptions.

4. Post a message that the person's network is slow so we have to kick you, and if they wanna come back just refresh the page. The most logical solution but sometimes this might shock people since no one wants to be kicked all of the sudden.

So if you have any better solutions, tell us, because not everyone is gonna have a half-decent connection to go on chat and that could result in this unintended doorspamming.

No GIF background requests
This should be improved, instead of restricting all GIFs. Instead of banning GIF requests, how about checking the file size instead. If the file size is below the max allowable limit (I recommend <1MB, but you decide), then it's allowed, even if they're GIFs, and vice versa. This is because sometimes huge uncompressed PNG files (e.g. 1440p or 4K PNG files) can also have incredibly huge size (usually over 3MB), and that's another problem. Meanwhile, some GIFs, even if they're animated can take less than 1MB if compressed properly, so it's not a good rule to disallow GIF requests instead of disallowing all pic requests with excessive size.

Specify the max allowable limit below for background images.

There should be a rule for the emoticons too
Just like background requests size restrictions, there should be one for emotes as well, since apparently we ever had some emoticons of consoles (PS3, DS, Xbox 360) that actually take over 1MB, which is ridiculously huge for such tiny emotes. It could be better if the size restriction is much smaller for emoticons (<512 KB might be enough), and if they're too big, one can try using the scaled-down version of the pictures (the wiki supports downscaled picture links, and I think 32 pixels is ideal since I bet it's gonna be scaled down somewhere in that range anyway.) GIF emotes are allowed as long as they don't exceed the size limit. Even at 32x32 pixels the files shouldn't exceed that size limit (especially for animated GIFs).

Not allowing to type more than 3 same letters consecutively
There should be an exception to this. In case of mentioning abbreviations or actual things (like VVVVVV) or AaAaAA!!!, both are actual video games), then it's allowed. Tell us if there are any more things to be deemed acceptable for this rule (besides abbreviations or something that actually exists with such names).

I'll put this as a discussion due to the nature of the thread. 