davidgilbertson

const http2 = require('http2');
const fs = require('fs');
const path = require('path');
const zlib = require('zlib');
const brotli = require('brotli'); // npm package

const PORT = 3032;
const BROTLI_QUALITY = 11; // slow, but we're caching so who cares
const STATIC_DIRECTORY = path.resolve(__dirname, '../dist/');
const cache = {};

est31

Trying to deploy WPA3 on my home network

Introduction

Recently, news broke about a new possible offline attack on WPA2 using PMKID. To summarize the attack, WPA2 protected APs can end up broadcasting PMKID values which can then be used to offline-brute-force the password.

These PMKID values are computed this way:

PMKID = HMAC-SHA1-128(PMK, "PMK Name" | MAC_AP | MAC_STA)

pavanjadhaw

# Default terminal
set-option -g default-terminal "screen-256color"

# Use vim key bindings
set-option -g mode-keys vi
set-option -g status-keys vi

# Turn the mouse on
set-option -g mouse on

VictorTaelin

async/await is just the do-notation of the Promise monad

CertSimple just wrote a blog post arguing ES2017's async/await was the best thing to happen with JavaScript. I wholeheartedly agree.

In short, one of the (few?) good things about JavaScript used to be how well it handled asynchronous requests. This was mostly thanks to its Scheme-inherited implementation of functions and closures. That, though, was also one of its worst faults, because it led to the "callback hell", an seemingly unavoidable pattern that made highly asynchronous JS code almost unreadable. Many solutions attempted to solve that, but most failed. Promises almost did it, but failed too. Finally, async/await is here and, combined with Promises, it solves the problem for good. On this post, I'll explain why that is the case and trace a link between promises, async/await, the do-notation and monads.

First, let's illustrate the 3 styles by implementing

bvaughn

React lifecycle cheatsheet

Method	Side effects1	State updates2	Example uses
Mounting
componentWillMount		✓	Constructor equivalent for createClass
render			Create and return element(s)
componentDidMount	✓	✓	DOM manipulations, network requests, etc.
Updating
componentWillReceiveProps		✓	Update state based on changed props

drahosistvan

#!/bin/bash

if [ -z "$1" ]
  then
    echo "Please specify a folder"
    exit
fi

if [ -z "$2" ]
  then

eyecatchup

git commit stats

Commands to get commit statistics for a Git repository from the command line -
using git log, git shortlog and friends.

---

zeroseis

• Close Android File Transfer
• Open Activity Monitor and kill “Android File Transfer Agent”
• Go to where you installed “Android File Transfer.app” (I have it under /Applications)
• Ctrl+click –> “Show package contents”
• Go to Contents/Resources
• Rename “Android File Transfer Agent” to e.g. “Android File Transfer Agent_DISABLED”
• Then go to “/Users/username/Library/Application Support/Google/Android File Transfer” and again rename the Agent app.

ilyaigpetrov

Comparison of ASP.NET and Node.js for Backend Programming

We will compare ASP.NET and Node.js for backend programming.
Source codes from examples.

Updates

This document was published on 21.09.2015 for a freelance employer. Some changes since then (14.02.2016):

1. Koa.js no longer uses co-routines, it has switched to Babel's async/await. yield and await are used almost in the same way, so I see no point to rewrite the examples.

stav

""" pipelines.py """
import collections
import scrapy
import scrapy.contrib.exporter
import myproject


class SitemapPipeline(object):
    """
    Sitemap builder