SELECT
file.project,
COUNT(*) as total_downloads,
FROM
TABLE_DATE_RANGE(
[the-psf:pypi.downloads],
TIMESTAMP("20160114"),
#!/usr/bin/python | |
approved_UUIDs = ['your-beacon-UUID-here'] # see line 64 | |
path_to_lock_sound = '/Users/frogor/Desktop/car_lock.m4a' | |
path_to_warn_sound = '/Users/frogor/Desktop/viper_warning.m4a' | |
import time | |
import objc | |
from objc import NO | |
from Foundation import NSBundle, NSClassFromString, NSObject, NSRunLoop, NSDate, NSUUID, NSMakeRange, NSURL | |
from AVFoundation import AVAudioPlayer |
from urllib.request import urlopen | |
from urllib.parse import urljoin, unquote_plus | |
import re | |
from random import choice | |
from bs4 import BeautifulSoup | |
BASE_URL = 'https://en.wikipedia.org/' |
The easiest way to get the ClamAV package is using Homebrew
$ brew install clamav
Before trying to start the clamd
process, you'll need a copy of the ClamAV databases.
Create a freshclam.conf
file and configure as so
Install osxfuse
(3.x.x) from https://github.com/osxfuse/osxfuse/releases.
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew update
This post has moved to my personal blog: http://maximilianschmitt.me/posts/istanbul-code-coverage-badge-github/
While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.
Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.
var Stealth = require('../'); | |
var bitcore = require('bitcore') ; | |
var spends = [ | |
new bitcore.PrivateKey(), | |
new bitcore.PrivateKey(), | |
new bitcore.PrivateKey() | |
]; | |
var scanKey = new bitcore.PrivateKey(); |
Normal bitcoin addresses cannot be published in public without losing all privacy, since all transactions to that address can be seen by anybody. Stealth addresses let us publish an address in public which can be used by payers to derive a new address that the payee has access to, but no one else knows is associated with the stealth address. The trick is that the payer must use a nonce to derive the address paid to, and this nonce must be delivered to the payee so they know how to recover the funds. This nonce can be delivered in the transaction, so that no separate channel is required to communicate the nonce.
The same technology can also be used to construct new public keys to send encrypted messages to.
We will discuss four methods:
- The simplest form of stealth addresses, which has some drawbacks that can improved upon.