Bitcoin miners want their newly-found blocks to propagate across the network as quickly as possible, because every millisecond of delay increases the chances that another block, found at about the same time, wins the "block race."
// Just before switching jobs: | |
// Add one of these. | |
// Preferably into the same commit where you do a large merge. | |
// | |
// This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
// and then it quickly escalated into more and more evil suggestions. | |
// I've tried to capture interesting suggestions here. | |
// | |
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
# wiki page | |
https://en.bitcoin.it/wiki/Contract | |
# Nick Szabo essays | |
http://szabo.best.vwh.net/smart_contracts_idea.html | |
http://szabo.best.vwh.net/smart.contracts.html | |
http://szabo.best.vwh.net/micropayments.html | |
# secure multiparty computation in bitcoin | |
https://eprint.iacr.org/2013/784.pdf |
I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.
If you want to roll up all of these into a single jQuery plugin check out Sharrre
Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
#!/usr/bin/env bash | |
# Colours picked from https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/ | |
### | |
# Label definitions | |
### | |
declare -A LABELS | |
# Platform |
var singleString = 'Some Artist - Some Title'; | |
var duration = 600; // length in seconds (required!) | |
// ideally, you have an object with the artist and title separate (and maybe credits!) | |
// you can use soundtrack.trackFromSource('object', ... , ...) for this | |
// see https://github.com/martindale/soundtrack.io/blob/soundtrack.io/lib/soundtrack.js#L326-L352 | |
// however... | |
// if you only have a single string (like youtube), you can do this... | |
var parts = util.parseTitleString( singleString , function(parts) { | |
(That's my attempt to understand what problem Impulse solves and how. I am not a designer/developer of this scheme.)
Regular Bitcoin transactions are not guaranteed until mined sufficiently deep in the blockchain. Unconfirmed transactions can be observed nearly instantly, but they cannot be trusted (could drop out because of insufficient fees, or double-spent).
Impulse Overview
test awesome sauce plug.dj
16:49:08 martindale: oh, you forced that guy to take his video down because you weren‘t making money on the plays? no problem, we’ll just automatically roll everyone‘s playlists over to this other audio source, and your artist’s fans can continue to enjoy the music of the person you're exploiting for commercial benefit.
16:50:13 martindale: and hey, while we‘re at it, we’ll give everyone access to all the different formats and videos for that song… increasing the engagement of that artist and probably getting him more fans.
Each day into the challenge, complete as many burpees as you are days into the challenge, until you reach 100 burpees in a go. Day 1 was 8/16/2013.