--- Log opened Mon Nov 29 00:00:46 2021
02:04 -!- kexkey [~kexkey@static-198-54-132-101.cust.tzulo.com] has quit [Ping timeout: 265 seconds]
02:05 -!- kexkey [~kexkey@static-198-54-132-165.cust.tzulo.com] has joined #c-lightning
05:00 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds]
05:55 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 268 seconds]
06:14 -!- belcher [~belcher@user/belcher] has joined #c-lightning
06:54 -!- jonatack [jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
08:10 < jasan> Meeting in 2 hours 50 minutes.
08:10 < jasan> vincenzopalazzo: ^^
08:11 < jasan> HelloShitty: ^^
08:29 < vincenzopalazzo> jasan: pong! Thanks :)
09:43 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Quit: Leaving]
09:43 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
10:06 -!- jarthur [~jarthur@2603-8080-1540-002d-ddb3-cd8f-aeab-5219.res6.spectrum.com] has joined #c-lightning
11:00 -!- rusty [~rusty@118.102.87.68] has joined #c-lightning
11:02 < rusty>  Hi Everyone!  Our bi-weekly open development meeting is starting  at https://meet.jit.si/CLightning-Open-Meeting!
11:02 < cdecker[m]> Heya ^^
11:58 -!- An0rak [An0rak@user/an0rak] has quit []
12:03 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has quit [Ping timeout: 265 seconds]
12:03 -!- AdityaSharma[m] [~M1adityam@2001:470:69fc:105::c473] has quit [Ping timeout: 265 seconds]
12:04 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has joined #c-lightning
12:18 -!- rusty [~rusty@118.102.87.68] has quit [Ping timeout: 264 seconds]
12:21 -!- AdityaSharma[m] [~M1adityam@2001:470:69fc:105::c473] has joined #c-lightning
12:28 < willcl_ark> Wow, on 26 channels I only have 3 with a forwardstats rate above 0.5, all the rest are below 0.2.  One has tried 326 forwards and failed every single time -- erg.  CLBOSS has not been choosing me the best channels it seems... Nice plugin though mschmoock!
12:31 < vincenzopalazzo> willcl_ark: unfortunatlly there are a lot of cases where this happen. In addition CLBOSS choose node with the help of an API, so we need some way to help CLBOSS to find these node
12:32 < vincenzopalazzo> The real problem, how you say it is find the good nodes, not remove the bad nodes
12:33 < willcl_ark> vincenzopalazzo: sure I understand that. I was looking into how CLBOSS decides if a channel is good, and there's certainly already some thought there: https://github.com/ZmnSCPxj/clboss/blob/d3b252428a06cc35838009705668940f421d495b/Boss/Mod/PeerStatistician.cpp#L26-L124
12:34 < willcl_ark> I will add that, annecdotally, CLBOSS (with 10.2 routing algo) was extremely reliable for me in ES when making a whole load of lightning payments to a lot of new nodes, despite not having "only the best peers"
12:35 < vincenzopalazzo> willcl_ark: one of the things that  clboss ignore it is the up time in the life of the node. But this is a open world
12:36 < willcl_ark> vincenzopalazzo: I'm not sure if I misunderstand, but with clboss-auto-close=true set I saw CLBOSS close a peer last week whose uptime became too low for its liking
12:37 < vincenzopalazzo> One thing that I would like to have, it is a global metrics system, that all agree in some way. At the moment CLBOSS says for me X is good for this reason. autopilot plugin says Y it is good for this reason.
12:38 < vincenzopalazzo> willcl_ark: yes, I can, but clboss can not look in the history of the node, if the node each X period will go down, there is no way to look in the history
12:39 < vincenzopalazzo> CLBOOS ask to the remote API, please give me some good node, and after that I will calculate some metrics on the node that the gossip map has
12:40 < willcl_ark> vincenzopalazzo: is it not storing this in bitcoin/data.clboss (I have not checked that it stores historical uptime there, I just thought it might be!?)
12:40 < vincenzopalazzo> at the first startup how you know this information? when there is no db?
12:41 < vincenzopalazzo> What i'm saying it is that a node should or could learn from the gossip map with some internal metrics, but if you have clean node how you decide who is the best?
12:41 < willcl_ark> ah I see, you are saying it could perhaps reach out to 1ml/amboss.space/similar and ask for a few good nodes, or some data to work with? If so I agree (but not sure how to do it "safely")
12:42 < vincenzopalazzo> Well, we need the up time + forwards rating + info that are in the gossip map
12:43 < vincenzopalazzo> and put it in a server that talk specification. Well I spoiler my master thesis project :-P but any way it will be out in a couple of way
12:44 < vincenzopalazzo> at the moment you can "not trust" system like 1ml, amboss, lightning terminal, because you don't know how the information are collected and stored. How you now that 1ml don't make some preference in the node selection? 
12:45 < willcl_ark> sure I agree, but where else are you getting e.g. forwards rating
12:46 < vincenzopalazzo> or another common info, how you know what implementation the peers are using? if there is lnd 0.14.0 from other side maybe you don't want open a channel with
12:46 < vincenzopalazzo> also because you can't :P
12:47 < willcl_ark> right. Also I'd like to see it prefer dual-funded channels so it can avoid the costly initial rebalancing that it does. 
12:48 < vincenzopalazzo> with this global system you can announce also what you are supporting
12:49 < willcl_ark> I'm curious to learn more about it when its ready
12:49 < vincenzopalazzo> nothing to bad for the privacy I think, if you are a routing node
12:49 < vincenzopalazzo> Basicaly you can jump inside this repo https://github.com/LNOpenMetrics
12:50 < vincenzopalazzo> Tomorrow I will write the announce on the clightning mainling list
12:51 < vincenzopalazzo> I have a beta version of the plugin and hopeful a server that gives you some calculation for the end of December (hope before)
12:52 < willcl_ark> cool!
12:53 < vincenzopalazzo> just take note to see if we can add a feature list in the metrics https://github.com/LNOpenMetrics/lnmetrics.rfc/issues/18 :) thanks for suggesting this
13:23 -!- stonefox [~stonefox@user/stonefox] has quit [Quit: The Lounge - https://thelounge.chat]
13:23 -!- bfsfhkacjzgcytf [~bfsfhkacj@user/bfsfhkacjzgcytf] has quit [Quit: The Lounge - https://thelounge.chat]
13:24 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
13:24 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
13:24 -!- bfsfhkacjzgcytf [~bfsfhkacj@user/bfsfhkacjzgcytf] has joined #c-lightning
13:40 -!- Netsplit *.net <-> *.split quits: face, nathanael, plant-boy[m], RubenSomsen, vincenzopalazzo, berndj, jespada, achow101, roasbeef, livestradamus,  (+31 more, use /NETSPLIT to show all of them)
13:44 -!- Netsplit over, joins: _aj_, RubenSomsen, michaelfolkson, waxwing, _0x0ff, qubenix, willcl_ark, kanzure, merkle_noob[m], johncantrell97[m (+31 more)
15:04 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning
17:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
17:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
19:31 -!- Jackielove4u [uid43977@user/jackielove4u] has quit [Quit: Connection closed for inactivity]
19:49 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 256 seconds]
20:05 -!- rusty [~rusty@tro1759202.lnk.telstra.net] has joined #c-lightning
20:33 -!- rusty [~rusty@tro1759202.lnk.telstra.net] has quit [Ping timeout: 264 seconds]
21:07 -!- kexkey [~kexkey@static-198-54-132-165.cust.tzulo.com] has quit [Ping timeout: 264 seconds]
21:09 -!- kexkey [~kexkey@static-198-54-132-149.cust.tzulo.com] has joined #c-lightning
21:12 -!- rusty [~rusty@118.102.87.68] has joined #c-lightning
21:44 -!- rusty [~rusty@118.102.87.68] has quit [Quit: Leaving.]
21:44 -!- rusty [~rusty@118.102.87.68] has joined #c-lightning
21:59 -!- kexkey [~kexkey@static-198-54-132-149.cust.tzulo.com] has quit [Ping timeout: 264 seconds]
22:02 -!- kexkey [~kexkey@static-198-54-132-85.cust.tzulo.com] has joined #c-lightning
22:46 -!- jarthur [~jarthur@2603-8080-1540-002d-ddb3-cd8f-aeab-5219.res6.spectrum.com] has quit [Quit: jarthur]
23:12 -!- rusty [~rusty@118.102.87.68] has quit [Ping timeout: 264 seconds]
--- Log closed Tue Nov 30 00:00:47 2021