bufordtaylor

import React from 'react';
import ReactDOM from 'react-dom'
import { Switch, Route, BrowserRouter } from 'react-router-dom';
import { getRequest, createQueryString } from 'utils/getRequest'
import useScrollPosition from 'hooks/useScrollPosition'

const urlParams = new window.URLSearchParams(window.location.search)
const defaultFilters = {
  role_kinds: urlParams.get('role_kinds') ? urlParams.get('role_kinds').split(',') : []
}

bufordtaylor

call plug#begin('~/.vim/plugged')
Plug 'christoomey/vim-tmux-navigator'
Plug 'christoomey/vim-tmux-runner'
Plug 'Shougo/neocomplcache'
Plug 'airblade/vim-gitgutter'
Plug 'chriskempson/base16-vim'
Plug 'easymotion/vim-easymotion'
Plug 'endel/vim-github-colorscheme'
Plug 'flazz/vim-colorschemes'

bufordtaylor

set-option -g base-index 1             # Start window index count at 1 instead of 0
set -g history-limit 500000            # Set the history limit higher
set -s escape-time 0                   # Allows for faster key repetition
setw -g aggressive-resize on           # Don't constrain window size to smallest client if they're on another window
set -g focus-events on                 # Send focus events to vim
# setw -g monitor-activity on            # Highlight window name when their is activity
set -g mouse on                        # Enable mouse mode: scrolling, pane selecting and window selecting

# Use 256 colors; needed for lightline.vim
set -g default-terminal "screen-256color"

bufordtaylor

Your mod area: www.castingcall.club/mods In it, you'll find two tools, the audio verifiy tool and the project verify tool. They're what we use to give out those badges you see around the site

Here's the basic job of a mod:

1. check each casting call that is published. Does it have the correct information? Is it spam?
2. handle flagged users for abuse
3. verify audio requests as they come in
4. report bugs We try to keep the time spent on modding to as little as possible as we all have lives outside of CCC. So far, we've split our tasks amongst the team.

Audio Verifications: TJ, Magic Al, JFizzy

bufordtaylor

Feature Requests

• ability to consume (watch/listen/read) content offline Size: Small-Med Known Unknowns: Few Impact: Medium Discussion Points:
  1. Could be as simple as linking to stored files on s3 for the user to download and consume however they desire? formats:
• podcasts

bufordtaylor

# Feature Requests

- ability to consume (watch/listen/read) content offline
  Size: Small-Med
  Known Unknowns: Few
  Impact: Medium
  Discussion Points:
    1. Could be as simple as linking to stored files on s3 for the user to download and consume however they desire?
      formats:
        - podcasts

bufordtaylor

#! /usr/bin/env bash

export APPLE_USER=user@example.com
export APPLE_PASS=password1

export AUTH_PLIST=$(curl -su "$APPLE_USER:$APPLE_PASS" "https://setup.icloud.com/setup/authenticate/$APPLE_USER")

export DSID=$(/usr/libexec/PlistBuddy -c "Print appleAccountInfo:dsid" /dev/stdin <<< $AUTH_PLIST)
echo $DSID
export TEMP_MME_AUTH_TOKEN=$(/usr/libexec/PlistBuddy -c "Print tokens:mmeAuthToken" /dev/stdin <<< $AUTH_PLIST)

bufordtaylor

require 'rexml/document'
require 'rexml/xpath'
require 'http'
require 'icalendar'

HTTP::Request::METHODS = HTTP::Request::METHODS + [:report]
module AppleCalDav
  class Client
    attr_accessor :username, :password

bufordtaylor

# Install keybase and pinentry-mac
brew update
brew install keybase pinentry-mac

# Create a Keybase.io account and key
keybase signup

# Or if you have an account
keybase login

bufordtaylor

How to create a Ruby Gem

Why create a gem?

• For code reuse
• For isolation (easy to test, black box input/output)
• For important and/or complex code
• For community features and feedback (if open sourced)

Example code to turn into a gem