Push blueprint to gist

[matt-dray]

Reincorporate ability to push to a GitHub gist (as per v0.0.0.9000) to back-up/preserve a blueprint, possibly to allow for battling against other's pets, as per #8.

[mattkerlogue]

possibly to allow for battling against other's pets

You could add a level of rudimentary obfuscation by using some sort of a hashing function, using the pet's name and/or the user's GitHub username as the encryption/decryption key. That way people don't know in advance the capabilities of the other pet(s).

[matt-dray]

@mattkerlogue: Bingo, you're right, hashing is for sure on the cards. I don't want to waste any effort into making the blueprints truly uneditable (this package is for larks, after all), but I'd like to obscure them and not expose all the values that appear in the blueprint versus what appears when you print with get_stats() (it's possible I'll be adding some more 'hidden' variables like a randomised 'individual value' that may affect XP collection and other things, or a secret HP counter, or a counter that increments each time hunger reaches 5 or happiness reaches 0).