spookyuser

This script takes a single input file and

Reduces the volume of the third audio-track in the file by half
Writes the reduced volume track into l
Mixes both the second audio-track and the lowered l-track together and stores them into a
Maps the original video to be the first track
Adds the newly mixed audio-track a as the sole audio track
Enables pass-through for the video-track
Configures the mixed audio-track to be AAC at 192kbit/s

George Hotz - talking hour

Recommendation Martin Shkreli Finance Lesson
Book: White Noise by Don DeLillo
Nietzsche, Kirkegard, Kafka are accessible reading material
The Century of the Self
David Foster Wallace
- David Foster Wallace - The Problem with Irony

Post-Modernism is irony, cynicism, deprication, seen in Fight Club

Decompile JavaScript from source maps

Overview

Modern JavaScript build tools compile entire folder structures of JavaScript code into single, minified files that are near-impossible to read, but can also include source maps which can be used to display the original code in tools such as the Chrome DevTools Sources panel.

These source maps can be processed to extract mainly meaningful code and file structures, by installing a package calling Shuji and running a simple bash command.

Generally, production builds shouldn't include source maps, but if you do manage to lose your source files, or for some (obviously, ethical!) reason need to view the original files, and you happen to have / find the source maps, you're good to go.

Auto-remove unused python imports in VSCode on save

I could not find a proper full configuration for this online, and I know I'll need this again in the future.

There are two ways to achieve this with some plugins; one via hitting the shell and doing an in-place replace, the other is by doing it with extensions configurable in vscode. Both should give you the same results.

Install VSCode extensions needed:

If running via bash:

Run on Save

Logging setup for FastAPI

This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.

Then, you can use Structlog loggers or standard logging loggers, and they both will be processed by the Structlog pipeline (see the hello() endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!

Requests are assigned a correlation ID with the asgi-correlation-id middleware (either captured from incoming request or generated on the fly). All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented. This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog. You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom

	/*

	$ sanity init
	# Follow steps, choose the clean template
	# go to schemas/schema.js and paste this in
	*/

	// First, we must import the schema creator
	import createSchema from 'part:@sanity/base/schema-creator'

	brew install exa
	brew install bat
	brew install hexyl
	brew install fd
	brew install procs
	brew install ripgrep
	brew install dust
	brew install clementtsang/bottom/bottom
	brew install starship

	# tools from https://github.com/ibraheemdev/modern-unix
	tap "cantino/mcfly"
	tap "clementtsang/bottom"
	brew "bat"
	brew "exa"
	brew "lsd"
	brew "git-delta"
	brew "dust"
	brew "duf"
	brew "broot"

	import torch
	from diffusers import StableDiffusionPipeline
	from torch import autocast
	import random
	import matplotlib.pyplot as plt
	import os


	prompts = [
	"1965 Porsche 911",

	(defun codex-refactor (&optional b e)
	(interactive "r")
	(shell-command-on-region b e "codex-refactor.py" nil nil))