| version: "3" | |
| networks: | |
| web: | |
| external: true | |
| internal: | |
| external: false | |
| services: | |
| blog: |
*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August
This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
| #! /bin/bash | |
| # Make a directory to hold local libs and bins | |
| mkdir -p ~/usr/local | |
| # Get protobuf | |
| wget https://protobuf.googlecode.com/files/protobuf-2.5.0.tar.gz | |
| # Extract protobuf | |
| tar -xvzf protobuf-2.5.0.tar.gz | |
| cd protobuf-2.5.0 |
| (ns sudoku | |
| (:refer-clojure :exclude [==]) | |
| (:use [clojure.core.logic]) | |
| (:require [clojure.core.logic.fd :as fd])) | |
| (defn init-board [vars puzzle] | |
| (matche [vars puzzle] | |
| ([[] []] | |
| succeed) |
| So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
| Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
| * Off the top of my head * | |
| 1. Fork their repo on Github | |
| 2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
| git remote add my-fork git@github...my-fork.git |