zfogg

#include <Adafruit_NeoPixel.h>
#include <IRremote.hpp>
#include <FastLED.h>

#define LED_PIN 7
#define IRRECV_PIN 8
#define FPS_MILLIS 17
#define NUM_LEDS 12

unsigned int brightness = 32;

zfogg

#include <IRremote.hpp>

#define IRRECV_PIN 8
 

void setup() {
  // Open a serial connection for printing logs.
  Serial.begin(9600);

  // Turn on the infrared receiver.

zfogg

// SPDX-License-Identifier: MIT
pragma solidity 0.8.12;

import {IERC20} from "../interfaces/IERC20.sol";

contract BetEscrow {

    event BetOffered(uint betId);

    enum Status {

zfogg

GitHub Org - Follow Members

How to use it

Manually

1. Navigate to a GitHub organization's member page.
2. Open your browser devtools and go to the JavaScript console tab.
3. Copy 1.follow-github-org-members.js to your clipboard.
4. Paste the script into the JavaScript console and run it, once per page of organization members.

zfogg

This post links my 3Box profile to my Github account! Web3 social profiles by 3Box.
    
  ✅ did:3:bafyreibdbideyyqal6jg6othyvzpa2at5x35ejudk2pr3uabugp3fvjczm ✅
    
    Create your profile today to start building social connection and trust online at https://3Box.io/

zfogg

Section "ServerLayout"
  Identifier "layout"
   Screen 0 "intel"
   Inactive "nvidia"
   Option "AllowNVIDIAGPUScreens"
EndSection

Section "Device"
  Identifier "nvidia"
  Driver "nvidia"

zfogg

#!/usr/bin/env sh

address=${1:-localhost}
port=${2:-53}
proto=${3:-tcp}

(echo > "/dev/$proto/$address/$port") >/dev/null 2>&1 \
    && echo "✅ $address:$port is ONline ✅" \
    || echo "⛔ $address:$port is OFFline ⛔"

zfogg

#!/bin/bash

# Delete Archived Applications
rm -r ~/Library/Developer/Xcode/Archives/*/

# Delete Devired Data
rm -r ~/Library/Developer/Xcode/DerivedData/*/

# Delete Apple cached files
rm -r ~/Library/Developer/CoreSimulator/Caches/dyld/*/*/

zfogg

Flux - all about async actions

So, let's say you have a basic Flux action that fetches remote data asynchronously, and then dispatches that data to its store. The dispatch is called after the async fetch completes, using a promise or callback. Nothing out of the ordinary here! Just your standard async control flow patterns.

Next, let's say we take this action, tie it to a button's onClick, and then we click it. If the async call takes a bit of time to complete (as they tend to do), that click would feel like it either didn't go through or threw an error, because any components listening to the store would do absolutely nothing until the callback completes or the promise resolves (which is when the dispatch will occur).

UI interactions should always give feedback immediately.

If they don't, interactions feel unresponsive, and the app will feel 'broken' in many situations. It will be frustrating to use at the very least!

---

zfogg

Verifying my Blockstack ID is secured with the address 12Y9URumipMVGdnwTf6G2pVC2ZAaXRtcsH https://explorer.blockstack.org/address/12Y9URumipMVGdnwTf6G2pVC2ZAaXRtcsH