1a57danc3

var cv = document.getElementById('cv');
var c = cv.getContext('2d');
var txtDiv = document.getElementById('txt');
var fileBtn = document.getElementById("up-button");
var img = new Image();
img.src = 'a.jpg';
img.onload = init; // 图片加载完开始转换
fileBtn.onchange = getImg;

// 根据灰度生成相应字符

1a57danc3

# /etc/nginx/sites-available/fanfou.shellex.info
# 这儿假设的域名是 fanfou.shellex.info
# 请替换为实际的域名

server {
  resolver 8.8.8.8;
  listen 443;
  server_name fanfou.shellex.info;

  ssl on;

1a57danc3

#! /usr/bin/env python
# -*- coding: utf-8 -*-

import subprocess
import re

ntfs_pattern = re.compile(r'File System Personality:  NTFS')
ntfs_device_node = re.compile(r'.*Device Node:.*')
device_dict = {}

1a57danc3

[Proxy]
WIFI = direct, interface=en2
VPN = direct, interface=utun0

[Rule]
DOMAIN-SUFFIX,yach.me,WIFI
FINAL,VPN

1a57danc3

good, 你已经有了一个自己的shadowsocks代理了，现在想要把这个代理公布出去给所有人分享。
但是没有两个小时，代理就没法使用了，为什么？因为你需要额外注意以下事项（以下步骤需要比较高的linux技能）
本文只关注于确保shadowsocks服务还“活着”，如果你希望让其跑得更快，请参考 
https://github.com/clowwindy/shadowsocks/wiki/Optimizing-Shadowsocks

1、 shadowsocks的timeout设置
超时时间越长，连接被保持得也就越长，导致并发的tcp的连接数也就越多。对于公共代理，这个值应该调整得小一些。推荐60秒。

2、 检查操作系统的各种限制
对于openvz的vps，特别需要检查一下

1a57danc3

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.

Solution

This solution fixes the error caused by trying to run npm update npm -g. Once you're finished, you also won't need to use sudo to install npm modules globally.

Before you start, make a note of any globally installed npm packages. These instructions will have you remove all of those packages. After you're finished you'll need to re-install them.

1a57danc3

#!/bin/sh

#delay 30 minute
delay=-v-30M
#image location
location=$HOME/Pictures/himawari8

date=$(date -u $delay "+%Y/%m/%d")
file_name=$(date -u $delay "+%H")$(echo "($(date -u $delay "+%M"))/10 * 10" | bc)"00_0_0.png"
url=http://himawari8-dl.nict.go.jp/himawari8/img/D531106/1d/550/$date/$file_name

1a57danc3

When setting up (that's immediately when user enables it in settings) Opera VPN sends few API requests to https://api.surfeasy.com to obtain credentials and proxy IPs, see below, also see The Oprah Proxy.

The browser then talks to a proxy de0.opera-proxy.net (when VPN location is set to Germany), it's IP address can only be resolved from within Opera when VPN is on, it's 185.108.219.42 (or similar, see below). It's an HTTP/S proxy which requires auth.

When loading a page with Opera VPN enabled, the browser sends a lot of requests to de0.opera-proxy.net with Proxy-Authorization request header.

The Proxy-Authorization header decoded: CC68FE24C34B5B2414FB1DC116342EADA7D5C46B:9B9BE3FAE674A33D1820315F4CC94372926C8210B6AEC0B662EC7CAD611D86A3 (that's sha1(device_id):device_password, where device_id and device_password come from the POST /v2/register_device API call, please note that this decoded header is from another Opera installation and thus contains

1a57danc3

@-moz-document domain("baidu.com") {
body {
     display: none;
}

html {
     margin: 30px;
}

html::after {

1a57danc3

Result: 1
Items {
  TemplateId: "BADGE_BATTLE_ATTACK_WON"
  Badge {
    BadgeType: BADGE_BATTLE_ATTACK_WON
    BadgeRanks: 4
    Targets: "\nd\350\007"
  }
}
Items {