.

lightning_node_management.md

@@ -115,4 +115,36 @@ that to have a few, large channels for large nodes and many, smaller channels
 for smaller nodes.
 
 Ok, this is as far as my intuition goes. Now I'm going to do a bit of research
-to try to find out if there are any other factors I'm missing in my thinking.
+to try to find out if there are any other factors I'm missing in my thinking.
+
+----
+
+I came
+across [this brilliant post by Jameson Lopp](https://blog.lopp.net/lightning-network-liquidity-management-guide/)
+. Awesome stuff, as it tends to be when he writes it. In it, it gives a
+thorough explanation of his own experience trying to run a routing lightning
+node. There is plenty of knowledge to get from it, but the main points I'm
+keeping in mind for now are:
+
+- Avoid channels smaller than 1M sats completely. If possible, do larger than
+  10M sats.
+- The rebalance tool by carsten otto works nicely, but only if you don't also
+  have an automatic fee setter (or if you do, just make sure that rebalancing
+  and fee setting happen not so frequently and with time between both).
+- The swaps on [lightningnetwork.plus](https://lightningnetwork.plus) are a
+  good idea and not some random internet scam, so I should look into how to use
+  that.
+
+A few links to interesting stuff that I got from Lopp's post:
+
+- [An article by Alex Bosworth](https://github.com/alexbosworth/run-lnd/blob/master/LIQUIDITY.md)
+  , with the usual thoughts. One new idea I had not seen anywhere though: using
+  my own node to make payments on the lightning network is a great way to
+  rebalance channels that need inbound liquidity.
+- [Node match tool](https://moneni.com/nodematch) to find nodes that increase
+  connectivity of another node (mine, basically).
+- [Lightning Terminal page](https://terminal.lightning.engineering/#/) to get
+  scores on any node. Good for judging candidates for channel opening.
+- [Lightning conductor](https://lightningconductor.net/receipt), which offers
+  liquidity services including a pretty convenient services to open an incoming
+  channel with an on-chain transaction.