lisamelton

#!/usr/bin/env ruby
#
# hb-av1-transcode.rb
#
# Copyright (c) 2019-2023 Don Melton
#

require 'English'
require 'fileutils'
require 'json'

martinpickett

#!/usr/bin/env bash

# Function which does almost everything. It needs to be a function as it is recursively 
# called if the input is a directory.
main () {
	for i in "$@"; do

		# Check to see if input is valid
		checkInput "$i"
		

merlinmann

⌨️ Official Cursor-Resting Area:
╭―――――――—――╮
│  > 🐽 <  │
╰――――――――—―╯

lisamelton

%
% manuscript.latex
%
% Copyright (c) 2022 Don Melton
%
% LaTeX template for Pandoc to create PDFs in standard manuscript format
% with both short story and novel layouts.
%
% Version: 2022052301
%

lisamelton

#!/usr/bin/env ruby
#
# classic-transcode.rb
#
# Copyright (c) 2019-2022 Don Melton
#

require 'English'
require 'fileutils'
require 'json'

lisamelton

#!/usr/bin/env ruby
#
# special-transcode.rb
#
# Copyright (c) 2019-2022 Don Melton
#

require 'English'
require 'fileutils'
require 'json'

joepie91

The Freenode resignation FAQ, or: "what the fuck is going on?"

IMPORTANT NOTE:

It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.

Update 3 (May 24, 2021)

A number of things have happened since the last update.

khaosx

# This script creates a playlist that contains the next unwatched episode of any 
# shows you define in a collection.
#
# Requires python 3
#
# Usage:
# 
# In Plex, create a collection named "Current Shows". It should contain all the shows 
# that you want considered for the new playlist.
# 

cite-reader

This oral his­to­ry of pass­word stor­age on the Web orig­i­nal­ly ap­peared as a re­mark in the #in­fos­ec chan­nel of the Hang­ops slack—the con­ver­sa­tion had turned to a men­tion of “hashed, salt­ed pass­words” in a breach an­nounce­ment in a way that made me sus­pect at least some of our friends had not stud­ied the top­ic in de­tail. Sev­er­al par­tic­i­pants then en­cour­aged me to ex­pand the re­mark into a blog post, and now here we are.While I was around for some of this, much of it pre­dates my ca­reer; every­thing is as ac­cu­rate as I can rea­son­ably make it, but cor­rec­tions of gross er­rors are wel­comed.The first time peo­ple at­tempt to de­sign a Web lo­gin sys­tem, they will usu­al­ly de­fault to sim­ply in­sert­ing their users’ pass­words in their data­base. This so­lu­tion is sim­ple, ob­vi­ous, and wrong.The prob­lem is that data­base stor­age is not near­ly as pri­vate as we would all like it to be. Even the data­bas­es that we’d

khaosx

#! /bin/bash
#
# Calculate bitrate statistics for movies
# Script courtesy of https://www.reddit.com/user/pcpcy
#
# Requires: 
# ffmpeg_bitrate_stats (https://github.com/slhck/ffmpeg-bitrate-stats)
# printTable from util.bash (https://github.com/gdbtek/linux-cookbooks/blob/master/libraries/util.bash)
# jq (https://stedolan.github.io/jq/)
#