jsmlls

// 2024
{
  "workbench.startupEditor": "none",
  "workbench.iconTheme": "moxer-icons",
  "workbench.colorTheme": "Vesper",
  // Theme often switched...Try Kanagawa Black or Aura Theme Dark
  "workbench.settings.editor": "json",
  "breadcrumbs.enabled": false,
  "explorer.compactFolders": false,
  "editor.wordWrap": "on",

dphase

How to theme Slack v4.12.0+

Update as of 8.08.2021:

• Hid the bookmarks bar and fine-tuned some header styles.

If you want to add your own style to Slack, here's how.

My quazi-Tron Theme'ish?

I dunno what happened. I just wanted to try something sporty/future-y, I guess. Code for this is directly below.

sbilly

Common ZeroTier Rules Engine question

• Non-servers can talk to servers, but not each other
• Kind of like Client Isolation on some WiFi controllers

Rules

# Allow only IPv4, IPv4 ARP, and IPv6 Ethernet frames. Typical default
drop
not ethertype ipv4
and not ethertype arp

fnky

ANSI Escape Sequences

Standard escape codes are prefixed with Escape:

• Ctrl-Key: ^[
• Octal: \033
• Unicode: \u001b
• Hexadecimal: \x1B
• Decimal: 27

focus97

How to theme Slack v4.12.0+

Update as of 8.08.2021:

• Hid the bookmarks bar and fine-tuned some header styles.

If you want to add your own style to Slack, here's how.

My quazi-Tron Theme'ish?

I dunno what happened. I just wanted to try something sporty/future-y, I guess. Code for this is directly below.

possen

Sierra 10.12.6 Hackintosh

Based upon this GIST which was great!

This is my build documentation for an ASUS PRIME Z270-AR setup with an MSI 1080 Gaming X 8GB, EVGA 1080 8GB and the Intel i5 7600, most of this came from the person I forked this guide from. This build also doesn't have NVRAM. Nearest I can tell everything is running as expected, including all USB and audio ports. Make sure you get MacOS 10.12.6 as it has native support for Kaby Lake processors, and you won't need to fake the CPUID.

Build

• Asus Z270-AR
• Intel Core i5-7600 (Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz)*

unsalted

Sierra 10.12.3 Hackintosh

This is my build documentation for an ASUS Z170-A setup with an NVIDIA GTX960 and the Intel i5 6500, most of this came from Storks asus rog maximus build, his audio instructions didn't work for me so it differs substantially there. This build also doesn't have NVRAM. Nearest I can tell everything is running as expected, including all USB and audio ports.

Build

• Asus Z170-A
• Intel Core i5-6500
• Crucial Ballistix Sport LT 32GB (2 x 16GB) DDR4-2400 Memory
• MSI GeForce GTX 960 4GB Installed in slot 1!

phiresky

# vim: set ft=python:

# see the README at https://gist.github.com/phiresky/4bfcfbbd05b3c2ed8645
# source: https://github.com/mpv-player/mpv/issues/2149
# source: https://github.com/mpv-player/mpv/issues/566
# source: https://github.com/haasn/gentoo-conf/blob/nanodesu/home/nand/.mpv/filters/mvtools.vpy

import vapoursynth

core = vapoursynth.get_core()

danawoodman

WebSockets + Reflux + React

Using WebSockets, React and Reflux together can be a beautiful thing, but the intial setup can be a bit of a pain. The below examples attempt to offer one (arguably enjoyable) way to use these tools together.

Overview

This trifect works well if you think of things like so:

1. Reflux Store: The store fetches, updates and persists data. A store can be a list of items or a single item. Most of the times you reach for this.state in react should instead live within stores. Stores can listen to other stores as well as to events being fired.
2. Reflux Actions: Actions are triggered by components when the component wants to change the state of the store. A store listens to actions and can listen to more than one set of actions.

raggi

# rack_sse.ru
#
# An example of basic real-time, single-room broadcast chat using Server Sent
# Events in plain old Rack. This example does NOT use hijack, or the async
# hacks, it just relies on a well implemented threaded Rack server (at time of
# writing this will therefore only work with puma!). Other servers should be
# fixed to support this, as it is pretty critical to how Rack *should* work on
# most servers. The only spec-acceptable failure in this case is not flushing
# the content stream on each yield (for which the rack spec has no workaround
# today).