[ yn / yndd / fg / yume ] [ o / lit / media / og / ig / 2 ] [ ot / cc / x / sugg ] [ hikki / rec ] [ news / rules / faq / recent / annex / manage ] [ discord / matrix / scans / mud / minecraft / usagi ] [ aurorachan / desuchan / sushigirl / lewd ]

/sugg/ - Suggestions / Meta

Site meta-talk, help, suggestions, and moderation discussion
Name
Email
Subject
Comment
Verification
File
Password (For file deletion.)

A server move will likely be done in the near future to provide upgraded hardware. This could cause a few hours to a couple days of downtime.

File: 1437571497713.jpg (202.04 KB, 500x500, 1405583014285.jpg)

 No.2313

Someone needs to do something about this ad spam thing.

 No.2314

All we can do is ban them and delete their posts. The filter would inhibit the normal users too much to implement a stricter one. In the past we have polled for the implementation of captchas during the huge CP spam sessions. The community decided that they didn't want captchas.

 No.2315

I'm considering hiring new Janitors if this wave of spam doesn't pass soon. I'd like for us to be catching it faster.

We already have anti-spam measures in place that keep out most bots, but I think some bots nowadays specifically know how Tinyboard/Vichan works, and a few of those float our way sometimes.

 No.2316

I think it would be better to strength those spam measures.

 No.2317

>>2316
This post will be a bit in length.

Our anti-proxy measures are at very full throttle, such that if we turned them up any more there would be risk of blocking legitimate users by mistake. One or two might be blocked once in a while already. These measures block known proxies and bots and "naughty" IP ranges by querying several public real-time intelligence databases that keep track of these things through a number of techniques.

In addition, our new post / new thread forms have several invisible countermeasures designed to trick common and less common bots into revealing themselves and block them from posting. These include extra fields that normal web browsers know to ignore while rendering the page, which look to a bot like they should be filled out and if tripped will block the post, as well as hidden fields with randomized access keys pre-generated into them that will trip the system if they are altered or omitted. Most generalized bots, even many finer-tuned ones, fall prey to these automated defenses, and there are several more active and automated defenses embedded in the Vichan software.

Furthermore the mods rove when they have time and ban bots which I believe have been designed with the specific capabilities to outsmart Vichan's particular automated security measures. These we can do nothing about except to deeply alter the code or to enable captchas, which most people don't have time for or don't want respectively.

The last measure would be to hire Janitors. Unfortunately I have been busy lately, but I am planning and considering a new application process to be started soon if this wave of spam doesn't end, which I don't really expect it to, but I can hope. I'll get around to it when I can. Until then, I trust my staff to keep a watchful eye for the bots that have been bothering us lately.

TL;DR We have been and will continue to be working on it, far beyond what most of the users and the bots are aware of.



[Return][Go to top] [Catalog] [Post a Reply]
Delete Post [ ]
[ yn / yndd / fg / yume ] [ o / lit / media / og / ig / 2 ] [ ot / cc / x / sugg ] [ hikki / rec ] [ news / rules / faq / recent / annex / manage ] [ discord / matrix / scans / mud / minecraft / usagi ] [ aurorachan / desuchan / sushigirl / lewd ]