< jgarzik>
Perhaps duplicative, but another one didn't stick
< tripleslash>
and already seized on by a troll that you didn't provide enough warning. :-/
< phantomcircuit>
jgarzik, ha yeah that brough ina bunch of /xt trolls
< phantomcircuit>
shocking
< jcorgan>
why bother with /r/bitcoin anymore?
< tripleslash>
because it is the defacto?
< tripleslash>
same reason companies still screw with .com when there are plenty of other options
< alpalp>
jcorgan: what are better options?
< jcorgan>
i'm not sure there are any useful public venues for bitcoin related matters any more. i'd say post announcements on a read-only mailing list, say, bitcoin-core-announce, and let responsible people stay on top of announcements about software they run that handles their money.
< jcorgan>
but posting a PSA and notice and immediately getting troll grief just...sucks.
< tripleslash>
An announcement list is probably long overdue, but then the issues of "Who has post access and what" still come up
< phantomcircuit>
jcorgan, the same group of trolls is everywhere
< tripleslash>
you know whatever is decided won't be enough
< alpalp>
jcorgan: it's a handful of idiots
< alpalp>
who are loud
< alpalp>
one guy who thinks mike hearn warned us of this and would have saved us, and he gets downvoted, its not a big deal
< alpalp>
most of the children have moved out of /r/bitcoin anyway
< jcorgan>
meh. i don't know why we keep expecting unpaid but skilled and highly productive volunteers to put up with it.
< alpalp>
What are the odds this guy even runs a node
< tripleslash>
alpalp: he confessed to running xt, so I suppose it depends on your definition of 'node'
< jcorgan>
yeah, assholes are everywhere. engaging them just adds legitimacy, as if you agree anything they have to say is worth your time to respond.
< alpalp>
tripleslash: I have doubts even 1/4 of those who claim to run xt nodes actually do
< tripleslash>
yeah, I saw the number of people paying to have clones run several months ago
< jcorgan>
guys, sorry for instigating this discussion thread. clearly this was the kind of thing happening on #bitcoin-dev that brought about the change to using this channel instead. can we go back to pull requests and releases?
< tripleslash>
+1
< tripleslash>
So there's a .1 coming down to change the default minrelaytxfee?
< phantomcircuit>
jcorgan, ha he deleted his post
< phantomcircuit>
yes we can
< jcorgan>
i'm still interested in understanding what is going on with #6681
< phantomcircuit>
it would be nice if we could unify the memory usage stuff such that there was a single parameter
< * jgarzik>
returns from kid night-night
< jgarzik>
would prefer to keep non-tech discussion of my post on #bitcoin. if there are tech corrections, by all means, post here
< jgarzik>
RE: forum, twitter and reddit can be useful to start getting word out to other forums. reporters watch them etc.
< nanotube>
hm, set up a twitterbot to tweet bitcoin-announce mailing list titles with links to full email body? :)
< tripleslash>
nanotube: twitterbot with release notes for builds that have gone wide release
< wumpus>
looking at stack layouts, two functions stand out in bitcoind, secp256k1_ecmult_gen_context_build with a 221760 byte stack frame and ThreadSocketHandler with 67080. The rest is <8000.
< wumpus>
fortunately, neither is a recursive function
< sipa>
wumpus: the forner is gone is libsecp256k1 master
< cfields>
wumpus: might help to have pushes to that repo announced on irc as well
< michagogo>
cfields: how about .3?
< cfields>
michagogo: doing that next
< michagogo>
k
< wumpus>
cfields: yes, good idea
< tripleslash>
With regard to upnp vuln, its only an issue if you're on untrusted networks. If your local network is only your devices, there's not an issue, correct?
< wumpus>
tripleslash: yes
< wumpus>
tripleslash: although an attacker only needs to run one process on one device on your local network, and it can crash all miniupnpc-using applications on that network
< tripleslash>
unless they've been patched
< wumpus>
right
< cfields>
ah nice, the attach/detach changes were accepted into upstream osslsigncode
< jcorgan>
cfields: can you elaborate on what is wrong with the zmq/windows static build issue? not sure i can help much but would at least like to know how it is breaking.
< michagogo>
Turns out nobody's home atm, so I won't be signing now (and likely not tonight)
< cfields>
jcorgan: i haven't looked into it much. upstream specifically disables win32+static builds for some reason
< cfields>
s/specifically/explicitly/
< jcorgan>
ah, ok
< jcorgan>
that i might be able to dig into
< cfields>
jcorgan: when i first looked into it, i remember thinking "they might just disable since it's uncharted territory for them"
< cfields>
but nothing to substantiate that
< jcorgan>
i will have to set up the cross build environment again here
< jcorgan>
which you help me do once a long time and several workstations ago
< cfields>
jcorgan: make -C depends host=x86_64-w64-mingw32
< cfields>
er, HOST=
< jcorgan>
thanks, i'll figure it out from there
< cfields>
jcorgan: you can just edit depends/packages/packages.mk and add the zmq package unconditionally, so it'll try to build for windows too
< cfields>
then depends should fail for you in the right place
< jcorgan>
got it
< michagogo>
jcorgan: there's a full minimal set of packages you need somewhere in my Reddit package history
< michagogo>
er, comment* history
< jcorgan>
i'll let you know what i come up with
< jcorgan>
well, might just put it in the issue
< michagogo>
Ah, turns out it's extremely minimal
< michagogo>
on a clean install of Ubuntu precise, sudo apt-get install git g++-mingw-w64 autoconf libtool
< michagogo>
Plus nsis if you want to make the installer
< michagogo>
cfields: thanks. Not sure when I'll get around to it, since I won't be home until lateish tonight and the computer's off so I can't remote it, but at some point...
< btcdrak>
could you come to #bitcoin-dev for a few mins to discuss the mailing list policy?
< michagogo>
btcdrak: sorry, can't ATM
< michagogo>
Dividing myself already between family dinner and ##werewolf
< Luke-Jr>
lol
< wumpus>
hehe
< michagogo>
(If anyone doesn't play ##werewolf -- try it!)
< Luke-Jr>
michagogo: I prefer #yandere
< * btcdrak>
doesnt play games :/
< michagogo>
Luke-Jr: I think I've tried a couple different ones
< michagogo>
##werewolf is the biggest, which is an advantage
< michagogo>
Also it's actively developed by multiple people and is very featureful
< GitHub81>
[bitcoin] jmcorgan opened pull request #6810: zmq: point API link to 4.0 as that is what we are conforming to (master...zmq-api-link) https://github.com/bitcoin/bitcoin/pull/6810
< jcorgan>
wumpus: that's a trivial change get a gpg signed commit into the repo
< GitHub99>
[bitcoin] TheBlueMatt opened pull request #6812: Update bluematt-key, the old one is long-since revoked (master...master) https://github.com/bitcoin/bitcoin/pull/6812
< GitHub171>
[bitcoin] dexX7 opened pull request #6813: Support gathering code coverage data for RPC tests with lcov (master...btc-test-lcov-rpc) https://github.com/bitcoin/bitcoin/pull/6813