OK. I am mildy drunk, and I think that my WO brethren will not be mad about talking about something tangentially on topic under the (very understandable) circumstances while geopolitical pressures are taking center stage, but if not? Well get infofront to delete it... whatever.
Bob.
OK. So the channels I have with you tend to flow to the liquidity being on your side. Both DEEJ and JEED are that way right now.
So for now what I am going to do is set the fees on our channel UP a little. And also all other Wumbo outgoing channels I will drop their fees. If my poor stupid brain is tracking this will attract traffic to flow INTO our channel, but then OUT OF my others (which is where the fees get charged).
I really want to make our channels go back and forth constantly... 16mm IN, 16mm out rinse, lather, repeat 300 times. So once I get the liquidy back onto my side I will switch again, and flow it all our again... Hopefully the script you found ends up automating this... but I thought I'd try it with our channels first to see how it goers.
CURRENTLY I could care less about fees. I just do not want to LOSE money doing this. And I want to have the highest traffic possible. Once I achieve this some more... then I can optimise to make at LEAST enough to cover layer 1 fees.
Moje sudno na povitrianij podušci povne vuhriv!!!
cAPSLOCK is offering some very active inbound liquidity (dude, check your nodes, both are down), as are some other folk who have connected to me, and even transacting at my default 1000/250 rates upon connecting - Not going to complain AT ALL.
I have been running on a 16GB SD card since the beginning a couple years ago. That is becomming not quite enough anymore. So I moved the node over to a 128GB card.
Once the migration was done the bitcoind daemon is not reliably starting. *sigh*
I have rebuilt the thing a couple times, and each time it's the same... so for NOW I just am bring it up manually after a reboot. And voila, it's working like a charm.
So you should see my node again now. Hopefully. Though I still have some work to do to understand why the damn thing is not coming up after a reboot... seems almost like tyhere is a window of time where the daemon's pid file (stored on the HDD) cannot be written at first... Anyway. I will deal with this later. Now it's time for a nap.
