• Wide Event: A single, context-rich log event emitted per request per service. Instead of 13 log lines for one request, you emit 1 line with 50+ fields containing everything you might need to debug.

• Canonical Log Line: Another term for wide event, popularized by Stripe. One log line per request that serves as the authoritative record of what happened.

Source: https://news.ycombinator.com/item?id=46346796

Very well argued

Using a post-commit hook to run tests in a separate workspace, and report back the results as a git note.

All encryption is end-to-end, if you’re not picky about the ends. config TCG_TPM2_HMAC bool “Use HMAC and encrypted transactions on the TPM bus” default n select CRYPTO_ECDH select CRYPTO_LIB_AESCFB select CRYPTO_LIB_SHA256 select CRYPTO_LIB_UTILS help Setting this causes us to deploy a scheme which uses request and response HMACs in addition to encryption for communicating with the TPM to prevent or detect bus snooping and interposer attacks (see tpm-security.rst). Saying Y here adds some encryption overhead to all kernel to TPM transactions. Last year, I came agross a Linux kernel feature called TCG_TPM2_HMAC. It claims to detect or prevent active and passive interposer attackers. That’s one of my sleeper agent activation phrases, so I dug in.

Permacomputing is a nascent concept and a community of practice centred around design principles that embrace limits and constraints as a positive thing in computational culture, and on creativity with scarce computational resources. As a result, permacomputing aims to provide a countervoice to digital practices that promote maximisation, hyper-consumption and waste.

Seems like an incredibly cool alternative to docker that is far more portable

A way to select any text and have it execute some action

Intro to Oberon OS