maximilliangeorge

#!/usr/bin/env node

console.log("I was executed from a gist inside the terminal with npx!");

maximilliangeorge

#!/usr/bin/env node

console.log("I was executed from a gist inside the terminal with npx!");

maximilliangeorge

// strip unit utility function

@function strip-unit($n) {
  @return math.div($n, ($n * 0 + 1));
}

/**
 * @function interpolate
 * interpolates the size of an element based on the size of the screen
 *

maximilliangeorge

// Creates a helper function to create looping carousel slides.
// @param {number} arrIndex - Index of slide in array (starting from 0)
// @param {number} arrLength - The number of slides in the carousel
// @returns {function} offset - The helper function.

export const steps = (arrIndex, arrLength) => (progress) => {
  const wraps = ((arrIndex + 1) - progress) / arrLength
  const flooredWraps = Math.floor(wraps)

  return 0 - flooredWraps

maximilliangeorge

// MARKER SYNC
//
// Allows you to trigger playback of precomp segments using markers.
// This allows you to change timings without diving into precomps and makes it easier to reason about your project file.
//
// 1. Create a precomp A with a layer called "Controller"
// 2. Add named markers to the timeline within Controller.
// 3. In the parent comp, enable Time Remapping for the precomp A
//
// Modified expression based on Dan Ebbert's Marker Sync Expression

maximilliangeorge

// COUNTDOWN
//
// Creates a countdown in the following format:
// 00D:00H:00M:00S
//
// 1. Create text layer
// 2. Apply expression to text property.

rate = -1;
clockStart = 930604.999;

maximilliangeorge

// MOMENTUM SCROLLING
// 
// Nice easings without the hassle. Doesn't work well for very long distances.
//
// 1. Separate dimensions on layer to scroll (right click _> separate dimensions)
// 2. Apply the expression to the layers Y Position
// 3. Add keyframes. Easing will adapt to mimic momentum scrolling.

const c = thisLayer("Transform")("Y Position")

maximilliangeorge

<?php

// Add ACF data to the WP JSON REST API

  add_action('rest_api_init', 'create_api_posts_meta_field');

  function create_api_posts_meta_field() {

    function get_acf($post) {

maximilliangeorge

{
  "images": [{
    "id": 38123186,
    "name": "1883.1.0 (beta)",
    "distribution": "CoreOS",
    "slug": "coreos-beta",
    "public": true,
    "regions": ["nyc1", "sfo1", "nyc2", "ams2", "sgp1", "lon1", "nyc3", "ams3", "fra1", "tor1", "sfo2", "blr1"],
    "created_at": "2018-09-11T22:47:44Z",
    "min_disk_size": 20,

maximilliangeorge

Lightning Network User Use Cases

The Lightning Network is a layer 2 payment network built on top of Bitcoin. It is denominated in Bitcoin, and disputes are settled entirely by the Bitcoin network. Like Bitcoin, it is decentralized. Ultimately, the utility, speed and cost of the network will be defined by the sum of how all of the participants behave. In this post, I will explore at least 6 different user types I predict will exist on the Lightning Network and my expectation of how they will behave.