--- Log opened Fri May 10 00:00:11 2019
00:53 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has quit [Remote host closed the connection]
00:56 < m-schmoock> cdecker: I tell people to use the shipped recent source version of pylightning via env variable, because it has less bugs. also people that ask here, normally have the source compield anyway. if they install it via pip it only offers a older package, right?
00:57 < m-schmoock> cdecker: and i cant merge the autorestart PR :/ restricted or no button. GitHub foo
01:17 <@cdecker> Ok, invited you to a team that has push access to `master`, hopefully this allows you to merge in future
01:17 < m-schmoock> :D nice. thx
01:19 < m-schmoock> shall we close this now? https://github.com/ElementsProject/lightning/issues/2439   or do we keep the (imho cleaner) RPC call 'restartplugin' as a future task?
01:32 <@cdecker> Good point, I closed it ^^
01:32 <@cdecker> We can still revisit a `restartplugin` call later, though in normal operation I wouldn't want to encourage that
01:32 < m-schmoock> sure, cronjob restart plugin for bad code is good idea ^^
01:33 <@cdecker> Uff :-)
01:33 <@cdecker> I'd actually like to be able to mark a plugin as important and kill the daemon if the plugin dies
01:33 < m-schmoock> right
01:33 <@cdecker> With that we'd be almost guaranteed that the plugin doesn't miss something important (notifications or similar)
01:34 <@cdecker> It might be strange for people to expect a plugin to run, only to find out that it crashed days ago
01:34 < m-schmoock> indeed
01:35 < m-schmoock> if (plugin.error && plugin.version % 2) kill   ^^ 
01:39 < m-schmoock> or we add the thing as "dev-restartplugin".... if we have just tooo much time and are bored
01:40 < m-schmoock> the autorestarter is really a very helpful tool
01:41 <@cdecker> Glad you like it, it's actually a sideproduct of another plugin I was trying to write and I got annoyed at having to restart the entire daemon all the time :-)
01:47 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 258 seconds]
02:44 -!- Letze [uid63391@gateway/web/irccloud.com/x-trobpmczefjhiolx] has joined #c-lightning
03:30 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:36 -!- rafalcpp_ is now known as rafalcpp
03:44 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:50 -!- Letze [uid63391@gateway/web/irccloud.com/x-trobpmczefjhiolx] has quit [Ping timeout: 248 seconds]
03:52 -!- Letze [uid63391@gateway/web/irccloud.com/x-qqgtptwtnyglpxsp] has joined #c-lightning
04:57 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has joined #c-lightning
05:33 < fiatjaf> where can I ask for plugins?
05:33 <@cdecker> Here seems like a good place fiatjaf 
05:34 < fiatjaf> I want to build a node that is not officially in the network, but that can send and receive payments through a c-lightning node
05:36 < fiatjaf> so the c-lightning node would have to take incoming payments -- how do you call the onion packet containing payment information? -- and forward them to this external thing in a custom way
05:36 < fiatjaf> and on the other hand take packets from this external thing and send them to the next peer as if it was a normal packet
05:37 < fiatjaf> (this probably doesn't make any sense, I think I'll write this more clearly later and come back here)
05:45 <@cdecker> So you want to have something that can intercept payments as they go through and tell an external system about them?
05:45 <@cdecker> Sounds like the `htlc_accepted` hook that is currently under review is exactly what you want :-)
05:46 <@cdecker> See https://github.com/ElementsProject/lightning/pull/2267 for reference
05:46 <@cdecker> It has some unit tests that may be of interest to you
05:58 < fiatjaf> (I said I was asking for plugins but actually I wanted plugin features. you got it.)
06:03 < fiatjaf> nice, I think that solves everything for the incoming payment case. what about the outgoing case?
06:04 < fiatjaf> I mean: how can I insert an htlc on that plugin?
06:05 < fiatjaf> in other words: is it possible for me to build an onion/htlc/whatever and send it to c-lightning through external means and have it be accepted or rejected according to custom rules and then forward it?
06:06 < fiatjaf> (by "external means" I mean anything other than a normal lightning channel peer connection)
06:06 < fiatjaf> or can I fake that lightning channel peer connection even though there won't be a valid channel?
06:09 <@cdecker> We currently don't have a way to inject a payment into the daemon, but we might be looking into it for the cross-chain payments that bitonic-cjp is working on
06:41 < m-schmoock> cdecker: we should improve on the plugins repo main README.md regarding common installation stuff (like pip install or using the plugins directory with symlinks and such) so the README.md of each individual plugin can just point there for general installation instructions and less repeat the word "plugin" 100 times °_°
07:01 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
07:45 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has quit [Remote host closed the connection]
07:49 <@cdecker> Absolutely
07:52 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
09:34 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 252 seconds]
09:50 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 245 seconds]
09:54 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning
10:07 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning
10:23 -!- Letze [uid63391@gateway/web/irccloud.com/x-qqgtptwtnyglpxsp] has quit [Quit: Connection closed for inactivity]
12:15 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
13:41 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
13:50 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:04 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:18 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:36 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
19:22 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
19:31 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
19:35 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
21:28 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-enavimqrwmsgirdu] has left #c-lightning []
21:31 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-enavimqrwmsgirdu] has joined #c-lightning
22:13 -!- ctrlbreak_MAD [~ctrlbreak@142.162.20.53] has joined #c-lightning
22:16 -!- dmkathayat_ [~quassel@ec2-13-233-97-253.ap-south-1.compute.amazonaws.com] has joined #c-lightning
22:16 -!- adam3us_ [~adam3us@unaffiliated/adam3us] has joined #c-lightning
22:17 -!- dmkathayat [~quassel@ec2-13-233-97-253.ap-south-1.compute.amazonaws.com] has quit [Read error: Connection reset by peer]
22:17 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has quit [Ping timeout: 258 seconds]
22:17 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has quit [Ping timeout: 258 seconds]
22:17 -!- adam3us [~adam3us@unaffiliated/adam3us] has quit [Ping timeout: 258 seconds]
22:20 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 246 seconds]
22:23 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning
--- Log closed Sat May 11 00:00:09 2019