< CryptoMann> Welkomen
< bitcoin-git> [bitcoin] comradekingu opened pull request #11920: python → Python (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11920
< cluelessperson> bitcoin.org 's downloads are slow as balls
< cluelessperson> why is that?
< jonasschnelli> cluelessperson: use http://bitcoincore.org/bin/?
< cluelessperson> jonasschnelli: thanks, but we should fix the first things users see
< jonasschnelli> Download from http://bitcoin.org/ seems pretty fast on my end
< cluelessperson> bitcoin.org is kinda infuriating
< cluelessperson> needs a "download" link on the homepage
< sipa> well bitcoin.org is not primarily about bitcoin core
< cluelessperson> I guess
< cluelessperson> sipa: I would still make it better
< cluelessperson> "choose your wallet" should be first thing
< sipa> cluelessperson: i'm sure people will appreciate help on https://github.com/bitcoin-dot-org/bitcoin.org
< cluelessperson> jesus christ
< cluelessperson> I'm looking at the Bitcoin Core UI and it needs serious revamping
< cluelessperson> Who made this UI? I have recommendations
< Varunram> cluelessperson: bitcoin-qt?
< cluelessperson> yeah
< cluelessperson> The first thing on the receiving tab should be "Receiving Address: <ADDRESS>" "NEW"
< cluelessperson> This should be DUMB simple for braindead laymen to use, dead and center
< fanquake> cluelessperson open a pull request with your recommended changes.
< cluelessperson> I'm sorry if I'm being insulting
< cluelessperson> fanquake: I don't know C++
< fanquake> There's no doubt the GUI could be more user-friendly, but there's a lack of people willing/able to do the work.
< fanquake> cluelessperson If you can't contribute code, open an issue with recommendations, mockups/screenshots etc.
< fanquake> I think there might even be a few open with new design ideas.
< cluelessperson> fanquake: I'm putting togeether design mockups
< cluelessperson> fanquake: here's what I'm going for
< sipa> cluelessperson: i don't think an address should be shown until you request one
< cluelessperson> sipa: why?
< sipa> it's very hard to prevent reuse otherwise
< cluelessperson> sipa: Have core generate a new address when it detects a transaction come through
< sipa> cluelessperson: that's what we used to do. it makes people freak out their address changed
< cluelessperson> sipa: Or, just have it start out blank, and it won't show you one until you ask for it. :)
< sipa> still shouldn't show it afterwards anymore
< sipa> the whole "this is your address" causes more problems than understanding
< cluelessperson> sipa: then I'll add the subtext, "old addresses are stored in history" and you make them show up in the transactions/history tab
< sipa> an address is something that is per requested paymemt
< sipa> not something "belonging" to you
< cluelessperson> sipa: What?
< cluelessperson> of course addresses belond to you
< sipa> yes, of course they do
< sipa> but i mean people shouldn't see them as such
< sipa> they should see it as an invoice number
< sipa> more than as an account number
< cluelessperson> sipa: Sure, you definitely want to make it easy as hell to use, just toss out a QR code to scan, but you cannot hide it when people want it
< cluelessperson> it's also currently a fundamental of how people understand bitcoin to work.
< sipa> cluelessperson: i don't care about easy as hell
< sipa> if it results in lost funds later
< cluelessperson> sipa: https://i.imgur.com/5L7DLat.png
< cluelessperson> sipa: That's a good resolve to have, you're right, so let's do both. :)
< cluelessperson> Easy as hell AND No losing of funds.
< sipa> i dislike "your current receiving address" :)
< sipa> that sounds like ot's still sometging designed to last for a period of timr
< cluelessperson> sipa: That's just verbiage, I'm absolutely open to changing that and the layout. My mock up is to demonstrate the fundamental requirements that should be on the receiving tab, and the organization that would make sense "no questions asked" to all users.
< sipa> ok
< sipa> sure
< cluelessperson> sipa: I agree with you, what would you like to rename the "current receiving addrss" assuming I myself try to patch together a ... pull request
< cluelessperson> sipa: Thanks for your input, you are absolutely right
< cluelessperson> I'll put more thought into how to handle it as well
< bitcoin-git> [bitcoin] laanwj pushed 11 new commits to 0.15: https://github.com/bitcoin/bitcoin/compare/a69cc077d946...2559a19e6fdb
< bitcoin-git> bitcoin/0.15 6372a75 Jonas Schnelli: [Wallet] always show help-line of wallet encryption calls...
< bitcoin-git> bitcoin/0.15 7026845 Russell Yanofsky: Fix uninitialized URI in batch RPC requests...
< bitcoin-git> bitcoin/0.15 305f768 Russell Yanofsky: Limit AuthServiceProxyWrapper.__getattr__ wrapping...
< bitcoin-git> [bitcoin] canselcik opened pull request #11921: Fixing env variables/arguments in OpenBSD build instructions (master...master) https://github.com/bitcoin/bitcoin/pull/11921
< _destin243> ▄▄▄▄▄▄▄▄▄▄▄▄▄▄ HAPPY NIGGER DAY!! PLEASE SAY HI TO ALL THE DUMB NIGGERS IN #FREENODE...quicktalkeh676te.onion/6697ogwsnbju: twill booyah StopAndDecrypt Lightsword Giszmo dcousens LeMiner2 arubi_ AaronvanW Seven_ roadcrap andytoshi vicenteH puff Emcy ghost43 chjj meshcollider d9b4bef9 quantbot PaulCapest
< _destin243> ▄▄▄▄▄▄▄▄▄▄▄▄▄ HAPPY NIGGER DAY!! PLEASE SAY HI TO ALL THE DUMB NIGGERS IN #FREENODE...quicktalkeh676te.onion/6697dhyyhu: TheV01d dlb76 Seven_ eck fanquake asoltys tripleslash Dyaheon ryan-c chjj sipa lifeofguenter booyah Emcy gaf_ justanotheruser whphhg stevenroose twill zxzzt gribble ghost43 Arokh schnerchi owo
< _destin243> ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ HAPPY NIGGER DAY!! PLEASE SAY HI TO ALL THE DUMB NIGGERS IN #FREENODE...quicktalkeh676te.onion/6697lukcelkfu: c40d9b0753a91f40 Ge0rges victorSN sturles lrvick xHire ryan-c achow101 commavir michagogo pierre_rochard twill unholymachine zxzzt justanotheruser Cory cryptapus peterto
< dlb76> +kb
< bitcoin-git> [bitcoin] JavadSM closed pull request #11895: Moving to python3 (master...master) https://github.com/bitcoin/bitcoin/pull/11895
< bitcoin-git> [bitcoin] PierreRochard opened pull request #11923: Wallet : remove unused fNoncriticalErrors variable from CWalletDB::FindWalletTx (master...2017-12-17-FindWalletTx) https://github.com/bitcoin/bitcoin/pull/11923
< adminj> cluelessperson it can be helpful to draw proposed design changes on top of an existing screenshot, as it makes it easier to understand the relative change. Your last sketch looks completely different from the current look and feel. As much as I'd love a complete revamp, smaller incremental improvements are more likely to actually happen.
< cluelessperson> adminj: that's a good suggestion
< sturles> I have been education my users for a while to use segwit compatible wallets. The result is that now most of my outgoing transactions are to bc1.. and 3.. type addresses, with the change output being the only one to and1...
< sturles> Eoh.
< sturles> to an 1... address.
< sturles> This makes it very easy to single out.
< wumpus> sturles: what wallet are you using?
< sturles> Bitcoin Core.
< wumpus> sturles: with #11403?
< gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub
< provoostenator> (setting up ZNC is a pain...)
< wumpus> if so, you can change the changetype with -changetype
< sturles> Ah, thanks! Don't know why I haven't found this one before.
< sturles> Is it production ready?
< wumpus> definitely not, it needs testing
< sturles> Hmm. :-/
< wumpus> and review and all the things unmerged PR need
< sturles> I don't test much, but when I do I do it in production. :-)
< jonasschnelli> My nighly gitian builds for linux do fail since 1st of december... could be a local issue... but more likely a build thing
< adam_> hey guys
< adam_> does anyone still communicate on herE?
< asdfasdf> I'm here for the first time. I'm just wondering how this works