Fixing Spotty (again! Thanks SPOTIFY!!)

Spotify keeps changing its API / authentication method and breaking Spotty - a Spotify plugin for LMS.

Recent changes require using the Spotify App on other devices to authenticate it. Given my complicated network setup (wireless bridges etc), it is easier to just generate the credentials on a Windows machine and copy it over to LMS.

- using the Spotify app (not web browser) and start playing music

- download spotty.exe or just use WSL to run the spotty ELF executable on Windows with "spotty --cache . --authenticate"

- on Spotify app, open devices and click on "Spotty"

- a "credentials.json" file should be generated. Copy it to LMS's spotty cache folder

Gemini CLI docker broken

The recent Gemini CLI docker approach is broken. A temp fix is to change the entry point:

 SANDBOX_FLAGS='--entrypoint=""' ~/apps/gemini.sh

Resolving core dump issues when running llama.cpp on Ryzen iGPU

Although running llama.cpp on Ryzen iGPU with Vuklan is slow, but it is free. And with a competent model such as Gemma 4, I use it to plan coding changes overnight so that I could apply them with Gemini CLI the next day.

Recently llama.cpp would core dump due to "DeviceLostError" when the context size approaching ~35k. After some trial-and-error and googling, for now the only way to resolve it is to extend the GPU driver lock timeout with "amdgpu.lockup_timeout=1000000,1000000" kernel command line parameters.