Pages:
Author

Topic: ... - page 32. (Read 61015 times)

full member
Activity: 196
Merit: 100
August 19, 2015, 06:15:07 PM
Why does Hearn want to cram huge controversial poison-pill commits into XT along with the popular blocksize commit of Gavin's is the real question.

It's like those politicians cramming all the surveillance shit in the "Schumer Bill For The Protection of Widows Orphans and Kiddies."

Take something that may need to be done in order to make for a brighter future and then line it full of shit in the fine print.

You can thank Theymos for that. Its like you'r given a book. You can see the title but you cant read the book.

Then you're asked to give opinion of the book.

Sweet isnt it?
legendary
Activity: 4018
Merit: 1250
Owner at AltQuick.com
August 19, 2015, 06:09:45 PM
Why does Hearn want to cram huge controversial poison-pill commits into XT along with the popular blocksize commit of Gavin's is the real question.

It's like those politicians cramming all the surveillance shit in the "Schumer Bill For The Protection of Widows Orphans and Kiddies."

Take something that may need to be done in order to make for a brighter future and then line it full of shit in the fine print.
full member
Activity: 196
Merit: 100
August 19, 2015, 06:06:26 PM
Why does Hearn want to cram huge controversial poison-pill commits into XT along with the popular blocksize commit of Gavin's is the real question.

It's like those politicians cramming all the surveillance shit in the "Schumer Bill For The Protection of Widows Orphans and Kiddies."

Its a rule that you can turn off anytime. Reason its a controversy because someone make it be.

The XT was under DDoS attack, he had to write a defense mechanism quick. This feature does not affect anyone's privacy. You cant let emotion and prejudice to blind you
sr. member
Activity: 247
Merit: 250
August 19, 2015, 06:05:58 PM
IF XT wins it will bring on so many changes that the Bitcoin we thought we knew and had, will be something completely different. Be prepared for a fully centralised coin should it happen that XT gains consensus.

Whoa!! Hang on. There are lies and damned lies. How did you reach the conclusion that bitcoin will end up being 'centralized' if XT gains majority?  
hero member
Activity: 826
Merit: 1000
August 19, 2015, 06:05:43 PM
Why does Hearn want to cram huge controversial poison-pill commits into XT along with the popular blocksize commit of Gavin's is the real question.

It's like those politicians cramming all the surveillance shit in the "Schumer Bill For The Protection of Widows Orphans and Kiddies."
Again point to it. It is impossible to show that something doesn't exist since there is nowhere to point to that shows that. But if you show me where you think it is I can show you why you are wrong... To this point none did that.
legendary
Activity: 3920
Merit: 2349
Eadem mutata resurgo
August 19, 2015, 06:02:34 PM
Why does Hearn want to cram huge controversial poison-pill commits into XT along with the popular blocksize commit of Gavin's is the real question.

It's like those politicians cramming all the surveillance shit in the "Schumer Bill For The Protection of Widows Orphans and Kiddies."
hero member
Activity: 826
Merit: 1000
August 19, 2015, 05:55:05 PM
It would be such a damning move to insert such tracking code without telling anyone, that I don't think they'd do it. It's not like every bitcoiner is a total noob especially the hackers and thieves.

And I'm not even totally against IP blocking, maybe, finally some recourse for victims of theft, but it does go against one of the fundamental principals of BTC so it would need to get a huge concensus first
What tracking? Please let me know... If you are talking about leaking IP when running proxy and TOR that was in proposed QT(core) code but not in XT.

And there is no IP blocking. To this moment none pointed to the code that do that.

