If you haven't already, install fail2ban and ufw:
sudo apt-get install fail2ban ufw
Now make a copy of the fail2ban configuration, and name it jail.local
:
import re | |
from collections import namedtuple | |
ASCII_BYTE = " !\"#\$%&\'\(\)\*\+,-\./0123456789:;<=>\?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\[\]\^_`abcdefghijklmnopqrstuvwxyz\{\|\}\\\~\t" | |
String = namedtuple("String", ["s", "offset"]) | |
"""Lanczos interpolation (resampling): 1D. | |
Written by Michael Wood-Vasey | |
based on https://en.wikipedia.org/wiki/Lanczos_resampling | |
""" | |
from __future__ import division, print_function | |
import numpy as np | |
def lanczos_kernel(x, order): |
""" | |
A simple example pyside app that demonstrates dragging and dropping | |
of files onto a GUI. | |
- This app allows dragging and dropping of an image file | |
that this then displayed in the GUI | |
- Alternatively an image can be loaded using the button | |
- This app includes a workaround for using pyside for dragging and dropping |
curl -k -g -X POST -d "payload={\"text\":\"my important bot notification\", \"channel\":\"#monitoring\", \"username\":\"computer-bot\", \"icon_emoji\":\":computer:\"}" https://hooks.slack.com/services/XXXXXXXXX/XXXXXXXXX/XxXxXxXxXXXxxXXXxxx |
<? | |
///////////////////// | |
// slack2html | |
// by @levelsio | |
///////////////////// | |
// | |
///////////////////// | |
// WHAT DOES THIS DO? | |
///////////////////// | |
// |
Info: | See <http://docutils.sf.net/rst.html> for introductory docs. |
---|---|
Author: | David Goodger <[email protected]> |
Date: | 2013-02-20 |
Revision: | 7612 |
Description: | This is a "docinfo block", or bibliographic field list |
Note
If you are reading this as HTML, please read
#ifndef NOISE_SIMPLEX_FUNC | |
#define NOISE_SIMPLEX_FUNC | |
/* | |
Description: | |
Array- and textureless CgFx/HLSL 2D, 3D and 4D simplex noise functions. | |
a.k.a. simplified and optimized Perlin noise. | |
The functions have very good performance | |
and no dependencies on external data. |
Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.
For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.
But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.
SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil