Tripcode testing thread

ITT I will perform some saged experiments with tripcodes.

Here's the full range of characters usable in tripcodes.  Other characters either mirror (only the lowest 7 bits are checked in tripcodes) these, or expand (& -> &, etc.) to something you can already express with this.

char charset[] =
  "\x80\x81\x82\x83\x04\x05\x06\x07\x08\x89\x8a\x0b\x0c"
  "\x0d\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19"
  "\x1a\x1b\x1c\x1d\x1e\x1f !\xa2#$%\xa6'()*+,-./012345"
  "6789:;\xbc=\xbe?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`ab"
  "cdefghijklmnopqrstuvwxyz{|}~\x7e";

>>151
Now that I think of it... you could just use \x80-\xff ;)  I prefer printable characters though.

>>153
That only works if you're using an iso8859 layout. Highly unreliable and prone to generating invalid multi-character combinations. Also sage.

>>154
PHP doesn't bother itself with such petty matters.  If it's in a string -- it's ASCII.

Sage for not Unicode

>>155
Nope, if you're using the mbstring extension, you're treating whatever character set/encoding you chose, which for your own sake should be UTF-8, and substr, strlen, etc. will work accordingly. For UTF-8, you can also use preg_* if you specify the u flag. And thus, the only non-Unicode operation remaining in PHP is the one you probably want to leave as such - $a{n}, which gives you access to raw octets. (For string slicing use substr.)