A brilliant/terrible idea

If you hang out on the imageboards at all, there's a cool greasemonkey script available that allows you to play .ogg audio files catenated to an image. After the novelty wore off, I started thinking.

You can't upload images to /prog/, but there IS a possible way to upload .ogg, archives, or even image files here. ASCII and Unicode characters are stored as integers, right? One could create a script that converts a file into a string of characters, which can then be posted into /prog/. A greasemonkey script could convert any encoded file (surrounded with a new EXTENDED BBCODE file tag, so that those with the script do not have to see a million characters) into an audio file, archive, image, whatever.

The only problem is that of a maximum post length. Does anyone happen to know the maximum characters allowed in a /prog/ post? I've seen some very long ones, so I assume its greater than the standard imageboard post. If it is necessary, one could modify the script to spread file data over several posts, allowing for potentially unlimited file sizes.

>>29
You can't just read the bytes as chars ala uuencode or you'll run into a variety of problems. For one, multiple newline characters are condensed by shiichan into 1, resulting in file corruption. Addition, the various null characters would most likely be stripped by the board software.
I don't really understand you. Didn't you do any research? Do you understand how uuencode works?
Just use Base64 or Ascii85 or whatever.

Let us assume then that there are at least 163 Unicode characters printable by the Shiichan software.
And are you certain that the software won't interpret multi-byte Unicode characters as multiple ASCII characters? I mean, you couldn't use Unicode to increase the amount of information you can fit in a post.

Files are encoded "in reverse."
It seems you actually thought about the system a little, I like that.

Also this project isn't the best use of your time; as enticing the prospective of uploading stuff directly to Prague is, I wouldn't want to see it cluttered with shit.

>>31,33,36
Take a look at the HTML code generated by BBCode tags (especially [spoiler] tags).