< bitcoin-git> [bitcoin] fanquake closed pull request #21249: doc: Add Whitepaper in Docs (master...whitepaper) https://github.com/bitcoin/bitcoin/pull/21249
< bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/828bb776d29c...5bb64acd9d3c
< bitcoin-git> bitcoin/master fa330d8 MarcoFalke: ci: Avoid invoking curl on the host
< bitcoin-git> bitcoin/master 5bb64ac fanquake: Merge #21243: ci: Avoid invoking curl on the host
< bitcoin-git> [bitcoin] fanquake merged pull request #21243: ci: Avoid invoking curl on the host (master...2102-ciCurl) https://github.com/bitcoin/bitcoin/pull/21243
< bitcoin-git> [bitcoin] theStack opened pull request #21250: build: make HAVE_O_CLOEXEC available outside LevelDB (bugfix) (master...2021-02-build-pass-have_o_cloexec) https://github.com/bitcoin/bitcoin/pull/21250
< bitcoin-git> [bitcoin] x00x00 opened pull request #21251: doc: Add whitepaper with images in Docs (master...whitepaper) https://github.com/bitcoin/bitcoin/pull/21251
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #21252: test: Add missing wait for sync to feature_blockfilterindex_prune (master...2102-testFix) https://github.com/bitcoin/bitcoin/pull/21252
< bitcoin-git> [bitcoin] fanquake closed pull request #21251: doc: Add whitepaper with images in Docs (master...whitepaper) https://github.com/bitcoin/bitcoin/pull/21251
< hebasto> Talkless: for all user-visible strings we must use `tr()`; also there is a dedicated channel ##bitcoin-core-gui :)
< bitcoin-git> [bitcoin] prayank23 opened pull request #21253: Add whitepaper link in README.md (master...whitepaper-link) https://github.com/bitcoin/bitcoin/pull/21253
< bitcoin-git> [bitcoin] fanquake closed pull request #21253: Add whitepaper link in README.md (master...whitepaper-link) https://github.com/bitcoin/bitcoin/pull/21253
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #21254: test: Avoid connecting to real network when running tests (master...2102-testNoTelemetry) https://github.com/bitcoin/bitcoin/pull/21254
< bitcoin-git> [bitcoin] fanquake opened pull request #21255: contrib: run test-symbol-check for RISC-V (master...riscv_test_symbol_check) https://github.com/bitcoin/bitcoin/pull/21255
< bitcoin-git> [bitcoin] theStack closed pull request #21250: build: make HAVE_O_CLOEXEC available outside LevelDB (bugfix) (master...2021-02-build-pass-have_o_cloexec) https://github.com/bitcoin/bitcoin/pull/21250
< bitcoin-git> [bitcoin] theStack reopened pull request #21250: build: make HAVE_O_CLOEXEC available outside LevelDB (bugfix) (master...2021-02-build-pass-have_o_cloexec) https://github.com/bitcoin/bitcoin/pull/21250
< bitcoin-git> [bitcoin] percy-g2 opened pull request #21256: Add wp link in README (master...whitepaper-link) https://github.com/bitcoin/bitcoin/pull/21256
< bitcoin-git> [bitcoin] laanwj closed pull request #21256: Add wp link in README (master...whitepaper-link) https://github.com/bitcoin/bitcoin/pull/21256
< achow101> what is with all these people trying to add the whitepaper to the repo?
< luke-jr> fanquake locked one, so maybe he knows
< sipa> i have no idea
< midnight> just people upset at craig
< Biodragon> is this an appropriate channel to ask a question about bitcoin addresses/protocol?
< sipa> Biodragon: no, try https://bitcoin.stackexchange.com
< michaelfolkson> achow101: The latest one was getting quite abusive towards to wumpus (Apologies on behalf of humanity for that wumpus)
< michaelfolkson> I wonder if when closing them a drafted 1 or 2 line statement should be added explaining why they are being closed without review
< michaelfolkson> Something explaining legal uncertainty, many others opening PRs to do exact same thing and not wanting to take up any more reviewer time
< michaelfolkson> That's not to excuse angry comments but may calm them down a touch
< michaelfolkson> "Thank you for your pull request to Bitcoin Core. We have received many similar pull requests to add a link to the white paper but due to legal uncertainty and in the interests of not taking up any more of reviewers' time we will be instantly closing any such pull requests."
< * michaelfolkson> shrugs
< luke-jr> michaelfolkson: doesn't seem to be any basis for legal uncertainty if it's just a link, especially to bitcoin.org where Satoshi himself published it
< phantomcircuit> luke-jr, it's something to fight about and there's no point in fighting so whatever
< michaelfolkson> luke-jr: Should we just add a link to bitcoin.org then? I suggested a StackExchange link https://github.com/bitcoin/bitcoin/pull/21210#discussion_r578425782
< michaelfolkson> But if bitcoin.org is superior from a legal uncertainty perspective maybe we should add that? I'm not entirely sure what is going on behind the scenes with CSW nonsense and I'm certainly no legal expert
< luke-jr> michaelfolkson: shrug. I don't see any harm in a link to bitcoin.org, but it's also not worth fighting about if others disagree.
< luke-jr> the CSW nonsense is pretty irrelevant and unrelated IMO
< luke-jr> michaelfolkson: definitely shouldn't encourage blockchain spam "solutions" tho ;)
< michaelfolkson> What are you referring to? lol
< jb55> guessing the pdf in the utxo set :P
< michaelfolkson> I don't think Luke is a fan of the whitepaper being encoded in a "m of n multisig Tx with 947 outputs" :)
< jb55> who needs s3...
< luke-jr> michaelfolkson: indeed, that's strictly abusive of Bitcoin and harms the entire network permanently.
< michaelfolkson> Regardless if there is no legal uncertainty with the bitcoin.org link we should probably just link to that. Or respond with a drafted statement to closed PRs to calm the anger
< michaelfolkson> People seem to be getting very upset
< sipa> can we just drop this stupid whitepaper nonsense?
< sipa> it's everywhere on the internet
< sipa> this is just an enormous waste of time
< michaelfolkson> We can obviously drop it here. But people who aren't here keep opening PRs and then responding angrily when they are closed
< sipa> i'm sure they'll get bored
< phantomcircuit> michaelfolkson, those people are not your friends