Sung Jeon BasixKOR

Proxy Traps Cheat Sheet

There are various shenanigans around the Proxy API, including issues with Array.isArray and Object.ownKeys so that this gits purpose is to describe all the undocummented caveats to help anyone dealing with all possibilities this half-doomed API offers.

The 3 + 1 Proxy Types

object: any non primitive value can be proxied but apply and construct traps won't work with it. If the object somehow wants to represent an array without being one, it's impossible to survive Array.isArray brand check (it will be false) and with ownKeys the target needs to have a non configurable length property or it will also fails once reached
array: it's like object but it survives the `

PostgreSQL is Enough

Background and Cron Jobs

macOS Internals

Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.

Starting Points

How to use this gist

You've got two main options:

Jellyfin API Authorization

To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.

Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.

Sending authorization values

There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed. It's recommend to use the Authorization header. If header auth isn't an option, the token may be sent through the ApiKey query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.

	export function IsolateCSS(props: { children: React.ReactNode }) {
	const onceRef = useRef(false);
	const [shadowRoot, setShadowRoot] = useState<ShadowRoot>();
	const ref = useCallback((ref: HTMLDivElement \| null) => {
	if (ref && onceRef.current === false) {
	onceRef.current = true;
	setShadowRoot(ref.attachShadow({ mode: 'open' }));
	}
	}, []);

	// I'm tired of extensions that automatically:
	// - show welcome pages / walkthroughs
	// - show release notes
	// - send telemetry
	// - recommend things
	//
	// This disables all of that stuff.
	// If you have more config, leave a comment so I can add it!!

	{

	#!/bin/bash

	# Ensure we're working on the latest version of the main branch
	git switch main
	git fetch
	git pull

	# Create a new branch
	git switch -c vitest

	// ==UserScript==
	// @name ASTx2 Emulator
	// @namespace http://tampermonkey.net/
	// @version 0.1
	// @description try to take over the world!
	// @author @BawAppie
	// @match https:///
	// @icon https://www.google.com/s2/favicons?sz=64&domain=ahnlab.com
	// @grant none
	// ==/UserScript==

	# 20x faster replacement for "npm run"
	# - It supports scripts executing a built-in shell function
	# - It supports scripts executing a binary found in PATH
	# - It supports scripts executing a binary found in node_modules
	# - It supports passing arguments and options to scripts
	# - It supports reading scripts either via ripgrep (fast) or via jq (slower, but safer)
	# - It adds ./node_modules/.bin to the $PATH
	# - It handles gracefully when a script has not been found
	# - It handles gracefully when "&", "&&", "\|", "\|\|", or ENV variables are used, falling back to "npm run"

	=====
	parse
	=====
	canada x serde_json x 14.41 ops/sec ±3.31% (40 runs sampled)
	canada x serde_wasm_bindgen x 90.55 ops/sec ±0.53% (77 runs sampled)
	canada x msgpack x 101 ops/sec ±1.90% (72 runs sampled)
	citm_catalog x serde_json x 131 ops/sec ±0.64% (83 runs sampled)
	citm_catalog x serde_wasm_bindgen x 192 ops/sec ±1.02% (85 runs sampled)
	citm_catalog x msgpack x 161 ops/sec ±1.09% (82 runs sampled)
	twitter x serde_json x 203 ops/sec ±0.89% (85 runs sampled)