SoloSynth1

# Vimium config to match Tridactyl's mappings.
# https://vimium.github.io/commands/
unmap d
unmap u
unmap x
unmap j
unmap k
unmap s
unmap S
unmap o

SoloSynth1

[alias]
lg1 = log --graph --abbrev-commit --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold green)(%ar)%C(reset) %C(white)%s%C(reset) %C(dim white)- %an%C(reset)%C(bold yellow)%d%C(reset)' --all
lg2 = log --graph --abbrev-commit --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold yellow)%d%C(reset)%n''          %C(white)%s%C(reset) %C(dim white)- %an%C(reset)' --all
lg = !"git lg1"

SoloSynth1

For some reason, IntelliJ IDEs still run on Xwayland in Wayland WMs (as of 2025-08-12). This can cause scaling issues for some monitors where everyting is scaled 2x, or more. (I assume this is caused by HiDPI info provided is incorrect)

To fix this, you can instruct the IDE to use WLToolKit for AWT.

Steps:

1. Go to Help | Edit Custom VM Options.... You can use the search function to find it as well. A file with .vmoptions extensions will be opened.
2. Add a line at the end of the file: -Dawt.toolkit.name=WLToolkit.
3. Restart your IDE.

SoloSynth1

services:
  broker:
    image: docker.io/library/redis:8
    restart: always
    volumes:
      - /volume1/docker/paperlessngx/redis:/data
  db:
    image: docker.io/library/postgres:17
    restart: always
    volumes:

SoloSynth1

# Edited to add yabai-like joining commands & global shortcuts

# You can use it to add commands that run after login to macOS user session.
# 'start-at-login' needs to be 'true' for 'after-login-command' to work
# Available commands: https://nikitabobko.github.io/AeroSpace/commands.html
after-login-command = []

# You can use it to add commands that run after AeroSpace startup.
# 'after-startup-command' is run after 'after-login-command'
# Available commands : https://nikitabobko.github.io/AeroSpace/commands.html

SoloSynth1

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts and experience preferred (super rare at this point).

My own notes from a few months back.

Background

• Survey of LLMS
• Self-attention and transformer networks

SoloSynth1

SoloSynth1

CONDA_ENV=tf
conda create -n $CONDA_ENV python=3.9
conda deactivate
conda activate $CONDA_ENV

# install cuda toolkit
conda install -c conda-forge cudatoolkit=11.8.0

# install cuDNN and Tensorflow
python3 -m pip install nvidia-cudnn-cu11==8.6.0.163 tensorflow==2.12.0

SoloSynth1

Using virt-manager, one can connect to remote libvirtd to gain access to VMs hosted by the remote machine.

For reasons unknown, when trying to add new connection using its GUI, it will not connect properly.

This was most likely caused by the auto-generated URI being incorrect.

Therefore, one way to get around this is to use CLI arguments to add the remote host when opening virt-manager:

virt-manager -c 'qemu+ssh://@/system?socket=/var/run/libvirt/libvirt-sock'

SoloSynth1