Skip to content

Instantly share code, notes, and snippets.

View DanielOaks's full-sized avatar

Daniel Oaks DanielOaks

View GitHub Profile

Taking photos of your art

If you're trying to take photos of your art, there are a few things to do:

  1. Try to get the light as consistent as possible.
  2. Use your photo editing app to crop the picture nicely.
  3. Use your photo editing app to make the picture 'pop'.

Doing these will help your art look a lot cleaner.

#! /bin/sh
# SMARTd discord notifier
export WEBHOOK_URL="https://discord.com/api/webhooks/YOUR_WEBHOOK_HERE"
export TMP_FILE=/tmp/smartd-discord
# assemble file
echo "**S.M.A.R.T. ERROR**" > $TMP_FILE
echo "> $SMARTD_MESSAGE" >> $TMP_FILE
<!--
this helps me work out which numbers I should put in the effects column of an
XM file to make the chords I've just played. I keep it open on a separate
screen while I'm editing the file with milkytracker. whoo~
-->
<html>
<head>
<script src="https://cdn.jsdelivr.net/npm/webmidi"></script>
<script>
@DanielOaks
DanielOaks / shift-jis.txt
Last active November 7, 2020 22:52
shift-jis sjis emoticons
̿̿ ̿̿ ̿’̿’̵͇̿̿з=༼ ▀̿̿Ĺ̯̿̿▀̿ ̿ ༽
͡ (ु ˲̥̥̥́ ˱̥̥̥̀) ु⁾⁾
͡ (ुŏ̥̥̥̥ ‸ ŏ̥̥̥̥) ु
̯ ̜ᵒ̴̶̷⁎).₊♪‧˚*
ੱ ಒౢੱ)₹Ⱡ੭
‾͟͟͞(((ꎤ >口<)̂ꎤ⁾⁾⁾⁾
‾͟͟͞(((ꎤ ✧曲✧)̂—̳͟͞͞o
‾͟͟͞(((ꎤˋ⁻̫ˊ)—̳͟͞͞o
‾͟͟͞(((ꎤ°᷄д°᷅)و ̑̑༉☆))Д´)
‾͟͟͞(((ꎤ๑‾᷅༬‾᷄๑)̂—̳͟͞͞

GLSL Shader Bits

Constants

#define pi acos(-1.)
#define tau (2.*pi)
@DanielOaks
DanielOaks / kiwibnc-config.ini
Last active February 18, 2023 17:44
kiwibnc configs
[log]
# level may be one of: trace, debug, info, notice, warn, error
level="info"
colour=true
[listeners]
bind = [
"0.0.0.0:3001",
]
@DanielOaks
DanielOaks / writing-a-spec.md
Last active March 8, 2019 01:47
proposed IRCv3 writing-a-spec document draft

How to write an IRCv3 Specification

This rough guide aims to take you through the process of writing an IRCv3 specification and getting it accepted! It doesn't lay out exactly what you must do for a document to get accepted, but should be a useful set of suggestions and considerations to keep in mind as you go through the process.

Why write a spec?

There are a few main reasons why you'd want to write up a spec for inclusion within the IRCv3 Working Group:

  • You'd like to change an aspect of the IRC protocol, and write down in very exact detail how that change works.
  • You have a cool, interesting, and/or useful feature in your software and think that other software should include it.

title: "ACC Multi-Factor Authentication" layout: spec copyrights:

name: "Daniel Oaks"
period: "2019"
email: "[email protected]"

name: "Shivaram Lingamneni"

package main
import (
"log"
"fmt"
"strings"
"sync"
"strconv"
"net"

<limit> is defined by the server/bouncer by default, but the client can optionally ask for a different limit.

CHATHISTORY #ircv3 BEFORE id=ytNBbt565yt4r3err3 [<limit>]
    - get up to <limit> number of messages before the given id/time
CHATHISTORY #ircv3 AFTER id=ytNBbt565yt4r3err3 [<limit>]
    - get up to <limit> number of messages after the given id/time
CHATHISTORY #ircv3 LATEST id=ytNBbt565yt4r3err3 [<limit>]
    - get the most recent (up to `<limit>`) messages that have been sent since the given id/time
    - if * is given instead of a specific ID, just the most recent messages with no limit

CHATHISTORY #ircv3 AROUND id=ytNBbt565yt4r3err3 []