sudo rm -rf --no-preserve-root / pcaversaccio

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

How do you POST a JSON file with curl??

You can post a json file with curl like so:

curl -X POST -H "Content-Type: application/json" -d @FILENAME DESTINATION

so for example:

EMOJI CHEAT SHEET

Emoji emoticons listed on this page are supported on Campfire, GitHub, Basecamp, Redbooth, Trac, Flowdock, Sprint.ly, Kandan, Textbox.io, Kippt, Redmine, JabbR, Trello, Hall, plug.dj, Qiita, Zendesk, Ruby China, Grove, Idobata, NodeBB Forums, Slack, Streamup, OrganisedMinds, Hackpad, Cryptbin, Kato, Reportedly, Cheerful Ghost, IRCCloud, Dashcube, MyVideoGameList, Subrosa, Sococo, Quip, And Bang, Bonusly, Discourse, Ello, and Twemoji Awesome. However some of the emoji codes are not super easy to remember, so here is a little cheat sheet. ✈ Got flash enabled? Click the emoji code and it will be copied to your clipboard.

People

😄

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.

Translations: (No guarantee that the translations are up-to-date)

🇫🇷 Cette liste en français

Cryptographic Best Practices

Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.

The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from

	" Don't try to be vi compatible
	set nocompatible

	" Helps force plugins to load correctly when it is turned back on below
	filetype off

	" TODO: Load plugins here (pathogen or vundle)

	" Turn on syntax highlighting
	syntax on

	/**
	* Encode string into Base64, as defined by RFC 4648 [http://tools.ietf.org/html/rfc4648].
	* As per RFC 4648, no newlines are added.
	*
	* Characters in str must be within ISO-8859-1 with Unicode code point <= 256.
	*
	* Can be achieved JavaScript with btoa(), but this approach may be useful in other languages.
	*
	* @param {string} str ASCII/ISO-8859-1 string to be encoded as base-64.
	* @returns {string} Base64-encoded string.

	# Assume we are in your home directory
	cd ~/

	# Clone the repo from GitLab using the `--mirror` option
	$ git clone --mirror [email protected]:mario/my-repo.git

	# Change into newly created repo directory
	$ cd ~/my-repo.git

	# Push to GitHub using the `--mirror` option. The `--no-verify` option skips any hooks.

	//
	// The new assembly support in Solidity makes writing helpers easy.
	// Many have complained how complex it is to use `ecrecover`, especially in conjunction
	// with the `eth_sign` RPC call. Here is a helper, which makes that a matter of a single call.
	//
	// Sample input parameters:
	// (with v=0)
	// "0x47173285a8d7341e5e972fc677286384f802f8ef42a5ec5f03bbfa254cb01fad",
	// "0xaca7da997ad177f040240cdccf6905b71ab16b74434388c3a72f34fd25d6439346b2bac274ff29b48b3ea6e2d04c1336eaceafda3c53ab483fc3ff12fac3ebf200",
	// "0x0e5cb767cce09a7f3ca594df118aa519be5e2b5a"


	00D1E5
	0111E
	0115
	011ED
	011F1E1D
	011F1E1D5
	015E
	01AF
	01D1E