--- Day changed Tue Jul 31 2018 00:00 -!- User_ [~User@180.217.140.78] has joined #c-lightning 00:00 -!- User_ [~User@180.217.140.78] has quit [Client Quit] 00:01 -!- ken2812221 [~User@180.217.140.78] has joined #c-lightning 00:31 -!- froyer [~froyer@124.19.31.4] has quit [Remote host closed the connection] 00:58 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:06 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 01:11 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 276 seconds] 01:30 -!- tiagotrs [~user@i59F744A2.versanet.de] has joined #c-lightning 01:30 -!- tiagotrs [~user@i59F744A2.versanet.de] has quit [Changing host] 01:30 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 01:48 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 268 seconds] 01:50 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has joined #c-lightning 01:50 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has quit [Changing host] 01:50 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 02:03 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1782: Remove dead stores (master...remove-dead-stores) https://git.io/fNVzR 02:03 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1783: Make sure we're not using uninitialized values (master...don't-use-uninitialized-values) https://git.io/fNVzE 02:15 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 02:18 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 268 seconds] 02:20 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 256 seconds] 02:33 -!- tiagotrs [~user@i59F744A2.versanet.de] has joined #c-lightning 02:33 -!- tiagotrs [~user@i59F744A2.versanet.de] has quit [Changing host] 02:33 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 02:35 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1784: Return true or false from sqlite3_bind_* based on result from SQLite instead of always returning true (master...sqlite3_bind) https://git.io/fNVaY 02:46 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 02:49 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1785: Remove unused function parameters (master...remove-unused-parameters) https://git.io/fNVVg 02:51 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 260 seconds] 03:05 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1787: Don't advertise features we don't have in run-sphinx (master...truth-in-advertising) https://git.io/fNVr0 03:27 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 03:44 -githubby:#c-lightning- [lightning] cdecker closed pull request #1784: Return true or false from sqlite3_bind_* based on result from SQLite instead of always returning true (master...sqlite3_bind) https://git.io/fNVaY 03:45 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/fNV63 03:45 -githubby:#c-lightning- lightning/master b5682a7 practicalswift: Remove dead stores 03:53 -!- tiagotrs [~user@i59F744A2.versanet.de] has joined #c-lightning 03:53 -!- tiagotrs [~user@i59F744A2.versanet.de] has quit [Changing host] 03:53 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 03:58 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 268 seconds] 04:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 04:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 04:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 04:56 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 04:56 -!- tiagotrs [~user@i59F744A2.versanet.de] has joined #c-lightning 04:56 -!- tiagotrs [~user@i59F744A2.versanet.de] has quit [Changing host] 04:56 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 05:00 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 05:00 -!- farmerwampum [~farmerwam@88.202.178.98] has joined #c-lightning 05:12 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1788: Remove redundant code (master...redundant-code) https://git.io/fNV9M 05:39 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:47 -!- douglas_ [~douglas@172.58.216.99] has joined #c-lightning 05:50 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 276 seconds] 06:12 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has quit [Quit: leaving] 06:13 -!- qubenix [~qubenix@104.200.129.53] has quit [Ping timeout: 240 seconds] 06:15 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has joined #c-lightning 06:18 -!- qubenix [~qubenix@185.212.170.51] has joined #c-lightning 06:22 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 06:22 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 06:24 -!- douglas__ [~douglas@172.56.22.62] has joined #c-lightning 06:27 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 244 seconds] 06:27 -!- douglas_ [~douglas@172.58.216.99] has quit [Ping timeout: 244 seconds] 06:33 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 06:37 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 245 seconds] 06:38 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 264 seconds] 06:40 -!- sturles [~sturles@unaffiliated/sturles] has quit [Ping timeout: 240 seconds] 06:46 -!- douglas_ [douglas@nat/redhat/x-zhhvyjiktusmhduh] has joined #c-lightning 06:49 -!- douglas__ [~douglas@172.56.22.62] has quit [Ping timeout: 244 seconds] 06:58 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-dccehwduflltfavv] has joined #c-lightning 06:58 < Lightblock_> Hi everyone 06:58 < Lightblock_> we have been playing with c-lightning for a while now 06:59 -!- sturles [~sturles@ulrik.uio.no] has joined #c-lightning 06:59 -!- sturles [~sturles@ulrik.uio.no] has quit [Changing host] 06:59 -!- sturles [~sturles@unaffiliated/sturles] has joined #c-lightning 06:59 < Lightblock_> the discovery seems to be really poor, from our observations c-lightning has about 10-15 hours in comparison to other node implementations 07:00 < Lightblock_> are the any other factors which impact the frequency of updates for data about new nodes/channels? 07:04 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 07:11 < Lightblock_> anyone has to share anything on that? 07:13 -!- tiagotrs [~user@i59F744A2.versanet.de] has joined #c-lightning 07:13 -!- tiagotrs [~user@i59F744A2.versanet.de] has quit [Changing host] 07:13 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 07:21 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:22 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 07:31 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/fNwvC 07:31 -githubby:#c-lightning- lightning/master ba4282f practicalswift: Don't advertise features we don't have in run-sphinx 08:10 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 08:14 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:15 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 08:15 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 264 seconds] 08:28 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 248 seconds] 08:43 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 08:44 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 08:52 -githubby:#c-lightning- [lightning] jb55 opened pull request #1789: lightningd: add status flags, show when we're syncing (master...lightning-status-flags) https://git.io/fNwsJ 09:03 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:18 <@cdecker> Lightblock_: what do you mean by discovery? 09:18 <@cdecker> The time until the gossip messages are processed? 09:18 <@cdecker> And what are you comparing this to? 09:20 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has joined #c-lightning 09:23 < molz> cdecker, i suspect he's been doing some type of payment and chain analysis, he wants more info so he can track down on payments 09:24 -!- froyer [~froyer@126.121.233.220.static.exetel.com.au] has quit [Ping timeout: 264 seconds] 09:28 -!- douglas_ [douglas@nat/redhat/x-zhhvyjiktusmhduh] has quit [Ping timeout: 240 seconds] 10:03 -!- dougsland [~douglas@172.56.23.177] has joined #c-lightning 10:10 -!- dougsland [~douglas@172.56.23.177] has quit [Remote host closed the connection] 10:10 -!- dougsland [~douglas@172.56.23.177] has joined #c-lightning 10:13 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 10:14 < Chris_Stewart_5> Is there a reason c-lightning fee estimation on testnet is so radically different than eclair? 10:16 -!- dougsland [~douglas@172.56.23.177] has quit [Ping timeout: 248 seconds] 10:17 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-dccehwduflltfavv] has quit [Quit: Connection closed for inactivity] 10:34 -githubby:#c-lightning- [lightning] gabridome opened pull request #1790: improvements in format and flow. Some details added (master...patch-2) https://git.io/fNwuI 11:04 -!- keymone [~keymone@ip1f13761c.dynamic.kabel-deutschland.de] has quit [Ping timeout: 244 seconds] 11:11 -!- keymone [~keymone@ip1f13761c.dynamic.kabel-deutschland.de] has joined #c-lightning 11:22 < Chris_Stewart_5> it has bitten me, and users of my lapp a couple times now :-( 11:30 <@cdecker> c-lightning will attempt to fuzz the amount in order to hide its tracks 11:31 <@cdecker> It'll allow itself to overspend up to 0.5% by default (or 5 satoshi for tiny payments) and will randomize route selection 11:31 <@cdecker> i.e., not always pick the cheapest route 11:32 < Chris_Stewart_5> cdecker: If you have a direct connection surely it will choose that right? 11:32 <@cdecker> This is particularly felt for tiny payments, and less notable on mainnet 11:32 <@cdecker> It should, but it may also select a longer one 11:32 <@cdecker> Hm, actually that's a case we probably shortcircuit 11:32 <@cdecker> (since there is no fee for direct payment either) 11:32 <@cdecker> I'd need to check that 11:33 <@cdecker> Ok, added to my checklist :-) 11:33 < Chris_Stewart_5> ok, interesting. I've added my max fee mismatch to 150x on our testnet eclair node for now to get around this (!) 11:34 < Chris_Stewart_5> I had one of the lightning labs devs report this to me { "code" : -1, "message" : "received ERROR channel 0b3a6f4f6d7d521e45bc1ba0f239bfaf1b942e1fa7b1f9a3194e1c471e32c29e: local/remote feerates are too different: remoteFeeratePerKw=284 localFeeratePerKw=31216" } 11:35 <@cdecker> Wat? We now slowly ramp up to the actual fee estimate over 5 minutes to give the remote side time to witness a change in fee estimate as well 11:35 <@cdecker> It used to be the case that we see a block, immediately jump to the new estimate, and the remote end would still see the old estimate 11:49 < Chris_Stewart_5> cdecker: So looking at that closer it does seem eclair has a very high fee estimation compared to c-lightning 11:49 < Chris_Stewart_5> and I would guess that c-lightnings was probably closer to "correct" whatever that means :-) 11:50 < Chris_Stewart_5> by the way, I think your info graphics on your videos are getting better 11:57 <@cdecker> I'd define "correct" as being as low as possible, as private as possible and still working (3 chose 2 xD) 11:57 <@cdecker> Thanks ^^ 11:58 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has quit [Read error: Connection reset by peer] 12:06 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 12:35 -!- tiagotrs [~user@i577A637A.versanet.de] has joined #c-lightning 12:35 -!- tiagotrs [~user@i577A637A.versanet.de] has quit [Changing host] 12:35 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 12:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 12:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 13:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:45 -!- deusexbeer [~deusexbee@079-170-138-040-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 244 seconds] 13:55 -!- deusexbeer [~deusexbee@093-092-177-247-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 14:09 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 256 seconds] 14:09 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 256 seconds] 14:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds] 14:51 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 15:49 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 16:29 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 264 seconds] 16:52 -!- froyer [~froyer@pa49-181-171-123.pa.nsw.optusnet.com.au] has joined #c-lightning 16:54 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:55 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 17:07 -!- froyer [~froyer@pa49-181-171-123.pa.nsw.optusnet.com.au] has quit [Remote host closed the connection] 17:14 -!- froyer [~froyer@124.19.31.4] has joined #c-lightning 17:24 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 260 seconds] 17:26 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 17:31 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 256 seconds] 17:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:54 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 17:57 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 240 seconds] 18:06 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds] 18:09 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 18:39 -!- Waldo17 [~Waldo@121.143.182.103] has joined #c-lightning 18:39 < Waldo17> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 18:39 < Waldo17> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ 18:39 < Waldo17> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate 18:39 < Waldo17> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ 18:40 -!- Waldo17 [~Waldo@121.143.182.103] has quit [Remote host closed the connection] 18:41 -!- nou [~nou@221.239.33.82] has joined #c-lightning 18:41 < nou> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 18:41 < nou> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ 18:41 < nou> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate 18:41 < nou> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ 18:42 -!- nou [~nou@221.239.33.82] has quit [Remote host closed the connection] 18:44 -!- Tabmow16 [~Tabmow@softbank126078094067.bbtec.net] has joined #c-lightning 18:44 -!- Tabmow16 [~Tabmow@softbank126078094067.bbtec.net] has quit [Remote host closed the connection] 18:49 -!- siniStar [~siniStar@crr06-4-82-247-76-10.fbx.proxad.net] has joined #c-lightning 18:49 < siniStar> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 18:49 < siniStar> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ 18:49 < siniStar> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate 18:49 < siniStar> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ 18:50 -!- siniStar [~siniStar@crr06-4-82-247-76-10.fbx.proxad.net] has quit [Remote host closed the connection] 18:55 -!- eido1on [~eido1on@218.52.99.31] has joined #c-lightning 18:55 < eido1on> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 18:55 < eido1on> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ 18:55 < eido1on> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate 18:55 < eido1on> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ 18:55 -!- conno [~conno@cpe-74-72-170-105.nyc.res.rr.com] has joined #c-lightning 18:55 -!- eido1on [~eido1on@218.52.99.31] has quit [Killed (Unit193 (Spam is not permitted on freenode.))] 18:56 -!- conno [~conno@cpe-74-72-170-105.nyc.res.rr.com] has quit [Remote host closed the connection] 18:58 -!- mode/#c-lightning [+o rusty] by ChanServ 19:00 -!- sawdey21 [~sawdey21@59.16.193.79] has joined #c-lightning 19:00 < molz> rusty, we need +r for this channel :) these idiotic spammers have been going around so many channels 19:00 -!- sawdey21 [~sawdey21@59.16.193.79] has quit [Read error: Connection reset by peer] 19:04 <@rusty> molz: that seems a bit fascist, though. 19:05 < molz> rusty, you mean making this channel +r? 19:05 <@rusty> molz: yeah... 19:05 < molz> well i don't think so 19:05 <@rusty> molz: I can't tell how many current people that would remove.... 19:05 < molz> rusty no it won't 19:06 < molz> if they're already here they're here 19:06 <@rusty> molz: but they won't be able to rejoin AFAICT, until they register their nick? 19:06 < molz> those spammers have been in every bitcoin channel i'm in 19:06 < molz> if they keep coming back i'll just have to leave 19:06 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 240 seconds] 19:07 < molz> rusty, right but im saying if the spammers keep coming back we might need it for a while to deter those spammers away 19:07 < molz> doesn't mean we should have +r permanently 19:07 <@rusty> molz: it seems to happen every few years. The ops seems to get on top of it and it goes away, in my experience. 19:08 < molz> no they haven't gone away :( 19:09 < molz> the dossing might have gone away but not spammers 19:11 <@rusty> molz: how long has this spam been going on? I think it's the first time we've had it in this channel. 19:11 < molz> let's see.. about 4 or 5 days now 19:13 <@rusty> molz: I guess we've been lucky: today is the first time here and in lightning-dev. Let's set +r for now, and see.... 19:13 -!- mode/#c-lightning [+r] by rusty 19:15 < molz> thanks, rusty, if you look at #bitcoin-core-dev they have to use +r the last several days because of these spammers that would give false positive to windows defender 19:19 < roasbeef> depending on what github bot you have, it may not be able to post anymore due to +r 19:20 < molz> roasbeef, if github bots are registered, they're ok? 19:21 < molz> im surprised they found these smaller channels but i guess they got run out of big channels now 19:23 < ovoldemorto> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 19:23 < ovoldemorto> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ 19:23 < ovoldemorto> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate 19:23 < ovoldemorto> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ 19:24 <@rusty> molz: ? 19:25 < jb55> clearly we need proof of work freenode registrations 19:25 < molz> i give up 19:26 < molz> i'll be back when summer is over or those spammers are dead 19:26 -!- molz [~IRCIdent@unaffiliated/molly] has left #c-lightning ["Leaving"] 19:26 <@rusty> molz: they didn't join the channel; this is because I set the mode up for the github bot to voice without having to join. Will fix that too... 19:26 < jb55> ah 19:27 < Ritche2> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 19:27 < Ritche2> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ 19:27 < Ritche2> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate 19:27 < Ritche2> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ 19:27 <@rusty> FFS... 19:27 < jb55> back to coding 19:28 < jb55> and by coding I mean staring at CI until it passes 19:29 <@rusty> I can't even remember the github hook setup. What a waste of my time, this is exaclty why I should have just kept ignoring it. 19:32 -!- mode/#c-lightning [+n] by ChanServ 19:38 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 19:58 <@rusty> jb55: status flags a great idea, but I don't think they can be a single word like this. How will a JSON aPI consumer react if we add a new status word? 19:59 < jb55> rusty: should it be a list of words? 20:01 < jb55> or comma separated 20:03 < jb55> that's why my test does `assert "syncing" in getinfo()["status"]` instead of `assert "syncing" == getinfo()["status"], but it may not be clear to api consumers that it could have multiple statuses... 20:05 < jb55> an array instead of a string might be the least surprising... 20:14 <@rusty> jb55: I'm trying to think what other status we could add. Maybe one for when bitcoind is being unresponsive, for example, or when we're dazed and confused and have lost funds. I guess the q. is, do we want a broad 'status' or individual fields? 20:17 < jb55> like scrap flags and just use a single enum + string? 20:20 -!- qubenix [~qubenix@185.212.170.51] has quit [Remote host closed the connection] 20:20 -!- qubenix [~qubenix@185.212.170.51] has joined #c-lightning 20:22 <@rusty> jb55: We could add 'still-syncing' : 'true' to the JSON, but I feel that's not great either. 20:25 <@rusty> jb55: so IOW, either we need a single field, or a JSON array here. If we go for a single field, then the code becomes simpler because we can just reach into topology to see if we're synced rather than having a bitmap in struct lightningd. It comes down to whether there really will be other statuses... 20:27 < jb55> rusty: I was just thinking due to the concurrency I wouldn't want the statuses stomping over each other. that's assuming there will be other statuses... 20:28 <@rusty> jb55: no concurrency, we're good :) 20:30 < jb55> kk 20:43 <@rusty> jb55: Can you expand on your comment 'https://github.com/ElementsProject/lightning/pull/1777/commits/a9c4897de8ea131c22fcb48e35eff057981fab7b' here? 20:43 -!- arowser [~arowser1@93.179.99.5.16clouds.com] has joined #c-lightning 20:44 < jb55> rusty: was just trying to understand that part of the code, perhaps I'm just unsure what role risk is playing in routing. I'm sure that's written down somewhere... 20:45 <@rusty> Well, that direct check is just double-checking we're not going to overflow the later math steps. 20:46 <@rusty> jb55: for the others, we basically have a 'risk premium', which we add to the cost of routing through a channel. 20:46 <@rusty> (We ahve to track it separately, as the risk premium doesn't alter the fees we pay, unlike the real fee) 20:58 < jb55> rusty: if the channel had *just* enough capacity but would go over due to risk, shouldn't that edge be discarded too? 20:58 < jb55> line 402 20:58 < jb55> oh wait 20:58 < jb55> hmm 20:58 <@rusty> jb55: no, why? We're eliminating them only because it saves time trying and them failing it. 20:59 <@rusty> jb55: unrelated, there should be some ramp-up penalty for when we're trying to use more than 5(?)% of a channel, since it's likely to fail... 21:00 < jb55> rusty: I'm probably still misunderstanding the risk thing, I'll read through the code/docs some more. 21:03 <@rusty> jb55: it's a measure of how long the node wants to add to the delay. 21:03 <@rusty> jb55: ie. we prefer low-timeout routes to high-timeout ones. 21:03 <@rusty> jb55: interestingly, the getroute man page covers thsi. 21:04 < jb55> rusty: oh I missed that, nice. will read. thanks! 21:17 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 21:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 21:43 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 22:01 -!- grubles_ [~grubles@unaffiliated/grubles] has joined #c-lightning 22:02 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 264 seconds] 22:04 -!- molz [~IRCIdent@unaffiliated/molly] has joined #c-lightning 22:04 < molz> rusty, i found out ovoldemorto wasn't a registered spammer, he took the name of a registered person and spammed it here 22:05 < molz> evidently none of these spammers are registered 22:06 < molz> what we can do is when we get a flood spam, you can do this: +q $~a and that will mute them, i asked the freenode staff how to deal with these spammers 22:11 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 22:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer] 22:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 22:30 -!- froyer [~froyer@124.19.31.4] has quit [Remote host closed the connection] 22:45 -!- grubles_ [~grubles@unaffiliated/grubles] has quit [Ping timeout: 256 seconds] 22:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer] 23:38 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning