metashx

/*
This script is designed to allow smart accounts to log into websites that require a
signature. It will automatically (without prompting the user) accept a WalletConnect
session for the provided URI and sign the incoming personal_sign request to pass the
log in step on https://app.liquifi.finance/. It should realistically work on any
website that requires a signature to log in.

Dependencies:
1. Copy the package.json into a folder alongside this script.

scryptonite

1. Modify & run dump-sequelize-schema.js.
   • It currently uses a few lodash methods, so be sure to temporarily install them—or if you feel up to it you can rewrite the script so they're not needed.
   • npm i lodash.sortby lodash.pick lodash.omit lodash.mapvalues
2. Inspect sequelize-schema.json and make sure it appears represent all of your tables, attributes, indexes, constraints, references, etc...
3. When you are satisfied, copy and rename sequelize-schema.json file into a migration-extras/ directory that is next to your migrations/. Name it initial-sequelize-schema.json.
   • migration-extras/
     • -> initial-sequelize-schema.json
   • migrations/
     • (this folder should probably be empty)
4. Run sequelize migration:create and then copy the contents of 2018XXXXXXXXXX-initial-migration.js into the newly generated migration script. No additional modifications are required if y

hnvn

import 'package:flutter/material.dart';
import 'dart:math' as math;
import 'dart:async';

void main() => runApp(new MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {

wesbos

{
  "window.zoomLevel": -1,
  "editor.fontFamily": "Operator Mono, Menlo, Monaco, 'Courier New', monospace",
  "editor.fontSize": 29,
  "editor.lineHeight": 40,
  "editor.letterSpacing": 0.5,
  "workbench.editor.tabSizing": "shrink",
  "eslint.autoFixOnSave": true,
  "eslint.alwaysShowStatus": true,
  "html.format.enable": true,

dropmeaword

Browser histories

Unless you are using Safari on OSX, most browsers will have some kind of free plugin that you can use to export the browser's history. So that's probably the easiest way. The harder way, which seems to be what Safari wants is a bit more hacky but it will also work for other browsers. Turns out that most of them, including Safari, have their history saved in some kind of sqlite database file somewhere in your home directory.

The OSX Finder cheats a little bit and doesn't show us all the files that actually exist on our drive. It tries to protect us from ourselves by hiding some system and application-specific files. You can work around this by either using the terminal (my preferred method) or by using the Cmd+Shft+G in Finder.

Once you locate the file containing the browser's history, copy it to make a backup just in case we screw up.

cvrebert

Test apparatus: http://jsfiddle.net/hRub4/

(Windows = Windows 8.1 desktop)

• Windows Chrome 39
  • Button focuses on click and via keyboard tabbing
  • Anchor focuses on click and via keyboard tabbing
• Windows Firefox 30.0
  • Button focuses on click and via keyboard tabbing
  • Anchor focuses on click and via keyboard tabbing
• Windows Internet Explorer 11