Ram on Nostr: `` I originally published this article in my gopherhole on March 8, 2022 [0]. Aside ...
I originally published this article in my gopherhole on March 8, 2022 [0]. Aside from a few formatting quirks, I did not change the content of this article and it is exactly the same as when I first published it.
My internet went down today. But despite that, I can still write a phlog talking about it and I can be assured that once I have my internet connection back, that the processes that I have put in place will kick in and automatically update my gopherhole. I think that’s a comforting thought to have, that I have built a mostly delay-tolerant system that I can reliably rely on all situations.
I personally think that having this kind of mentality is imperative nowadays. I think having as much of the things that you have to be not reliant on other people and processes are a much better solution. For example, if you are using a platform like Medium to compose and publish your blogs then you would be helpless and cut-off if you can’t access their website.
It might not be intuitive or it might even require you to *gasp* read a manual. But the payoff is incredible.
Contrast that to just having your own local copy of your website and you just periodically update it through simple terminal commands. It might not be intuitive or it might even require you to *gasp* read a manual. But the payoff is incredible. It means that you are not reliant on the infrastructure that other have made and that should those infrastructure prove to be fragile, as is the case today. Then you are not caught helpless and unable to do anything about it.
[0] gopher://kalayaan.xyz/0/~rtr/guper/fragility-of-infrastructure.txt
Published at
2023-04-05 03:22:56Event JSON
{
"id": "df9f1ba8365ee49e3b64a726b4da91992965fb688861278e57ed7c62736eddd5",
"pubkey": "3acf7ffdbab8f2d07029a8d7e2a4439f2c131d41450faefe3f5972e0937abb7b",
"created_at": 1680664976,
"kind": 30023,
"tags": [
[
"d",
"1680663865221"
],
[
"title",
"The Fragility of Infrastructure"
],
[
"summary",
"A brief article where I talk about the boon of having a resilient way of publishing information online."
],
[
"published_at",
"1680664976"
],
[
"t",
"gopher"
],
[
"t",
"frugal computing"
]
],
"content": "``\nI originally published this article in my gopherhole on March 8, 2022 [0]. Aside from a few formatting quirks, I did not change the content of this article and it is exactly the same as when I first published it.\n``\n\n---\n\nMy internet went down today. But despite that, I can still write a phlog talking about it and I can be assured that once I have my internet connection back, that the processes that I have put in place will kick in and automatically update my gopherhole. I think that's a comforting thought to have, that I have built a mostly delay-tolerant system that I can reliably rely on all situations.\n\nI personally think that having this kind of mentality is imperative nowadays. I think having as much of the things that you have to be not reliant on other people and processes are a much better solution. For example, if you are using a platform like Medium to compose and publish your blogs then you would be helpless and cut-off if you can't access their website. \n\n\u003e It might not be intuitive or it might even require you to `*gasp*` read a manual. But the payoff is incredible.\n\nContrast that to just having your own local copy of your website and you just periodically update it through simple terminal commands. It might not be intuitive or it might even require you to `*gasp*` read a manual. But the payoff is incredible. It means that you are not reliant on the infrastructure that other have made and that should those infrastructure prove to be fragile, as is the case today. Then you are not caught helpless and unable to do anything about it.\n\n[0] gopher://kalayaan.xyz/0/~rtr/guper/fragility-of-infrastructure.txt",
"sig": "92a311cc09c7bb3bbe0d6dc4659080d26e9a2eec00b993eaa347b721f985f499e0a5c280d0c2b55a52be7fe9d13783c26d9cdc10e5496322283189f003d572fc"
}