Also I'm interested how IP blocking will help victims of theft...
Why don't you read the code instead of post after post of misinformation? It clearly bans by IP, that isn't even in question.
Yes I did and there is no banning. But you can't point to something that is not there so I can't help you. But you can say where the code is doing that and I will explain to you why you are wrong...
// A group of logically related IP addresses. Useful for banning or deprioritising
// sources of abusive traffic/DoS attacks.
struct CIPGroupData {
    std::string name;
    // A priority score indicates how important this group of IP addresses is to this node.
    // Importance determines which group wins when the node is out of resources. Any IP
    // that is not in a group gets a default priority of zero. Therefore, groups with a priority
    // of less than zero will be ignored or disconnected in order to make room for ungrouped
    // IPs, and groups with a higher priority will be serviced before ungrouped IPs.
    int priority;

//! Whether this peer should be disconnected and banned (unless whitelisted).
    bool fShouldBan;

That is just one segment describing that section of code, there are literally thousands of lines of code that deal with banning.
You are a liar.
No you don't know how to read a code. This is a comment. But you can also read a comments... But you can't read just one. EDIT:(Just to be more clear) "It describes for what it can be used but that doesn't mean it is used for that. So go and find a line that says this bans IPs."

What code dose(if you are read it) is when node is attacked by TOR DOS it just drops any TOR connection in exchange for not TOR connection. And for this to even happen there needs to be 125 connections to a node. This is not banning... This replace the need to block TOR with FW permanently since XT nodes do get a lot of attacks from TOR. So it is a good thing for TOR.

EDIT2: You do know that the comment you posted is not in https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23

This part:

//! Whether this peer should be disconnected and banned (unless whitelisted).
    bool fShouldBan;

I can't find it...
full member
Activity: 196
Merit: 100
August 19, 2015, 05:53:52 PM
It would be such a damning move to insert such tracking code without telling anyone, that I don't think they'd do it. It's not like every bitcoiner is a total noob especially the hackers and thieves.

And I'm not even totally against IP blocking, maybe, finally some recourse for victims of theft, but it does go against one of the fundamental principals of BTC so it would need to get a huge concensus first

I can ensure you no IP blocking or bitcoin blacklist bullshit.

This FUD is a test of bitcoin community, and we failed miserably.

If we had a FUD like this in 2011, i bet you the second post would be "Gtfo"
hero member
Activity: 826
Merit: 1000
August 19, 2015, 05:46:10 PM
It would be such a damning move to insert such tracking code without telling anyone, that I don't think they'd do it. It's not like every bitcoiner is a total noob especially the hackers and thieves.

And I'm not even totally against IP blocking, maybe, finally some recourse for victims of theft, but it does go against one of the fundamental principals of BTC so it would need to get a huge concensus first
What tracking? Please let me know... If you are talking about leaking IP when running proxy and TOR that was in proposed QT(core) code but not in XT.

And there is no IP blocking. To this moment none pointed to the code that do that.

Also I'm interested how IP blocking will help victims of theft...
Why don't you read the code instead of post after post of misinformation? It clearly bans by IP, that isn't even in question.
Yes I did and there is no banning. But you can't point to something that is not there so I can't help you. But you can say where the code is doing that and I will explain to you why you are wrong...
hero member
Activity: 826
Merit: 1000
August 19, 2015, 05:44:05 PM
No it is not. If you don't believe me I guess you would believe https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010388.html

EDIT: It is from QT(core) proposed code. XT has fixes that solves the problem. And to this moment I didn't see a blocking code. But you are welcome to point to it.
This is the BitcoinXT commit, its in the current version https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23

Peter Todd:

Oh, and I just checked, and Mike's original pull-req for the Tor
blacklist didn't include the proxy disable code; what's in master != the
pull-req, so the OP may have been looking at the wrong code by accident.

So you say Peter Todd don't know what he is talking about?
hero member
Activity: 826
Merit: 1000
August 19, 2015, 05:38:02 PM
It would be such a damning move to insert such tracking code without telling anyone, that I don't think they'd do it. It's not like every bitcoiner is a total noob especially the hackers and thieves.

And I'm not even totally against IP blocking, maybe, finally some recourse for victims of theft, but it does go against one of the fundamental principals of BTC so it would need to get a huge concensus first
What tracking? Please let me know... If you are talking about leaking IP when running proxy and TOR that was in proposed QT(core) code but not in XT.

And there is no IP blocking. To this moment none pointed to the code that do that.

Also I'm interested how IP blocking will help victims of theft...
legendary
Activity: 1456
Merit: 1010
Ad maiora!
August 19, 2015, 05:30:46 PM
It would be such a damning move to insert such tracking code without telling anyone, that I don't think they'd do it. It's not like every bitcoiner is a total noob especially the hackers and thieves.

And I'm not even totally against IP blocking, maybe, finally some recourse for victims of theft, but it does go against one of the fundamental principals of BTC so it would need to get a huge concensus first
hero member
Activity: 826
Merit: 1000
August 19, 2015, 05:22:44 PM
The fact that theymos went as far as to sticky this thread which is yet another pathetic lie (on par with the XT is an altcoin fallacy) shows how fucking miserable he is.

There is no banning or blacklisting. It's a form of DDos protection.
This thread is not stickied.

You're right, it's on top and looked like to be stickied as the wider line below separates them from the rest. Sorry.
It's still questionable, why this thread wasn't moved to the Altcoin section. Since according to theymos, we are talking about an Altcoin here.
Maybe it is, because he is hypocrite, but who knows?
This is a threat to the core values of Bitcoin, it's important for Bitcoiners to know before electing to support a BitcoinXT fork. If BitcoinXT forked with the code it has now it might ruin the Bitcoin market, so it's obviously quite relevant.
But it is not relevant since this everything about banning or IP leaking is a lie... To this moment none show part of a code that do one or another. Well in XT code. They found it in QT proposed code. But QT is core...
This is directly from the current version of Bitcoin XT. Why are you spreading misinformation?
No it is not. If you don't believe me I guess you would believe https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010388.html

EDIT: It is from QT(core) proposed code. XT has fixes that solves the problem. And to this moment I didn't see a blocking code. But you are welcome to point to it.
hero member
Activity: 826
Merit: 1000
August 19, 2015, 03:36:22 PM
The fact that theymos went as far as to sticky this thread which is yet another pathetic lie (on par with the XT is an altcoin fallacy) shows how fucking miserable he is.

There is no banning or blacklisting. It's a form of DDos protection.
This thread is not stickied.

You're right, it's on top and looked like to be stickied as the wider line below separates them from the rest. Sorry.
It's still questionable, why this thread wasn't moved to the Altcoin section. Since according to theymos, we are talking about an Altcoin here.
Maybe it is, because he is hypocrite, but who knows?
This is a threat to the core values of Bitcoin, it's important for Bitcoiners to know before electing to support a BitcoinXT fork. If BitcoinXT forked with the code it has now it might ruin the Bitcoin market, so it's obviously quite relevant.
But it is not relevant since this everything about banning or IP leaking is a lie... To this moment none show part of a code that do one or another. Well in XT code. They found it in QT proposed code. But QT is core...
full member
Activity: 196
Merit: 100
August 19, 2015, 03:21:36 PM
The fact that theymos went as far as to sticky this thread which is yet another pathetic lie (on par with the XT is an altcoin fallacy) shows how fucking miserable he is.

There is no banning or blacklisting. It's a form of DDos protection.
This thread is not stickied.

You're right, it's on top and looked like to be stickied as the wider line below separates them from the rest. Sorry.
It's still questionable, why this thread wasn't moved to the Altcoin section. Since according to theymos, we are talking about an Altcoin here.
Maybe it is, because he is hypocrite, but who knows?

Even on reddit, they intentionally leave it and not deleting it.


As for hypocrite? I dont know but take a look:

It's often repeated that Satoshi intended to remove "the limit" but I always understood that to be the 500k maximum generation soft limit... quite possible I misunderstood, but I don't understand why it would be a hardforking protocol rule otherwise.

Satoshi definitely intended to increase the hard max block size. See:
https://bitcointalksearch.org/topic/patch-increase-block-size-limit-1347

I believe that Satoshi expected most people to use some sort of lightweight node, with only companies and true enthusiasts being full nodes. Mike Hearn's view is similar to Satoshi's view.

I strongly disagree with the idea that changing the max block size is a violation of the "Bitcoin currency guarantees". Satoshi said that the max block size could be increased, and the max block size is never mentioned in any of the standard descriptions of the Bitcoin system.

IMO Mike Hearn's plan would probably work. The market/community would find a way to pay for the network's security, and it would be easy enough to become a full node that the currency wouldn't be at risk. The max block size would not truly be unlimited, since miners would always need to produce blocks that the vast majority of full nodes and other miners would be able and willing to process in a reasonable amount of time.

However, enforcing a max block size is safer. It's not totally clear that an unlimited max block size would work. So I tend to prefer a max block size for Bitcoin. Some other cryptocurrency can try the other method. I'd like the limit to be set in a more decentralized, free-market way than a fixed constant in the code, though.

So, the wiki should be changed, right?

It's not yet known how this issue will be handled. The wiki describes one possibility, and this work shouldn't be removed.

hero member
Activity: 714
Merit: 500
August 19, 2015, 03:14:51 PM
The fact that theymos went as far as to sticky this thread which is yet another pathetic lie (on par with the XT is an altcoin fallacy) shows how fucking miserable he is.

There is no banning or blacklisting. It's a form of DDos protection.
This thread is not stickied.

You're right, it's on top and looked like to be stickied as the wider line below separates them from the rest. Sorry.
It's still questionable, why this thread wasn't moved to the Altcoin section. Since according to theymos, we are talking about an Altcoin here.
Maybe it is, because he is hypocrite, but who knows?
sr. member
Activity: 437
Merit: 250
August 19, 2015, 03:13:37 PM

Where is a banning part. This only download a list if you are not using proxy or TOR. No banning... I asked for banning part...

And the rest is as you say same as QT but you just don't like it...

I meant it was standard for most modern software to identify itself in the useragent, Bitcoin core doesn't identify itself to torproject.org like this. Sorry, I edited the post for clarity. I haven't commented on the "banning" thing because right now it's a list of IPs for connection priority reasons, I'm just voicing concern on a separate but related issue.
You are right. I assumed to much from your comment. Well if you are using TOR or proxy this will not happen. Peter Todd is source for this. And if you are not using any of this two things you probably don't care. And if you read documentation you can see that you can also disable download....

True, true.
hero member
Activity: 886
Merit: 1013
August 19, 2015, 03:11:31 PM
The fact that theymos went as far as to sticky this thread which is yet another pathetic lie (on par with the XT is an altcoin fallacy) shows how fucking miserable he is.

There is no banning or blacklisting. It's a form of DDos protection.
This thread is not stickied.

You're right, it's on top and looked like to be stickied as the wider line below separates them from the rest. Sorry.
hero member
Activity: 826
Merit: 1000
August 19, 2015, 03:08:14 PM

Where is a banning part. This only download a list if you are not using proxy or TOR. No banning... I asked for banning part...

And the rest is as you say same as QT but you just don't like it...

I meant it was standard for most modern software to identify itself in the useragent, Bitcoin core doesn't identify itself to torproject.org like this. Sorry, I edited the post for clarity. I haven't commented on the "banning" thing because right now it's a list of IPs for connection priority reasons, I'm just voicing concern on a separate but related issue.
You are right. I assumed to much from your comment. Well if you are using TOR or proxy this will not happen. Peter Todd is source for this. And if you are not using any of this two things you probably don't care. And if you read documentation you can see that you can also disable download....
copper member
Activity: 3948
Merit: 2201
Verified awesomeness ✔
August 19, 2015, 03:06:53 PM
The fact that theymos went as far as to sticky this thread which is yet another pathetic lie (on par with the XT is an altcoin fallacy) shows how fucking miserable he is.

There is no banning or blacklisting. It's a form of DDos protection.
This thread is not stickied.
Pages:
Jump to: