Chanda Mulenga stctheproducer

Generating Authy passwords on other authenticators

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

Never touch your local /etc/hosts file in OS X again

To setup your computer to work with *.test domains, e.g. project.test, awesome.test and so on, without having to add to your hosts file each time.

Requirements

Homebrew
Mountain Lion -> High Sierra

Install

Import Keybase PGP to GPG

After installing the keybase command-line tool onto a new / fresh computer, you may want to import your PGP key to the local keyring so that you may use the keys with GPG.

Import your PUBLIC PGP key:

keybase pgp export|gpg --import -

This abstract Mapper class provides a flexible and type-safe way to serialize, transform, and label AdonisJS Lucid models and their paginated results. It is designed to help you build clean API responses and DTOs in AdonisJS projects.

Features

Supports serialization of single models, arrays, and paginated results.
Custom serialization logic via subclassing.
Utility for picking specific fields and relations from models.
Label mapping mechanism for enums or field names.

Use this utility to keep your API layer clean, consistent, and maintainable when working with AdonisJS and Lucid ORM.

	#!/usr/bin/env node

	var fs = require('fs');
	var path = require('path');
	var request = require('request');

	var CERTDB_URL =
	'https://mxr.mozilla.org/nss/source/lib/ckfw/builtins/certdata.txt?raw=1';

	var OUTFILE = './certificates.js';

	# Windsurf Memory Bank

	I am Windsurf, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.

	## Memory Bank Structure

	The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:

	```mermaid
	flowchart TD

	import { options } from "preact";
	import { Signal } from "@preact/signals";

	// Add `bind:value` to JSX types
	declare global {
	namespace preact.createElement.JSX {
	interface HTMLAttributes {
	"bind:value"?: Signal<string \| string[] \| number \| undefined>;
	}
	}