Andrei Jiroh Halili ajhalili2006

First, logged in the Cloudflare Dashboard, and go to User Profile, choice API Tokens, generated API Token.

Then, once successfully generated, the token secret is only shown once. Make sure to copy the secret to a secure place. Replace the "API Token" at auth_key.

import json
import requests

cloudflare_verify = "https://api.cloudflare.com/client/v4/user/tokens/verify"
auth_key = "API Token"

How to create a Keybase bot and run arbitrary things, as the bot, from a shell.

Before you begin:

Requires: Docker, access to Docker Hub, existing Keybase account.

To make sure those things are ready:

docker pull keybaseio/client:stable-node

keybase whoami

Keybase proof

I hereby claim:

I am ajhalili2006 on github.
I am ajhalilidev06 (https://keybase.io/ajhalilidev06) on keybase.
I have a public key ASBCy4KerdCaXCSFZpzJNB2i665yhaKyOelNx6nVqwXXego

To claim this, I am signing this object:

Notice! This documentation is outdated & will no longer be updated.

We've recently moved to https://docs.intellivoid.net/openblu/introduction

OpenBlu API V1-IVA2.0

This document explains how to use the OpenBlu API to retrieve OpenBlu servers, filter them and retrieve their OpenVPN configuration details

Authenticate

OpenBlu API uses Intellivoid API, to learn how to

Deploy the source code is not harder as you think. In fact there are some ways to deploy it. Read on to learn more about how you deploy an app to make things working. In this tutorial, we use MadeByThePinsTeamHub/mwbot-official as am example during this tutorial.

What you need

Git CLI, Node.js and NPM (pre-installed, but you can update it)
A service to deploy code (e.g. Glitch)

Type	Emoji	code
feat	✨	`:sparkles:`
fix	🐛	`:bug:`
docs	📚	`:books:`
style	💎	`:gem:`
refactor	🔨	`:hammer:`
perf	🚀	`:rocket:`
test	🚨	`:rotating_light:`
build	📦	`:package:`

	KUTT_HOST="https://kutt.it"
	KUTT_API_KEY="API_KEY"
	kutt() {
	if [[ "$1" == "delete" ]] && [[ -n "$2" ]]; then
	curl -s -H "X-API-KEY: $KUTT_API_KEY" \
	-X DELETE \
	"$KUTT_HOST/api/v2/links/$2" \| jq
	elif [[ -z "$1" ]]; then
	curl -s -H "X-API-KEY: $KUTT_API_KEY" \
	"$KUTT_HOST/api/v2/links" \| jq

	* it was a mistake to let npm, inc. get as far as it did with what should have always been a part of the foundation (post Joyent).
	* The CLI isn't the interesting part – the registry contains the value & needs to be safeguarded.
	* I really strongly dislike Facebook and don't trust anyone that takes a paycheck or benefits at all from that brand. NPM is know to not be well managed but I really don't like Facebook.
	* "Dear God please don't ship Yarn by default. Not only are the maintainers unpleasant to interact with, the whole thing is just... bad.
	* Most of the time fixing Yarn issues comes down to: ""Can you try npm instead?"". Making that a default experience would be a catastrophy."
	* I am more concerned about the stability of the npm package management repo than necessarily npm vs yarn.
	* I remember when node didn't come with a package manager, it was pretty bad
	* the problem is not the package manager, it’s the registry. Currently the registry is not owned the foundation. no matter what the client is, we

	//
	// Author: Jonathan Blow
	// Version: 1
	// Date: 31 August, 2018
	//
	// This code is released under the MIT license, which you can find at
	//
	// https://opensource.org/licenses/MIT
	//
	//

	Since 2013 I've worked entirely in the open, lowering the barriers to different
	developer ecosystems as one of the most active users on GitHub.
	I've helped big OSS projects with design, project management and occasionally code.