You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I'm playing w/ 256-color xterm colors and UTF-8 for.. reasons. ░▒ blends of the 6^3 color grid yield 6036 colors;
more mixed w/ the greyscale ramp. Add the base 256 color set w/ Block Elements (▙▂▚) for sub-char-size pixels, bloom, and dither for a libcaca/libtcod clone?
Why limit yourself to block characters? There must sometimes be ASCII or UTF-8 characters which are better approximations of a block of pixels than the block elements...
(One good answer is that it would be a hell of a lot more difficult to find the exact foreground/background/character combination which is perceptually "best".)
I started w/ just quarter block elems @ 4 taps per glyph. Then tried including 5 and 6/8ths vert/hor glyphs to trade error in pairs of taps against the other. W/ 64 taps/glyph, I get that for free and can get the GPU to do it all and can regress to trade accuracy for speed later.
Block elements have known pixel coverage masks. 3/8ths of the square vertically, etc. If I associate each character with an 8x8 block of pixels I can compute exact approximation error for a given pair of colors. Most stuff outside that block is less well behaved in unknown fonts.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
