niconiconi on Nostr: It's 2026, and when you change any config files you still need to do the ritual: `cp ...
It's 2026, and when you change any config files you still need to do the ritual: `cp server.conf server.conf.example`. Imagine if package managers are tightly coupled to the file system, so you no longer need to do this (overlayfs-based managers already do it to an extent), the downside is that a broken package manager is also a filesystem corruption.
Published at
2026-09-02 16:37:09 UTCEvent JSON
{
"id": "a2feba4af69eafb553c6230ff5be32d669401ff11189aacf0a18145b6b97b6ac",
"pubkey": "c9d683688e5e4cb1bfa183741c2f9a7199c5f8a8efd49c7bdcb0ae145acd4f93",
"created_at": 1788367029,
"kind": 1,
"tags": [
[
"proxy",
"https://mk.absturztau.be/notes/aqnvv8rd2w9r0142",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mk.absturztau.be/notes/aqnvv8rd2w9r0142",
"pink.momostr"
],
[
"-"
]
],
"content": "It's 2026, and when you change any config files you still need to do the ritual: `cp server.conf server.conf.example`. Imagine if package managers are tightly coupled to the file system, so you no longer need to do this (overlayfs-based managers already do it to an extent), the downside is that a broken package manager is also a filesystem corruption.",
"sig": "9d2bcbe22dc94c11e1b9b98230d4c3ce8b439d46abb9146510f5b17ec93a1864e3681286aeeef84b1ad9e8061383665c2cd82974dab6ddb37f880c4c708f6036"
}