stupidly simple "pastebin" service.

it's a "pastebin" in a very simplified sense. effectively, it:

• accepts (optionally compressed) post requests containing raw content
• saves the content to disk and caches it in memory
• returns a key to indicate the location of the content
• serves content (in a compressed form if the client can handle it) when requested

there's a very minimal HTML frontend for posting content.

the primary intended purpose of bytebin is to act as a middle man in the communication of two separate clients, using payload objects (uploaded to a bytebin instance) as a means to transmit data.

it's also quite good for transferring or sharing large log/plain text files because they're particularly compressible with gzip.

The API fully supports CORS. wooo 🎉

• content can be read from /{key}.

• send a POST request to /post.
• the request body should contain the content to be uploaded.
• it is recommended to provide Content-Type and User-Agent headers, but this is not required.
• ideally, content should be compressed with GZIP before being uploaded. Include the Content-Encoding: gzip header if this is the case.
• the key is specified in the returned Location header.
• the response body is a JSON object with only one property, {"key": "{key}"}.

• I host a public instance at https://bytebin.lucko.me
• you can use it in your application as long as:
  • you're not malicious
  • you don't needlessly spam it
  • your usage isn't illegal or going to get me into trouble
  • you provide a User-Agent header uniquely identifying your application
  • if you're planning something likely to be super duper popular or use a lot of data (> 1GB), then please run it past me first

bytebin uses:

• rapidoid as a web server
• caffeine to cache content & handle rate limits
• guava for byte stream manipulation
• gson to read the config

and plain old java for everything else.

well it's written in java, but.. rapidoid is pretty fast, and so is caffeine.

MIT, go wild.