flypool

#http://zcash.flypool.org/
#NOTA: último commit de nheqminer: 9b3d9c7

sudo apt-get install qt5-default
git clone https://github.com/etherchain-org/nheqminer.git
cd nheqminer
mkdir build
cd build
qmake ../nheqminer/nheqminer.pro
make

mardlin

/* 
* A simple script for building an authorization redirect URL for your Coinbase Connect app.
* Follow the ##STEPS
*/


/* ##STEP1**: To generate an Authorization URI for a Sandbox App, set this to TRUE
*  Hint: If you're using this script, you probably want to start on the Sandbox
*/
var useSandbox = true;

petertodd

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

This is my standard consulting agreement, drafted by Addison Cameron-Huff
<addison@cameronhuff.com> Feel free to use/distribute this as you see fit.


Consulting Agreement
====================

jorilallo

require "base64"
require 'openssl'
require 'json'

class CoinbaseExchange
    def initialize(key, secret, passphrase)
      @key = key
      @secret = secret
      @passphrase = passphrase
    end

jbinto

### Last tested February 7 2014 on a Galaxy S3 (d2att) running Cyanogenmod 11 nightly, with Google Authenticator 2.49.

### Device with Google Authenticator must have root.
### Computer requires Android Developer Tools and SQLite 3.

### Connect your device in USB debugging mode.

$ cd /tmp
$ adb root
$ adb pull /data/data/com.google.android.apps.authenticator2/databases/databases

vvilp

Installing Arch:


sudo vim /etc/pacman.conf
Update packages list: sudo pacman -Syy
run sudo pacman -Syu  before installing any software (to update the repositories first)

* Timing issue:
    - Change hardware clock to use UTC time:
        sudo timedatectl set-local-rtc 0

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

Tho85

Build your own private, encrypted, open-source Dropbox-esque sync folder

Prerequisites:

• One or more clients running a UNIX-like OS. Examples are given for Ubuntu 12.04 LTS, although all software components are available for other platforms as well (e.g. OS X). YMMV
• A cheap Ubuntu 12.04 VPS with storage. I recommend Backupsy, they offer 250GB storage for $5/month. Ask Google for coupon codes.

Software components used:

• Unison for file synchronization
• EncFS for folder encryption

kxhitiz

Surround:

yss"   - surround whole line with "
ysiw"  - surround a word with "
cs'"   - replace surround - with "
ds"    - delete surround "


Tabs:

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style