--- Log opened Wed Feb 20 00:00:54 2019
02:32 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-sztoaakskooyefnq] has joined #secp256k1
03:33 < gmaxwell> sipa: ever notice https://github.com/bitcoin-core/secp256k1/issues/436
03:35 < gmaxwell> okay, I got 20 issues closed, someone elses turn now.
03:37 < gmaxwell> (forgive me if I was too agressive at closing something here or there. Don't hesitate to yell at me or reopen.)
03:38 < gmaxwell> I think the sea of open issues was making the entire issue list not so useful.
03:41 < gmaxwell> sipa: I would merge https://github.com/bitcoin-core/secp256k1/pull/550  but I dunno what merge script you're using.
05:17 < andytoshi> i think #292 (add blind sigs) should be closed, and maybe re-opened on -zkp in case you're afraid we'll forget about it (though we won't ;))
05:18 < andytoshi> it seems like since 2015 we've gotten much stricter about not merging things that don't have direct bitcoin/core applicatinos
05:18 < andytoshi> i'll just say that on the issue and close it, you're welcome to re-open
05:21 < gmaxwell> fine with me, there is some other pr where someone is asking for a scalar inverse ... because they are supposidly implementing blind sigs themselves.
05:23 < andytoshi> fwiw nickler is working on it for -zkp I think
05:23 < andytoshi> yeah, i recall that PR, i don't remember if i replied to them or not
06:12 -!- jtimon [~quassel@119.24.134.37.dynamic.jazztel.es] has joined #secp256k1
09:31 -!- jtimon [~quassel@119.24.134.37.dynamic.jazztel.es] has quit [Quit: gone]
11:31 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
14:13 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-sztoaakskooyefnq] has quit [Quit: Connection closed for inactivity]
16:28 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:28 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
16:33 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 264 seconds]
19:30 < gmaxwell> sipa: hey I'd like to merge some trivial improvements that you've acked. But I'd like to maintain consistency with your existing merges. Are you just using the bitcoin core merge script?
19:48 < sipa> yes
19:49 < sipa> and thanks for all the work going through issues and requests
19:55 < gmaxwell> I didn't even know 90% of them were there. :(  I've never had a workflow that let me see stuff happening on github really. I pool, and I wasn't polling issues.
19:55 < gmaxwell> sorry about that, I could have handled a lot of these a long time ago.
19:55 < gmaxwell> poll*
19:56 < gmaxwell> of course, github recently killed their irc bot or I'd suggest that we have every issue/pr open get bot-mentioned here
19:58 < sipa> there is a bot for bitcoin core though, that someone recently wrote
21:03 < gmaxwell> Someone who isn't me, please ack the trivial comment I shoved onto the end of https://github.com/bitcoin-core/secp256k1/pull/516
21:03 < gmaxwell> sipa: andytoshi: nickler
21:06 < gmaxwell> also it's fucking nuts that I can push onto randos master just because they PRed to our repo.
21:25 < gmaxwell> looking at these JNI bindings, I feel kinda uneasy about them. They aren't very high quality.
21:26 < gmaxwell> E.g. currently forcing uncompressed keys (though there is a PR for that), ignoring return values.
23:02 -!- droark [~droark@c-24-21-203-195.hsd1.or.comcast.net] has joined #secp256k1
--- Log closed Thu Feb 21 00:00:55 2019