ztmr

On Xorg and Wayland

There's already been quite a bit of hype surrounding the way Wayland has been developed over Xorg, see for example:

https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277?permalink_comment_id=4749746

But a lot of the criticisms seem to stem from the limitations of Wayland right now, whether that's due to design decisions which Wayland have made in comparison to Xorg, or because Wayland has a feature which is similar to Xorg but not quite the same.

Most people seem to take it at face value that Xorg is slow and insecure, etc., with only anecdotal evidence to back it up, and hence just believe that Wayland is better because it has a different design.

Author: Kukks

New protocol design: Discrete Payments through Wabisabi coinjoins and Nostr ecnrypted communication

Merchant creates invoice of 0.1BTC
Merchant generates a unique key for invoice
Merchant shows the pubkey of (2), a recommended nostr relay uri
Customer generates a unique key for this invoice payment
Customer posts an encrypted event addressed to pubkey of (3) with a message stating intent to pay invoice of 0.1BTC using a specific wabisabi coordinator

Synology: how to increase shutdown temperature

My Synology DS218+ runs with a single SSD disk that has an operating temperature range of 0–70 °C, which is common for SSDs. Synology, however, has a default shutdown temperature of 61 °C, probably due to HDDs and some lazy programming.

I'm a very light user of NAS – all I want is a network attached storage and silence. My DS218+ has one 2 TB SSD disk in it and I've changed the system fan for a quieter / slower one.

Everything runs fine but about once in a month, I get this notification:

[Synology DS218+]Synology shut down due to disk overheating. >

With src/foo/core.cljs:

(ns foo.core)

(defn calculate []
 (let [xform (comp (map inc) (filter odd?) (take 123))]
   (transduce xform + (iterate inc 0))))

(js/print (calculate))

Create Gitlab Personal Access Token using curl

Prerequisites

You need a Gitlab server up and running
You need user credentials for a (admin) user on the Gitlab server
You need curl and Perl on your server

Airband receivers

Heya all! I was asked to write up a document on how to build your own autonomous airband ACARS receiver and join the club. Before you start shelling out moneys, though, I recommend checking whether there is any plane activity in your area: go visit your favourite plane spotting site (e.g. flightradar24) and observe air traffic for awhile; if there's nothing flying above for the whole day, there is no big point in setting up.

My big thanks extends to Thierry and Hugo who helped to beta test this document. :-)

Without any further delay, let's dive.

To build a working receiver, you will need:

	# Project Policy

	This policy provides a single, authoritative, and machine-readable source of truth for AI coding agents and humans, ensuring that all work is governed by clear, unambiguous rules and workflows. It aims to eliminate ambiguity, reduce supervision needs, and facilitate automation while maintaining accountability and compliance with best practices.

	# 1. Introduction

	> Rationale: Sets the context, actors, and compliance requirements for the policy, ensuring all participants understand their roles and responsibilities.

	## 1.1 Actors

	#!/bin/sh
	#
	# Original: https://github.com/cceckman/homelab/blob/main/helpers/rm2-tailscale.sh
	# I am the original author of this document and release it into the public domain.
	# Go wild.
	#
	# This script enables [Tailscale] on a [reMarkable 2] tablet.
	#
	# Tailscale is run in [userspace networking] mode, so any outbound applications
	# will need to be configured to proxy via tailscaled.

	#!/usr/bin/env python3

	# install dependencies:
	# pip install base45 cbor2 (cwt - not used here)

	import sys
	import zlib

	from base45 import b45decode
	from cbor2 import loads

	{ lib ? null, ... }:

	let

	net = {
	ip = {

	# add :: (ip \| mac \| integer) -> ip -> ip
	#
	# Examples: