Cocoa Hoto in real life (nprofile…k9rm) perner (nprofile…3j8n) Yes, no. I don't want 1 to 2 million lines of update-required every few months months bloat code running on my personal machines just to route some desktop applications through a different VPN; I suffered enough already maintaining Docker & Kubernetes clusters at work for almost a decade, I paid my penance. Not to mention it would likely end up routing the traffic through the Docker router and Kubernetes networking plugins; a needless overhead and source of the nastiest bugs in my experience. And I only want network namespacing for my use-case, nothing more; I will be fighting against every other feature those container engines provide.
I'll stick to my init script that calls the ip and wg commands a few times, then works forever :)
Red Rozenglass /
npub1aj…94pgc
2025-03-26 09:59:32
in reply to nevent1q…ppy6
Author Public Key
npub1aj05n6h74ys35hfujyddczfcmr4drhs79xtrfdxw8sutdq2gnw9q994pgcPublished at
2025-03-26 09:59:32Event JSON
{
"id": "bf935068a22f7ea89422b342d7ecc29cf31710b88e160120659814121daca53d",
"pubkey": "ec9f49eafea9211a5d3c911adc0938d8ead1de1e299634b4ce3c38b681489b8a",
"created_at": 1742983172,
"kind": 1,
"tags": [
[
"p",
"0a93edbc7e77bd5da46055e51d8192ce20cdb5d9cfd88010f67f7d46684cf827",
"wss://relay.mostr.pub"
],
[
"p",
"fb963a709816d4f9fdec6d5375d788a29cd346a6eac195cdb3ae104d01ebc59f",
"wss://relay.mostr.pub"
],
[
"e",
"9aadc584093bf5143db1b66dd5113975950b2a452d3394ea3d12d8efd153d277",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fedi.dreamscape.link/rozenglass/p/1742983172.672056",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqp2f7m0r7w774mfrq2hj3mqvjecsvmdweelvgqy8k0a75v6zvlqns0yk9rm nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlwtr5uyczm20nl0vd4fht4ug52wdx34xatqetndn4cgy6q0tck0sx03j8n Yes, no. I don't want 1 to 2 million lines of update-required every few months months bloat code running on my personal machines just to route some desktop applications through a different VPN; I suffered enough already maintaining Docker \u0026 Kubernetes clusters at work for almost a decade, I paid my penance. Not to mention it would likely end up routing the traffic through the Docker router and Kubernetes networking plugins; a needless overhead and source of the nastiest bugs in my experience. And I only want network namespacing for my use-case, nothing more; I will be fighting against every other feature those container engines provide.\n\nI'll stick to my init script that calls the ip and wg commands a few times, then works forever :)\n\n",
"sig": "288fccd5e48d04c694bc4e87a2e0cde31de02c2e63af930ba113954df123c4e78da5b2b397817c083269a14ac613baa865b4000f22817b7419e3faec47cba76f"
}