@kriegalex
Crypto enthusiast running a free relay at wss://nostr.21crypto.ch
Relays (3)
- wss://nostr.21crypto.ch – read & write
- wss://relay.damus.io – read & write
- wss://nostr-2.21crypto.ch – read & write
Recent Notes
Had an interesting interaction with a cashier today.
This young man in his 20s was ringing people up. His voice and mannerisms were basically like Napoleon Dynamite.
In front of me, the customer sai...
I don't think most people have yet realized that most men in his age ARE in fact sad and lonely. It has become normal.
Call it how you want, find it ok or not, an excuse or not, it exists. It started as a dating crisis in Japan, now it's everywhere.
Call it how you want, find it ok or not, an excuse or not, it exists. It started as a dating crisis in Japan, now it's everywhere.
1❤️1
Waiting to see how much max storage space an electrs electrum server will take without pruning.
Currently I'm looking at already 1TB lol
If I've understood correctly, the rule is that the maximum wi...
Online recommandation for SSDs are valid, I can hear my HDDs scratching non-stop since the initial sync finished.
Not sure what would cause so much activity on an empty unused freshly initialized electrum server.
Not sure what would cause so much activity on an empty unused freshly initialized electrum server.
Waiting to see how much max storage space an electrs electrum server will take without pruning.
Currently I'm looking at already 1TB lol
If I've understood correctly, the rule is that the maximum wi...
It took between 20 to 24 hours and peaked at almost 2TB, before compacting to ~950GB. The pool is mainly HDDs with SSD cache, but I don't think that the cache helped much, for this amount of data.
I did not use lightmode and did not use "--address-search".
I did not use lightmode and did not use "--address-search".
Waiting to see how much max storage space an electrs electrum server will take without pruning.
Currently I'm looking at already 1TB lol
If I've understood correctly, the rule is that the maximum will be twice the bitcoind block storage, then it will compact.
#bitcoin #homelab #electrum #electrs
Currently I'm looking at already 1TB lol
If I've understood correctly, the rule is that the maximum will be twice the bitcoind block storage, then it will compact.
#bitcoin #homelab #electrum #electrs
2
I'm building a helm chart for a full Bitcoin stack: bitcoind, an explorer (+electrum) and lightning. What am I missing?
Starting from the blockstream repositories, but I could try to support mix and matches from different sources, if it gets any interest.
#helm #k3s #selfhosting #homelab #docker #bitcoin #lightning
Starting from the blockstream repositories, but I could try to support mix and matches from different sources, if it gets any interest.
#helm #k3s #selfhosting #homelab #docker #bitcoin #lightning
I would use some kind of remote share if the same data should be shared across many apps.
Local storage isn't usually meant for shared data. But I can see why one want would want fast local shared data, that is something easy to do in non cloud native technologies, but it doesn't fit the cloud native mentality.
Maybe it's possible, let us know!
Local storage isn't usually meant for shared data. But I can see why one want would want fast local shared data, that is something easy to do in non cloud native technologies, but it doesn't fit the cloud native mentality.
Maybe it's possible, let us know!
Helm is such a brittle piece of shit. The fucking VHS of managing Kubernetes workloads.
Fuck my life.
I like helm. Maybe I'm weird... Or I got past the beginning with many hours looking for some stupid error in my template.
I wasn't a fan of using helm charts, especially when something goes wrong. I'm probably just inept at k3s, but I like docker for the simplicity.
The only real thing with helm is that your PVC or at least the PV should survive (be Retained) when you need to "helm uninstall", if you don't want to loose data.
Other than that, not really different to other tools. Since it's meant for cloud native stuff, maybe it counts more on your data being easily recoverable from snapshots or S3 buckets, or stuff like that.
Other than that, not really different to other tools. Since it's meant for cloud native stuff, maybe it counts more on your data being easily recoverable from snapshots or S3 buckets, or stuff like that.