rain-1

Raspberry Pi, Static HTTPS site with Docker and Nginx

This tutorial is dated Oct 2021, if it's much further on than that this information might be out of date.

This is a guide on setting up a static HTTPS website on your raspberry pi using docker and nginx. The aim is to have this running on the raspberry pi and to be able to access it from a host computer on the same local network. You should already be able to ssh into your pi from your host computer and have raspberry pi OS set up.

Find your raspberry pi

rain-1

Why is IRC distributed across multiple servers?

I have been wondering for a long time why IRC networks have multiple servers. Wouldn't it be simpler just to use a single server?

One of the problems of having multiple servers is that netsplits can occur. Anybody who has been on IRC for a while will have witnessed one. Hundreds of people suddenly ripped out of the chat. This can also screw up channel and user modes, and 'some people' have been known to wait for netsplits in order to takeover channels or enter password protected channels.

So lets compare situation (A) a single IRC server everyone connects to with the current setup people use (B) multiple servers. Let's say you run an IRC network with u = 40,000 users and n = 20 server nodes that people connect to via round robin DNS (meaning that when people resolve the DNS it gives them a random server from the set of 20 to connect to). These are vaguely realistic numbers modelled after libera.chat.

So in (B) you have roughly u/n = 2000 clients connected

rain-1

#include <assert.h>
#include <errno.h>
#include <libgen.h>
#include <limits.h>
#include <linux/limits.h>
#include <signal.h>
#include <stdarg.h>
#include <stdio.h>
#include <stdlib.h>

rain-1

# INTRODUCTION

This document specifies the DEPENDS.TXT file for a software project.
This is simply a list of the build time and runtime dependencies of the software.

# SPEC

The file is in TSV (tab separated values) format with UTF-8 encoding, so each line is a record describing a single dependency.

Each record is <package-name>\t<type>\t<version>

rain-1

My Markdown Spec

This is (yet) another markdown specification. The purpose of this particular markdown spec is to provide a single unambiguous markdown specification. It aims to use formal regular expressions so that implementors can quickly create implementations (given a regex library) and the results will be consistent across platforms. We specify a very small subset of the markdown seen in the wild.

Version 0.1

rain-1

using Gtk;

// valac --pkg gtk+-3.0 mytv.vala

public class MarkupTextView : TextView {
	public void append_text (string s) {
		TextIter end_iter;
		buffer.get_end_iter (out end_iter);
		buffer.insert_with_tags_by_name (ref end_iter, s, -1, null);
	}

rain-1

package main

import (
	"bufio"
	"fmt"
	"os"
	"log"
	"regexp"
)

rain-1

#lang racket

(require racket/stream)

(define (make-prefix len)
  (lambda (tail)
    (append (make-list len '_) (cons 'o tail))))

(define (k-combinations k n)
  (cond ((= k 0)

rain-1

#lang racket

(require (for-syntax racket/syntax))

(define toplevel 'foo)

(define-syntax (set^ stx)
  (syntax-case stx ()
    [(_ (attr x) y)
     (with-syntax ([set-attr! (format-id #'toplevel "set-~a!" (syntax-e #'attr))])

rain-1

#lang racket

;; This implements a baby lisp interpreter using closure conversion pass before execution
;; It supports serialization of closures (e.g. for partial evaluation/staging) and reading back and executing those objects

(require data/queue)

;; closure conversion for lambda calculus
;;
;; the input language is: