/* Using a JavaScript proxy for a super low code REST client */ | |
// via https://dev.to/dipsaus9/javascript-lets-create-aproxy-19hg | |
// also see https://towardsdatascience.com/why-to-use-javascript-proxy-5cdc69d943e3 | |
// also see https://github.com/fastify/manifetch | |
// also see https://github.com/flash-oss/allserver | |
// and https://gist.github.com/v1vendi/75d5e5dad7a2d1ef3fcb48234e4528cb | |
const createApi = (url) => { | |
return new Proxy({}, { | |
get(target, key) { |
-- See: https://en.wikipedia.org/wiki/Linear_congruential_generator | |
-- See: https://en.wikipedia.org/wiki/Lehmer_random_number_generator | |
-- Original Lehmer RNG construction | |
local m = 65537 -- (2 ^ 16) + 1, a fermat prime | |
local a = 75 -- a primitive root modulo | |
local x0 = 65536 -- a seed number, greater than '0', less than 'm' | |
local md = m - 1 -- a floating-point devider | |
-- Lehmer random number generator formula | |
local function rng(x) |
Primeiro, verifique se o módulo está presente na sua instalação digitando pacmd
em seu terminal, listando todos os módulos presentes pelo comando list-modules
e procurando por module-echo-cancel
. Não está presente? Você precisa adicionar algumas linhas ao arquivo de texto responsável pela configuração do PulseAudio.
Com o seu editor favorito, abra (com privilégios de administrador) o arquivo /etc/pulse/default.pa
e adicione as seguintes linhas ao fim do arquivo:
### Enable Echo/Noise-Cancellation
load-module module-echo-cancel use_master_format=1 aec_method=webrtc aec_args="analog_gain_control=0\ digital_gain_control=1" source_name=echoCancel_source sink_name=echoCancel_sink
set-default-source echoCancel_source
set-default-sink echoCancel_sink
#include <time.h> // Robert Nystrom | |
#include <stdio.h> // @munificentbob | |
#include <stdlib.h> // for Ginny | |
#define r return // 2008-2019 | |
#define l(a, b, c, d) for (i y=a;y\ | |
<b; y++) for (int x = c; x < d; x++) | |
typedef int i;const i H=40;const i W | |
=80;i m[40][80];i g(i x){r rand()%x; | |
}void cave(i s){i w=g(10)+5;i h=g(6) | |
+3;i t=g(W-w-2)+1;i u=g(H-h-2)+1;l(u |
from | to | description |
---|---|---|
0 | 10,000 | System items (including junkyards and other special purpose items |
500,000 | 1,000,000 | Factions |
1,000,000 | 2,000,000 | NPC corporations |
3,000,000 | 4,000,000 | NPC characters (agents and NPC corporation CEO's) |
9,000,000 | 10,000,000 | Universes |
10,000,000 | 11,000,000 | NEW-EDEN Regions |
11,000,000 | 12,000,000 | Wormhole Regions |
12,000,000 | 13,000,000 | Abyssal regions |
int doubler(int x) { | |
return 2 * x; | |
} |
aliases({ | |
bundle : { command: ["bundle", "exec"]}, // system: azkdemo (default) | |
scaffold : { alias: "bundle", append: ["rails", "g", "scaffold"]}, | |
test : { alias: "bundle", append: ["rake", "test"], tty: true, context: 'test'}, | |
'import-db': { system: "mysql", command: ["mysql"], depends: false} | |
}); | |
// azk script generator --path ./script | |
// ./script/bundle | |
// ./script/scaffold |
As many of you know I have been on a quest to get Jetpack core development moved from the WordPress.org Subversion (svn) repository to Github (git). As part of this process I setup an experimental Jetpack repository to see how synchronization works between git and svn. Lets just clear the air right now and say not well, not well at all. This is due to how git and svn each store their respective histories. But! I think I finally have it figure out.
I wrote an article a couple months ago entitled Creating a synchronized Github fork of a WordPress.org Subversion plugin repository. This article is great (and still a recommended read) if you are only doing synchronization b
/** | |
* Mac Users: | |
* Add a file /etc/rsolver/my.domain.com | |
* nameserver [ip from dev.azk.io] | |
* port 5353 | |
* | |
* Linux Users: | |
* Add a file /etc/rsolver/my.domain.com | |
* nameserver [ip from dev.azk.io]:5353 | |
* |