Skip to content

Instantly share code, notes, and snippets.

// Simple debug output helper
function debug(message) {
Ti.API.info(message);
}
/**
*
* @param thisControl The control you wish to dump
* @param goDeep boolean Do you want deep introspection
* @param incFuncs boolean Do you want to include functions in the output when going deep
@dasher
dasher / litecoin.conf
Created December 22, 2012 18:13
example litecoin.conf
# litecoin.conf configuration file. Lines beginning with # are comments.
# Network-related settings:
# Run on the test network instead of the real litecoin network.
#testnet=0
# Connect via a socks4 proxy
#proxy=127.0.0.1:9050
@dasher
dasher / gist:4391953
Last active June 12, 2018 08:17
Litecoin Supernodes
"83.169.3.31"
"82.226.138.81"
"93.62.173.122"
"94.23.253.228"
"91.121.174.223"
"188.120.246.137"
"12.23.127.175"
"99.243.145.178"
"79.142.22.72"
"198.23.159.10"
var txId = "TheTXIdGoesHere";
$.getJSON('http://blockchain.info/tx-index/'+txId+'?format=json',
function(data) {
console.log(JSON.stringify(data));
}
);
@dasher
dasher / test.js
Last active December 17, 2015 19:09
Nested Policy Support Allows a policySet to be created that depends on a number of factors - in the current state this allows the path & the controller::action to define the policy set - it also allows the target of the policy to be either the policy file (the existing sails policy system) or a controller::action
'use strict';
var _ = require('lodash');
_.string = require("underscore.string");
// enhance the console a little
require("consoleplusplus");
// Timestamps not needed
console.disableTimestamp();
// Mock
// Relic integration point
/**
* Create a transactional scope in which instrumentation that will only add
* trace segments to existing transactions will funciton.
*
* @param Agent agent The agent whose tracer should be used to create the
* transaction.
* @param Function callback The function to be run within the transaction.
*/
"vectors" : "1",
"worksize" : "256",
"kernel" : "scrypt",
"lookup-gap" : "2",
"thread-concurrency" : "24576",
"shaders" : "1792",
"gpu-threads" : "1",
"scan-time" : "60",
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1
aticonfig --od-enable
aticonfig --od-setclocks=1000,1490 --adapter=0
./bfgminer -K ./
Getting started
With node installed (download), get your first application started by creating a directory somewhere on your machine:
$ mkdir hello-world
$ cd hello-word
$ git init
In this same directory you'll be defining the application "package", which are no different than any other node package. You'll need a package.json file in the directory, with express defined as a dependency. You may use npm info express version to fetch the latest version, it's preferred that you do this instead of "3.x" below to prevent any future surprises.
{
"name": "hello-world",
@dasher
dasher / snippet.js
Last active December 10, 2015 01:34
snippet: Loading modules using the compoundJS "after extensions" event trigger. Logging is verbose but filtered by the logging wrapper methods - so you can turn up/down the amount of info with a config setting
// This code expects both app & compound to resolve to the appropriate variables
if (app.get("userModulesEnabled")) {
var userModules = []; // To allow access later
// Attach to the framework event
compound.on("after extensions",
function(){
// Load - currently nothing passed by the framework
// we attach our log handler to the compound tools object - so it's available to console based apps
// compound.tools.winston is the logger instance