If you don’t want fields such as “[Online]”, “Available: …” appear in IEEEtran bibliography items:

1. Go to installation folder of IEEEtan bst.
(on my Mac OS with Texlive, the folder is /usr/local/texlive/2016/texmf-dist/bibtex/bst/IEEEtran)

2. Backup and then edit IEEEtran.bst, search “FUNCTION XXX” (XXX could be “inproceedings”, “inbook”, etc.), and comment out “format.url output”

3. run “texhash”

4. recompile .bib and .tex files.

Reference:https://tex.stackexchange.com/questions/45160/remove-url-in-ieeetran-bibliography

Reference: https://www.tensorflow.org/versions/r0.10/api_docs/python/nn/activation_functions_

1. Smooth nonlinearities:
(tf.nn.)sigmoid, tanh, elu, softplus, softsign

2. Continuous but not everywhere differentiable:
(tf.nn.)relu, relu6

3. Random regularization:
(tf.nn.)dropout

e.g. for tf.contrib.learn.DNNClassifier, the default activation function in __init__ is relu:

__init__( ..., activation_fn=tf.nn.relu, ...)

Reference: https://www.tensorflow.org/get_started/get_started

1. Multiple level APIs:
(1) lowest level: TensorFlow Core, if you need fine controls on the model
(2) higher levels: built on Core, easier to use, e.g. tf.contrib.learn

2. Tensor: an array of primitive values. Rank: how many dimensions. Shape: a vector, containing the numbers of elements in each dimension.
e.g. [[[1., 2., 3.]], [[7., 8., 9.]]] has rank 3, shape [2,1,3]

3. Import library

import tensorflow as tf

Continue reading

If there is “Error connecting to database” error, and the access.log file is huge (several GB), and there are many “POST /xmlrpc.php” or “POST /wp-login.php” in it, it’s brute force attack.

How to stop it?

I. Use password to protect wp-login.php

1. Generate file ./htpasswd, e.g. use http://www.htaccesstools.com/htpasswd-generator/, put it in folder (e.g. /var/www)
Note: could use the following command to generate random password first

openssl rand -base64 6

2. Add the following code in .htaccess under where the wp-login.php is (usually the root folder of WordPress installation)

# Stop Apache from serving .ht* files
<Files ~ "^\.ht">
Order allow,deny
Deny from all
</Files>

# Protect wp-login
<Files wp-login.php>
AuthUserFile [ABSOLUTE PATH]/.htpasswd
AuthName "Private access"
AuthType Basic
require user USERNAME-SET-IN-HTPASSWD
</Files>

Reference: Brute Force Attacks on WordPress.org

II. Stop access to xmlrpc.php

If xmlrpc is not used, just block access to it. In .htaccess file, add

<Files xmlrpc.php>
order deny,allow
deny from all
</Files>

The following steps work on Ubuntu 16.04.

1. Get source from https://github.com/guardianproject/Orfox.git

2. Install Android SDK 23, SDK Build-tools 23.0.1, Android Support Repository

3. Export ANDROID_HOME, ANDROID_NDK_HOME

4. In root folder, execute (note: if need to build modified code, first comment out the git part)

./make_build_release

5. If error “Could not find autoconf 2.13”, install autoconf-2.13 from source. e.g. on Ubuntu 16.04:

wget http://ftp.gnu.org/gnu/autoconf/autoconf-2.13.tar.gz
tar -xvzf autoconf-2.13.tar.gz
cd autoconf-2.13/
./configure --program-suffix=2.13
make
sudo make install'

6. If error “ccache not found”,

apt-get install ccache

Note: FIRST read this thread on XDA to determine which boot-to-root to download. As of today (2017-01-24), I used v2.78 SR3 for non-TWRP.

1. In Developer options, enable OEM unlocking

2. Unlock bootloader (this only works on Pixel directly bought from Google, not carrier versions):
(a) boot into bootloader mode:

adb reboot bootloader

(b)

fastboot flashing unlock

then confirm on phone

3. Download boot-to-root image from Chainfire (read this thread on XDA to determine the download version), then

fastboot boot boot-to-root.img

Note: after root, if Pixel is stuck in the booting process (e.g. because wrong version of boot-to-root.img is used), flash the factory boot.img from Google (fastboot flash boot boot.img), normal reboot, and repeat Step 3 above.

1. https://git.torproject.org/orbot.git
(In Eclipse, Import Projects from Git -> select “Clone submodules” -> Import as general project)

2. Install automake, libtool

3. Export ANDOIR_NDK_HOME and ANDROID_HOME, then

export PATH=$ANDROID_HOME/tools:$PATH

4. In Android SDK manager, install SDK Platform API 23 Rev.3, and Extras -> Android Support Repository

5. In orbotservices/src/main, run

ndk-build

Otherwise there is error: “orbotservices/src/main/libs/armeabi/pdnsd” not found

6. In Orbot root directory, run

make -C external

7. Verify tor and polipo binaries

file external/bin/tor external/bin/polipo

8. In Orbot root diretory, build a debug APK (assuming target is Android 6.0)

android update project --name Orbot --target android-23 --path .
./gradlew assembleDebug

the APK is in app/build/outputs/apk/