ghostbin is a paste service, and i’m going to skip explaining precisely what that is—it’s fairly obvious. the real interesting questions are “why did you build it?” and “where did i get all these bees?”
for the first, i’d like to first list my inspirations and driving motives. when i started, i’d recently fallen in love with a small font named envy code r. i’d wanted to put together a paste service (under my own control) for some time, and envy provided the final impetus; it made my code look awesome—more awesome, in fact, than my code truly was.
at nearly the same time, i’d decided that i wanted to learn go. the confluence of these two endeavours could not have been more piquant.
other popular, functional and attractive pastebin services certainly do exist, but i found them to be somewhat lacking:
* pastie was cool, but the ability to delete private pastes eventually evaporated. later, the ability to even edit private pastes—which was rather useful for affecting a simulacrum of deletion—vanished. pastie is not private by default.* pastee is private by default and provides both encryption and expiration, but it looks like it tumbled from the proverbial ugly tree. it’s functional, though, and that’s great. it seems to use pygments, much like ghostbin, but it doesn’t appear to have an updated language list.* hastebin looks neat. i have no qualms with it.ghostbin is an attempt at not only solving the above, but also solving some issues in the industry such as, but not limited to, me not knowing go. it’s opensource and i don’t think it’ll be going anywhere any time soon. it supports encryption, expiration, pastes up to one megabyte, and about six billion languages. well, some hundreds at the very least. also, doesn’t that paint job look simply dandy?
and—get your bees away from me. i don’t even know what you were expecting in bringing them here.
source code is available at https://github.com/dhowett/ghostbin and http://git.howett.net/paste.git
