generate key in batch mode using a custom profile
gpg --gen-key --batch gpgspecs
create a file with your fingerprint info and display the related information. A fingerprint is used as a robust key identifier
gpg --fingerprint
-- mpv script to download subtitles using subdl. | |
-- requires subdl (2016 Sep master branch): https://github.com/alexanderwink/subdl | |
-- default keybinding: B (capital B) | |
-- add the following to your input.conf to change the default keybinding: | |
-- keyname script_binding subdl_load_subs | |
local utils = require 'mp.utils' | |
function subdl_load() |
Vagrant.configure("2") do |config| | |
config.vm.define "default" do |default| | |
default.vm.hostname = "unisonbuild" | |
default.vm.provider "lxc" | |
default.vm.box = "zeitonline/bionic64-lxc" | |
# default.vm.box = "bento/ubuntu-18.04" | |
end | |
end |
Scalr | |
http://highscalability.com/blog/2010/3/22/7-secrets-to-successfully-scaling-with-scalr-on-amazon-by-se.html | |
http://stackoverflow.com/questions/10061843/how-to-convert-linux-cron-jobs-to-the-amazon-way | |
Cron Jobs Are Hard To Distribute | |
Watch out when scaling out instances with cron jobs on them. Cron jobs aren't designed for the cloud. If the machine image holding your cron job scales out to 20 instances, your cron job will be executed 20 times more often. | |
This is fine if the scope of your cron job is limited to the instance itself, but if the scope is larger, the above becomes a serious problem. And if you single out a machine to run those cron jobs, you run the risk of not having it executed if that machine goes down. |
#!/usr/bin/env python | |
import json | |
PRODUCT_PATH = "/usr/lib/code/product.json" | |
official_gallery = { | |
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery", | |
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index", | |
"itemUrl": "https://marketplace.visualstudio.com/items", |
#!/bin/bash | |
# bash generate random alphanumeric string | |
# | |
# bash generate random 32 character alphanumeric string (upper and lowercase) and | |
NEW_UUID=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) | |
# bash generate random 32 character alphanumeric string (lowercase only) | |
cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1 |
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | |
<!-- | |
Noto Mono + Color Emoji Font Configuration. | |
Currently the only Terminal Emulator I'm aware that supports colour fonts is Konsole. | |
Usage: | |
0. Ensure that the Noto fonts are installed on your machine. | |
1. Install this file to ~/.config/fontconfig/conf.d/99-noto-mono-color-emoji.conf |
There is an increasing count of applications which use Authy for two-factor authentication. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords.
Since I use 1Password for all of my password storing/generating needs, I was looking for a solution to use Authy passwords on that. I couldn't find any completely working solutions, however I stumbled upon a gist by Brian Hartvigsen. His post had a neat code with it to generate QR codes for you to use on your favorite authenticator.
His method is to extract the secret keys using Authy's Google Chrome app via Developer Tools. If this was not possible, I guess people would be reverse engineering the Android app or something like that. But when I tried that code, nothing appeared on the screen. My guess is that Brian used the