alfg / jot

:pencil: A server-less pastebin app for short messages. Data is stored within the URL.

Jot

A server-less pastebin-esque note-taking app.

Demo: http://alfg.github.io/jot

Features

• A simple, elegant design
• Retains formatting of messages
• Data is base64 encoded into the URL hash, so no data is stored on a server
• Easy to share via encoded URL
• Simple to deploy. Just a few static files.
• Add a secret key with encryption support via Blowfish

Notes

• Most modern browsers limit the URL to 2000 characters. Messages can easily generate a long URL depending on the content. So it is best to keep messages minimal (TODO lists, short snippets of code, etc...).
• Use a URL shortening service to shorten the URL when sharing. Jot URLs can typically be very long depending on the content.

Examples

http://alfg.github.io/jot/#eTWF5IHRoZSBzb3VyY2UgYmUgd2l0aCB5b3Uu http://alfg.github.io/jot/#eVGhlIGtleSB0byBoYXBwaW5lc3M6CgoqIEVhdAoqIFNsZWVwCiogQ29kZQ== http://alfg.github.io/jot/#btU/VJBS+XgS/Qjs6YPI7lRVCUSA1E/OxMDm1z+ZC9R8 (key is foobar)

License

jot is open-source under the MIT License.

jot's Issues

It's more efficient to copy and send your message than use jot.

(lib)root@awesomevm:# echo "Base64 takes more space than the original message" | wc -c
50
(lib)root@awesomevm:# echo "Base64 takes more space than the original message" | base64 | wc -c
69

Blowfish representation:hex to base64

Currently an encrypted message takes up twice the numbre of chars as an unencrypted message, due to the hex representation of the former versus base64 for the latter. In order to save some chars, it'd be nice to convert the hex to base64 and back.