Tamas Kalman ktamas77

Adaptive Streaming has become the neccessity for streaming video and audio. Unfortantely, as of this post, there isn't a whole lot of tutorials that accumulate all of the steps to get this working. Hopefully this post achieves that. This post focuses on using Amazon Web Services (AWS) to transcode for HLS and DASH and be the Content Delivery Network (CDN) that delivers the stream to your web page. We'll be using Video.js for the HTML5 player as well as javascript support libaries to make Video.js work with HLS and DASH.

So Here's what you need:

Set up three S3 buckets

Running Hashcat on Google Cloud's GPU-based VMs

In February 2017, Google announced the availability GPU-based VMs. I spun up a few of these instances, and ran some benchmarks. Along the way, I wrote down the steps taken to provision these VM instances, and install relevant drivers.

Update April 2019: Updated instructions to use instances with the Tesla T4 GPUs.

The Javascript in this gist can be used to grab a parameter (in this example, called "hop") from the URL's query string and place that value into a hidden form field (in this example, with an id of #inf_field_FieldName.)

There are two assumptions in this example, so you should alter them for your own use case.

Assumption 1: the URL parameter you're getting is called "hop".

For example, if you are accessing this page at http://example.com/?hop=something, then this example would retrieve a value of "something". If your URL parameter is called something other than "hop", change it on Line 8 of the example script from

document.getElementById('inf_field_FieldName').value = getUrlParameter('hop');

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

github multiple keys

$ eval "$(ssh-agent -s)"
$ ssh-add ~/.ssh/{private_key}
$ git clone git@{alias}:{github_user}/{repo}.git

~/.ssh/config

	##################
	### config.yml ###
	##################

	version: 2
	jobs:
	build:
	docker:
	- image: circleci/python:3.6
	steps:

	// http://www.iquilezles.org/www/articles/palettes/palettes.htm
	// to see this function graphed out go to: https://www.desmos.com/calculator/18rq4ybrru
	vec3 cosPalette( float t , vec3 brightness, vec3 contrast, vec3 osc, vec3 phase)
	{

	return brightness + contrastcos( 6.28318(osc*t+phase) );
	}

	vec3 hsb2rgb(vec3 c)
	{