Discover gists

Complete Recent Discord Quest

Note

This does not works in browser for quests which require you to play a game! Use the desktop app to complete those.

How to use this script:

Accept a quest under Discover -> Quests
Press Ctrl+Shift+I to open DevTools
Go to the Console tab
Paste the following code and hit enter:

svn merginfo

####show you what needs to be merged, next you need to svn merge each of those revisions

svn mergeinfo --show-revs eligible https://xxsubver/svn/path .

for each revision run with --dry-run as above and if no conflicts you can take the --dry-run out to perform the

The --dry-run option doesn't actually apply any local changes to the working copy. It shows only status codes that would be printed in a real merge. It's useful for getting a “high-level” preview of the potential merge, for those times when running svn diff gives too much detail.

Season	Episode	Title	Reason
1	5	The Enchiridion	A good intro to the series, plus introduces the important Enchiridion
1	2	Trouble in Lumpy Space*	Introduces LSP (episode out of order)
1	3	Prisoners of Love	Introduces Ice King and his obsession (episode out of order)
1	7	Ricardio the Heart Guy	Finn and PB development, Sets a returning plot
1	8	Business Time*	First mention of Ooo being post-apocalyptic
1	9	My Two Favorite People	Intros the Jake and Lady Rainicorn plotline
1	10	Memories of Boom Boom Mountain	A look at how Finn was adopted into Jake's Family
1	12	Evicted!	Intros Marceline

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.

[macOS] Change Ollama Model Directory

By default, all models pulled from Ollama are stored in the /Users/username/.ollama directory on macOS, where username is your system's current user. If you want to change the model directory to another location, such as an external storage device, you can follow one of the methods below.

Method 1: Temporarily Change the Model Directory

If you only want to change the model directory temporarily, execute the following command in Terminal and restart the Ollama app:

Install Ubuntu Server 20.04

There is no guarantee this guide will work flawless on earlier or later versions of Ubuntu!

1 CPU & 4GB RAM minimum (more CPU helps initial sync)
1TB SSD disk minimum
Resize ubuntu-lv to 50G
Create new umbrel-lv for the remaining space and new mount /umbrel
Select 'Install OpenSSH Server'
Do NOT choose the docker feature, this will be installed manually
Reboot after security patching finishes
Login via SSH

	# ---------------
	# Date: 7/25/2018
	# Place: Biella
	# Author: EscVM
	# Project: OID v4 to Yolo
	# ---------------


	import os
	from tqdm import tqdm

	// Extracted and merged from https://github.com/marekburiak/ILI9341_due
	// New color definitions use for all my libraries
	// Replace the few colours in Display.h (around line 363) with this
	#define TFT_ALICEBLUE 0xF7DF
	#define TFT_ANTIQUEWHITE 0xFF5A
	#define TFT_AQUA 0x07FF
	#define TFT_AQUAMARINE 0x7FFA
	#define TFT_AZURE 0xF7FF
	#define TFT_BEIGE 0xF7BB
	#define TFT_BISQUE 0xFF38

	version: '3'
	services:
	app:
	image: nginx:alpine
	ports: ["80:80"]
	restart: unless-stopped

	restarter:
	image: docker:cli
	volumes: ["/var/run/docker.sock:/var/run/docker.sock"]