This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
import praw # simple interface to the reddit API, also handles rate limiting of requests | |
import re | |
from collections import deque | |
from time import sleep | |
USERNAME = "Your username here" | |
PASSWORD = "Your password here" | |
USERAGENT = "Your useragent string here. It should include your /u/username as a courtesy to reddit" | |
r = praw.Reddit(USERAGENT) |
This information source from the following url:
http://peter.sh/experiments/chromium-command-line-switches/
And also in the chromium source:
https://source.chromium.org/chromium/chromium/src/+/main:media/base/media_switches.cc
/**************************************************************** | |
* Sudoku Solver | |
* | |
* Translated into Javascript from original code in C++ | |
* by Lee Hsien Loong | |
* The MIT License (MIT) | |
* Copyright (c) 2015 Vivian Balakrishnan | |
* | |
* | |
****************************************************************/ |
Edward Snowden answered questions after a showing of CITIZENFOUR at the IETF93 meeting; this is a transcript of the video recording.
For more information, see the Internet Society article.
Before we start with creating a custom OAuth2 connection in Auth0, it's worth to spend some time understanding the OAuth2 authentication process in Auth0. An OAuth2 authentication process starts with the application requesting Auth0 for authentication and ends with either the browser or the application server having an access token to represent the user. The access token can then be used to call the third party API on behalf of the user.
Redirect mode
npm users sorted by the monthly downloads of their modules, for the range May 6, 2018 until Jun 6, 2018.
Metrics are calculated using top-npm-users.
# | User | Downloads |
---|
export {} | |
if (typeof Array.prototype.flatMap !== 'function') { | |
// eslint-disable-next-line no-extend-native | |
Object.defineProperty(Array.prototype, 'flatMap', { | |
enumerable: false, | |
// https://bterlson.github.io/proposal-flatMap/#sec-Array.prototype.flatMap | |
value: function flatMap (callback, thisArg = undefined) { | |
const O = toObject(this) | |
const A = arraySpeciesCreate(O, 0) |
One of the biggest missed opportunities thus far with HTTP/2 ("H/2") is that we are not yet able to sunset WebSockets in favor of H/2. Web Sockets and H/2 both support multiplexing messages bi-directionally and can send both textual and binary data.
Server Sent Events ("SSE"), by contrast, are not bi-directional (they're a "server-push-only" channel) and binary data cannot be sent easily. They are, however, very simple to implement. Adding to the menagerie of options, RTCPeerConnection
can also be used to signal data to applications in a low-latency (but potentially lossy) way.
Because H/2 [does not support the handshake (upgrade) that WebSockets use to negotiate a connection](https://daniel.haxx.se/blog/2016/06/15/no-websockets-
(function (context, trackingId, options) { | |
const history = context.history; | |
const doc = document; | |
const nav = navigator || {}; | |
const storage = localStorage; | |
const encode = encodeURIComponent; | |
const pushState = history.pushState; | |
const typeException = 'exception'; | |
const generateId = () => Math.random().toString(36); | |
const getId = () => { |