< aj> BlueMatt: 80x24 is the one true terminal size, anything larger is sheer extravagance :P
< sipa> 80x25, with one status line, ok?
< * sipa> remebers GW-BASIC
< aj> is the status line in the window title?
< sipa> no
< aj> oh, is it part of the 25 lines?
< aj> that's how it was with gw-basic, right?
< aj> yes, brilliant
< sipa> yeah
< sipa> you could optionally disable the status line and have the entire 2000 character area available!
< sipa> including 3 bit foreground color flag, 3 bit background color flag, bright flag, and blinking flag, individually settable per character
< fanquake> sipa: you could just about block the author of #16662. That's the 3rd or 4th time they've turned up asking for help writing an alt.
< gribble> https://github.com/bitcoin/bitcoin/issues/16662 | Error , run " make " , · Issue #16662 · bitcoin/bitcoin · GitHub
< fanquake> Or maybe that's too harsh.
< fanquake> luke-jr: I can backport #15968 into 0.17.2, as it should be in 0.18 already
< gribble> https://github.com/bitcoin/bitcoin/issues/15968 | Fix portability issue with pthreads by grim-trigger · Pull Request #15968 · bitcoin/bitcoin · GitHub
< roasbeef> so i've noticed that at times the DNS seeds (when using filtering) will return results for a particualr service bit, but once connected out, the peers advertise a distinct set (bit not actually there)
< roasbeef> is this a result of the polling interval? or some filtering bug in the seed itself?
< roasbeef> an example is asking for x49 (full node, segwit, bip 158), but then getting (full node, segwit, partial block history)
< TD-Linux> sipa, your miniscript page doesn't explain the difference between the policy language and miniscript
< TD-Linux> might be nice to add a little blurb about it before you hit the policy compiler box
< sipa> yeah good point
< harding> luke-jr: do you still have a git repository with your seeder index results over time? If so, maybe send roasbeef the URL so he can look up the history of the nodes with inconsistent service bits.
< luke-jr> harding: yes, but GitLab limited its size so there's no way to get the last few months
< luke-jr> it's 13 GB now
< bitcoin-git> [bitcoin] fanquake opened pull request #16665: scripts: move update-translations.py to maintainer-tools repo (master...move_maintainer_scripts) https://github.com/bitcoin/bitcoin/pull/16665
< luke-jr> roasbeef: grab https://gitlab.com/Luke-Jr/my-bitcoin-dnsseed-historical-seeds.txt and I'll see about getting you access to pull the rest ;)
< sipa> luke-jr: create incremental git bundles
< sipa> and out those somewhere :)
< bitcoin-git> [bitcoin] BIAgents opened pull request #16666: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/16666
< bitcoin-git> [bitcoin] fanquake closed pull request #16666: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/16666
< tryphe> so much for a PR getting a sweet number
< fanquake> Had more spam PRs than legit PRs over the past few days
< tryphe> fanquake, sure seems like it. i wonder if there's an easy way to make the git bot just cancel commits that container the default github PR message.
< tryphe> s/container/contain*
< bitcoin-git> [bitcoin] fanquake opened pull request #16667: build: remove mingw linker workaround from win gitian descriptor (master...remove_mingw_linker_workaround) https://github.com/bitcoin/bitcoin/pull/16667
< bitcoin-git> [bitcoin] fanquake opened pull request #16669: [WIP] build: use new fork of osslsigncode for windows gitian signing (master...osslsigncode_2_0) https://github.com/bitcoin/bitcoin/pull/16669
< luke-jr> instagibbs: if say someone had a PR that added a new TxMempoolInfo construction with the current fields, they'd end up with something very broken silently compiled?
< luke-jr> or the opposite, someone based the new construction on this PR, and it got backported sloppily
< instagibbs> ok is there something that would make you feel better? The current logic is broken.
< instagibbs> wouldn't the increased number of fields make it impossible to compile if someone was using the old version?
< luke-jr> at least in C, zeros are implicitly added on the end :/
< instagibbs> CFeeRate field is also gone, so typing should also save the implementer?>
< luke-jr> eh? it isn't gone
< luke-jr> you just renamed it
< instagibbs> (yuck re:c)
< luke-jr> is it supposed to be a CAmount?
< instagibbs> wat, let me re-read my code
< instagibbs> maybe o_0
< luke-jr> (in which case, I'm not sure how implicit conversions work here)
< luke-jr> using an explicit constructor would probably solve at least backports
< instagibbs> yeah that's a bug(well it "works" but is the wrong type)
< instagibbs> yep agreed, let me fix
< provoostenator> sipa: okok, finally installed Quassel :-)
< kallewoof> GW-BASIC would hang my dad's 286 if I ever accidentally hit shift 4 instead of alt-gr 4 to get $. Sad times writing code and have to restart the machine all the time.
< kallewoof> I can't believe anybody else knows about GW-BASIC tho. I honestly thought it was my own personal secret. Or a bad nightmare. Or both.
< sipa> kallewoof: i learned to program in it
< kallewoof> Me too! I guess it was more popular than I realized.
< luke-jr> were there other options than GW-BASIC back then? :p
< luke-jr> AFAIK QBASIC only came a few years later
< kallewoof> luke-jr: Without internet and other ways to communicate, I'm afraid my knowledge on what was available was very limited (I was also single-digit years old). ;P
< luke-jr> same
< luke-jr> CompuServ and such came later
< luke-jr> in the meantime, I had to write BASIC programs to simulate basically a BBS
< kallewoof> I think I tried to write a bot that would talk back. I had great plans for my future AI overlords back then.
< luke-jr> XD
< luke-jr> kallewoof: better than Dr. Sbaitso?
< kallewoof> luke-jr: Haha, most likely not
< luke-jr> HELLO KALLE. MY NAME IS DOCTOR SBAITSO. I AM HERE TO HELP YOU. SAY WHATEVER IS ON YOUR MIND FREELY. OUR CONVERSATION WILL BE KEPT IN STRICT CONFIDENCE. MEMORY CONTENTS WILL BE WIPED OFF AFTER YOU LEAVE. SO, TELL ME ABOUT YOUR PROBLEMS.
< BlueMatt> aj: lol nahhhhh anything less than 420x100 is a joke of a terminal :p
< sipa> 190x58 here
< andytoshi> 254x76 ... but my matt-style terminal (which slows my reading rate by well over 50%, the font is so small) is 318x98
< andytoshi> but i still try to keep all my lines under 80.
< luke-jr> 155x30 apparently
< bitcoin-git> [bitcoin] MarcoFalke pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/e00ecb3d7aae...70b12af87eb0
< bitcoin-git> bitcoin/master 54aaa78 Daniel Edgecumbe: RPC: add weight to mempool entry output
< bitcoin-git> bitcoin/master 9c9cc2b Daniel Edgecumbe: qa: Add RPC tests for weight in mempool entry
< bitcoin-git> bitcoin/master 17d178f fanquake: doc: add release-notes for getmempoolentry weight field addition
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #16647: rpc: add weight to getmempoolentry output (master...rpc_mempoolentry_weight_rebased_release_notes) https://github.com/bitcoin/bitcoin/pull/16647
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #16670: util: Add Join helper to join a list of strings (master...1908-utilStringJoin) https://github.com/bitcoin/bitcoin/pull/16670
< luke-jr> pretty sure we already had one of those?
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #16671: doc: Prepare intermediate 0.19.0 release notes (master...1908-docReleaseNotes0.19) https://github.com/bitcoin/bitcoin/pull/16671
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #16671: doc: Prepare intermediate 0.19.0 release notes (master...1908-docReleaseNotes0.19) https://github.com/bitcoin/bitcoin/pull/16671
< bitcoin-git> [bitcoin] LarryRuane opened pull request #16673: Relog configuration args on debug.log rotation (master...relog-args-on-rotation) https://github.com/bitcoin/bitcoin/pull/16673