Allows access to the CJDNS Admin API via a GUI. Should be kept in a private, password protected location.
| " ========================================================== | |
| " Vundle | |
| " ========================================================== | |
| set nocompatible | |
| filetype off | |
| set rtp+=~/.vim/bundle/vundle/ | |
| call vundle#rc() | |
| " let Vundle manage Vundle |
| // http://jsfiddle.net/suBPQ/ | |
| $.ajax({ | |
| url: "http://api_test_server.proudlygeek.c9.io/", | |
| success: function(data) { | |
| console.log(data); | |
| } | |
| }); |
| 13:25 deberg: [17:21:57] hey, i just saw your question. | |
| 13:25 eiki: [17:22:17] great - any ideas? | |
| 13:25 deberg: [17:22:19] the thing to use is futures. | |
| 13:25 eiki: [17:22:36] what's the difference? | |
| 13:25 eiki: [17:22:45] and do you know of any sample code? | |
| 13:25 deberg: [17:23:02] yeah, one place to look is the meteor HTTP package. | |
| 13:25 deberg: [17:23:11] packages/http/httpcall_server.js:64 | |
| 13:25 deberg: [17:23:39] this is the basic pattern for wrapping a node callback. | |
| 13:25 eiki: [17:24:09] https://github.com/meteor/meteor/blob/master/packages/http/httpcall_server.js#L65 | |
| 13:25 deberg: [17:24:35] you want to declare a new future, call future.return() inside the callback, and block the outer caller (your method) with future.wait(). |
| /* | |
| * async_nif: An async thread-pool layer for Erlang's NIF API | |
| * | |
| * Copyright (c) 2012 Basho Technologies, Inc. All Rights Reserved. | |
| * Author: Gregory Burd <[email protected]> <[email protected]> | |
| * | |
| * This file is provided to you under the Apache License, Version 2.0 (the | |
| * "License"); you may not use this file except in compliance with the License. | |
| * You may obtain a copy of the License at: | |
| * |
#Introduction
Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.
Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.
| #!/bin/bash | |
| # From http://tech.serbinn.net/2010/shell-script-to-create-ramdisk-on-mac-os-x/ | |
| # | |
| ARGS=2 | |
| E_BADARGS=99 | |
| if [ $# -ne $ARGS ] # correct number of arguments to the script; | |
| then |
Thumbnail sketch: Two-factor (Yubikey or Google Authenticator) protected wallets
Hardware:
Computer. Shared-secret authenticator (Yubikey/Google Authenticator/etc). Server (possibly shared with millions of other users).
Motivating use case setup:
User creates a split (2-of-2 multisig) wallet on the computer and server. Keys must be securely backed up to protect against loss. GUI to be determined, but there will be some type of "Use Authenticator" checkbox specified at setup.
| --enable-optimized | |
| --disable-polly | |
| --disable-clang-arcmt | |
| --disable-clang-static-analyzer | |
| --disable-clang-rewriter | |
| --disable-assertions | |
| --disable-debug-symbols | |
| --disable-jit | |
| --disable-docs | |
| --disable-threads |
| sudo apt-get update | |
| # get ec2 ip and hostname | |
| curl http://169.254.169.254/latest/meta-data/public-ipv4 > public.ip | |
| curl http://169.254.169.254/latest/meta-data/public-hostname > public.hostname | |
| sudo apt-get install --yes build-essential curl git | |
| #install latest node | |
| sudo apt-get install --yes python-software-properties python g++ make | |
| sudo add-apt-repository --yes ppa:chris-lea/node.js | |
| sudo apt-get update |