automated censorship tools

detect an prevent people posting hate speech before it happens

wow, I'm amazed by these.

>>39
Not impressive until it's vertical.

A Submission to the /prog/ Journal of BBCODE, volume 666: An Observation on the Behavior of Underlining in a Multilevel Vertical BBCode Latice Structure - By Gerald Jewish Sussman.

...........................................................
:
:
:
:
:
:
: 1
4
72
5
83
6
9

  :
:
:
:
:
:
: The source code to the
^B_BCODE on the right
is as follows:

  :
:
:
:
:
:
: [m][s]1
4
7[/m][m][aa]2
5
8[/m][m][b]3
6
9[/o][/aa][/s][/m] :
:
:
:
:
:
:
...........................................................


Interesting behavior going on.
Take note of the [s], [aa] and
[o] tags. Each one only effects
the column that it is started
in, and not the others. However,
this appears to only be the case
for tags that generate a <span> in
HTML. When elements that generate some other HTML tag, such as [b],
or [i], the effect continues throu-
ght subsequent columns. It is al-
so the case that some elements,
such as [spoiler] or [sup], fail
to parse correcly at all. But pe-
rhaps the stranges behavior of
all is that of [u]. When [u] is placed in the place of [aa], it
does not underline everything in
the following columns, but it act-
ually underlines everything except
the very bottom of the final column.

What a strange thing for [u] to do!
 

detect an prevent people posting hate speech before it happens

well, if hitler won....

I have no idea where to begin in replicating this.

_⁶⁶Replication crisis in /prog/tology: over 65% of the BBCODE studies failed to replicate. "I have no idea where to begin in replicating this" says >>45!!_⁹⁹

It is also the case that some elements, such as [spoiler] or [sup], fail to parse correcly at all.

That's because you're not nesting correctly, and some tags won't have any of that.

>>47
I'm nesting exactly how I intended to nest. Edge case behavior makes for better study.

(Post not truncated)

vip quality

_{⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠}^{⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠⎠}

Report on how >>53 renders:
Firefox: Slopes met before the edge of the screen and move vertically only. Characters continue off screen though. The weird ⎠ character is not not as tall as in chrome. The top sticks out of the spoiler more than the bottom, so the bottom slope is larger.
Chrome: The slopes are fully diagonal, leaving a large blank gap in the post. ⎠ is very tall.
Opera 12: A single horizontal bar of spoiler, like three lines high. Ugly.
Internet Explorer: took like five minutes to render, browser frozen during that time. Didn't bother mousing over it. Presumably more freezing.

StarShip Quality!

>>53

KING EPIC BBCOAD MAN

WE CONJUR THE SPIRITS OF OUR BROWSER WITH OUR BBCODE SPELLS
WE CONJUR THE SPIRITS OF OUR BROWSER WITH OUR BBCODE SPELLS
WE CONJUR THE SPIRITS OF OUR BROWSER WITH OUR BBCODE SPELLS

So ^[aa] doesn't allow text to change size? Good to know.