Severyn Kozak sevko

Getting access token

Enable developer console in browser and navigate to:

https://www.facebook.com/v2.6/dialog/oauth?redirect_uri=fb464891386855067%3A%2F%2Fauthorize%2F&scope=user_birthday%2Cuser_photos%2Cuser_education_history%2Cemail%2Cuser_relationship_details%2Cuser_friends%2Cuser_work_history%2Cuser_likes&response_type=token%2Csigned_request&client_id=464891386855067&ret=login&fallback_redirect_uri=221e1158-f2e9-1452-1a05-8983f99f7d6e&ext=1556057433&hash=Aea6jWwMP_tDMQ9y

Look for the response of POST request in the network tab of developer console: https://www.facebook.com/v2.6/dialog/oauth/confirm?dpr=1 it contains the access token parameter. Just search for 'access_token' in the response. For the lazy people (like myself) i made a small helper that parses the token from response https://taseppa.github.io/tokenparser.github.io/

Getting facebook id

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on

note: always check for the latest versions, the version numbers shown here will fall out of date quickly.

Installing Go on Ubuntu:

Step 1. Grab yourself a binary release from here: https://golang.org/dl/

You'll want to use one from the Stable versions, you probably want one which is in bold, for Ubuntu it's xxx-linux-amd64.tar.gz

wget https://storage.googleapis.com/golang/go1.4.linux-amd64.tar.gz;

compile full Vim

The default Vim installed on most Linux distros lacks a number of vital features, like xterm_clipboard (allows copy-and-pasting to the system clipboard) and python (on which certain plugins rely). The compile_full_vim.sh shell script removes the currently installed Vim and compiles a full-featured version; it's based entirely off Valloric's YouCompleteMe walkthrough, which it bundles into a simple script for convenience. Vim will be compiled with the following feature flags:

--with-features=huge
--enable-multibyte

import quattroshapes into PostgreSQL

The import_quattroshapes_pgsql.sh shell-script will import all Quattroshapes shapefiles into a PostgreSQL database. The process has some gotchas and is generally painful to do manually. Before running the script, ensure that you are logged in as a user with permissions to access/write to PostgreSQL. Then:

bash import_quattroshapes_pgsql.sh

Note that the script will create a Postgres table quattroshapes, and download all Quattroshapes shapefiles into

mkdir pelias

Schema

git clone [email protected]:pelias/schema.git
npm install

install plugin

(if you used homebrew to install elasticsearch it should be /usr/local/Cellar/elasticsearch)

	# Instructions for 4.14 and cuda 9.1
	# If upgrading from 4.13 and cuda 9.0
	$ sudo apt-get purge --auto-remove libcud*
	$ sudo apt-get purge --auto-remove cuda*
	$ sudo apt-get purge --auto-remove nvidia*
	# also remove the container directory direcotory at /usr/local/cuda-9.0/

	# Important libs required with 4.14.x with Cuda 9.X
	$ sudo apt install libelf1 libelf-dev

 import ctypes
 from ctypes import pythonapi as api
 import sys
 from types import (BuiltinFunctionType, GetSetDescriptorType, FrameType,
                    MemberDescriptorType, MethodType)
 import guppy
 from guppy.heapy import Path
 hp = guppy.hpy()

	#include <stdio.h>

	typedef struct point {
	int x, y;
	} point;

	typedef struct point3d {
	struct point;
	int z;
	} point3d;

	#! /bin/bash
	set -e
	trap 'previous_command=$this_command; this_command=$BASH_COMMAND' DEBUG
	trap 'echo FAILED COMMAND: $previous_command' EXIT

	#-------------------------------------------------------------------------------------------
	# This script will download packages for, configure, build and install a GCC cross-compiler.
	# Customize the variables (INSTALL_PATH, TARGET, etc.) to your liking before running.
	# If you get an error and need to resume the script from some point in the middle,
	# just delete/comment the preceding lines before running it again.