You only run out when I need you the most.Peter R: #R3KT. Let this be a reminder to ensure that your jokes execute correctly before posting them.
Looks like it's back to posting animated GIFs from the Spherical Cow Farm for me
Topic: Analysis and list of top big blocks shills (XT #REKT ignorers) - page 27. (Read 46564 times)
January 19, 2016, 12:55:39 PM
Stupid stack space You only run out when I need you the most.
Peter R: #R3KT. Let this be a reminder to ensure that your jokes execute correctly before posting them.
Looks like it's back to posting animated GIFs from the Spherical Cow Farm for me
You only run out when I need you the most.Peter R: #R3KT. Let this be a reminder to ensure that your jokes execute correctly before posting them.
Looks like it's back to posting animated GIFs from the Spherical Cow Farm for me
January 19, 2016, 12:54:39 PM
Your coworker sold you all for 2.15 BTC
January 19, 2016, 12:46:14 PM
Uh? Okay 
January 19, 2016, 12:36:00 PM
I have everything. Payrolls, photographs.
Going to publish it soon.
Going to publish it soon.
January 19, 2016, 12:33:18 PM
There would be no war if people weren't selfish and following their own agenda
Well, we agree on something finally. So... when are you lot going to stop DDOSing, Spreading FUD, Lying, Manipulating, and following a whiny & childish scorched earth policy of trying to destroy Bitcoin if you can't control it??
Nobody can control bitcoin.
Only forkers want to destroy bitcoin... by forking it.
The hard fork is going to fail.
Shhh let the deluded Noobs around here and their segregated big blocks multi client Peter r encoded fantaisies going on. Useless people needs their forum drama going on for they at least feel
I know where the office of your team is located and I am going to post it on Wikileaks, soon.
January 19, 2016, 12:31:34 PM
There would be no war if people weren't selfish and following their own agenda
Well, we agree on something finally. So... when are you lot going to stop DDOSing, Spreading FUD, Lying, Manipulating, and following a whiny & childish scorched earth policy of trying to destroy Bitcoin if you can't control it??
Nobody can control bitcoin.
Only forkers want to destroy bitcoin... by forking it.
The hard fork is going to fail.
Shhh let the deluded Noobs around here and their segregated big blocks multi client Peter r encoded fantaisies going on. Useless people needs their forum drama going on for they at least feel
January 19, 2016, 12:19:04 PM
There would be no war if people weren't selfish and following their own agenda
Well, we agree on something finally. So... when are you lot going to stop DDOSing, Spreading FUD, Lying, Manipulating, and following a whiny & childish scorched earth policy of trying to destroy Bitcoin if you can't control it??
Nobody can control bitcoin.
Only forkers want to destroy bitcoin... by forking it.
The hard fork is going to fail.
January 19, 2016, 12:13:51 PM
The 1MB camp has already won do what you want.
This is the truth. I belive in Satoshi nakamoto and His 1MB block size cap.
January 19, 2016, 11:42:59 AM
My friend told my, that Reddit is taken over by big blocks (hard fork) shills.
Evidence: You get IP ban when you insult them.
Evidence: You get IP ban when you insult them.
January 19, 2016, 11:41:01 AM
Obviously, running your code does not always end up with "segmentation fault", it is only a possibility.
Code:
int main()
{
[b]int array[10]; [/b]
array[11] = 0;
printf("stick with core\n");
}
Oops, I was wrong. Because you put the "array" array on the stack, there are no chances for "segmentation fault".
Peter TRoll 'developer' #REKT
The array is neither static nor in a function, so its not on the stack. More likely ( dependent on your setup) its pre-allocated in the programs data section.
The fact that you dont core any time is down to blind luck.
int main() { ... } is not a function?
Look again!
Code:
(gdb) run
Starting program: /home/valiz/petertroll
Breakpoint 1, main () at petertroll.c:6
6 array[11] = 0;
(gdb) info registers rsp
rsp 0x7fffffffe2b0 0x7fffffffe2b0
(gdb) print &array[11]
$2 = (int *) 0x7fffffffe2dc
(gdb) l
1 #include
2
3 int main()
4 {
5 int array[10];
6 array[11] = 0;
7 printf("stick with core\n");
8 }
9
you are correct. for some reason i didnt see that...
January 19, 2016, 11:33:46 AM
My friend told my, that Reddit is taken over by big blocks (hard fork) shills.
Evidence: You get IP ban when you insult them.
Evidence: You get IP ban when you insult them.
January 19, 2016, 09:36:29 AM
Obviously, running your code does not always end up with "segmentation fault", it is only a possibility.
Code:
int main()
{
[b]int array[10]; [/b]
array[11] = 0;
printf("stick with core\n");
}
Oops, I was wrong. Because you put the "array" array on the stack, there are no chances for "segmentation fault".
Peter TRoll 'developer' #REKT
The array is neither static nor in a function, so its not on the stack. More likely ( dependent on your setup) its pre-allocated in the programs data section.
The fact that you dont core any time is down to blind luck.
int main() { ... } is not a function?
Look again!
Code:
(gdb) run
Starting program: /home/valiz/petertroll
Breakpoint 1, main () at petertroll.c:6
6 array[11] = 0;
(gdb) info registers rsp
rsp 0x7fffffffe2b0 0x7fffffffe2b0
(gdb) print &array[11]
$2 = (int *) 0x7fffffffe2dc
(gdb) l
1 #include
2
3 int main()
4 {
5 int array[10];
6 array[11] = 0;
7 printf("stick with core\n");
8 }
9
January 19, 2016, 09:03:22 AM
Obviously, running your code does not always end up with "segmentation fault", it is only a possibility.
Code:
int main()
{
[b]int array[10]; [/b]
array[11] = 0;
printf("stick with core\n");
}
Oops, I was wrong. Because you put the "array" array on the stack, there are no chances for "segmentation fault".
Peter TRoll 'developer' #REKT
The array is neither static nor in a function, so its not on the stack. More likely ( dependent on your setup) its pre-allocated in the programs data section.
The fact that you dont core any time is down to blind luck.
January 19, 2016, 03:59:02 AM
Obviously, running your code does not always end up with "segmentation fault", it is only a possibility.
Code:
int main()
{
[b]int array[10]; [/b]
array[11] = 0;
printf("stick with core\n");
}
Oops, I was wrong. Because you put the "array" array on the stack, there are no chances for "segmentation fault".
Peter TRoll 'developer' #REKT
January 19, 2016, 03:54:39 AM
Hey Lauda, I took your advice to learn C [1]. I've been playing around with arrays and I think I've found a technical solution to the block size limit debate:
When I run my program, it gave me the answer:
It's time to dump the core!!
/stupid programmer joke
Code:
#include
int main()
{
int array[10];
array[11] = 0;
printf("stick with core\n");
}
When I run my program, it gave me the answer:
Code:
>./decentralize_development
segmentation fault (core dumped)
It's time to dump the core!!
/stupid programmer joke
Hey Peter TRoll, you are such an incompetent 'developer'. Obviously, running your code does not always end up with "segmentation fault", it is only a possibility. Look, I compiled and ran the code and there was no segmentation fault.
Your code only leads to undefined behavior. And btw, you should put a "return" statement when you exit the main function to hide your gross incompetence.
Code:
$ cat petertroll.c
#include
int main()
{
int array[10];
array[11] = 0;
printf("stick with core\n");
}
$ gcc -o petertroll petertroll.c
$ ./petertroll
stick with core
[1] Just kidding. My C code is running in semiconductor fabs all over the world including at Intel and Samsung.
No proof for this statement.
January 19, 2016, 03:24:10 AM
What's the Classic position on opt-in RBF?
Our polling shows that there is almost no support for it (and lots of opposition towards it). For this reason, opt-in RBF will not be included in Bitcoin Classic.
Classic is censoring supporters of RBF! It's literally worse than the Khmer Rouge!
Good luck with your Toomin dictatorship and its (feature) killing fields. You can take our RBF, but you will never take our freedom!
Says the one who supports censorship the most and opens threads that are censored by himself. Noone with half a brain listens to your orwellian BS.
Orwellian? Like how Big Brother Toomin memory-holed RBF, by removing even the option to enable it?
At least I know the difference between the Schweizerische Eidgenossenschaft and a democracy. That's pathetic, given that you live in the Confoederatio Helvetica!
You know nothing. If the people in Switzerland want to decide and vote upon any option, we can! If we decide to not enable BS that the Politbüro programmed, we do!
January 19, 2016, 03:17:01 AM
What's the Classic position on opt-in RBF?
Our polling shows that there is almost no support for it (and lots of opposition towards it). For this reason, opt-in RBF will not be included in Bitcoin Classic.
Classic is censoring supporters of RBF! It's literally worse than the Khmer Rouge!
Good luck with your Toomin dictatorship and its (feature) killing fields. You can take our RBF, but you will never take our freedom!
Says the one who supports censorship the most and opens threads that are censored by himself. Noone with half a brain listens to your orwellian BS.
Orwellian? Like how Big Brother Toomin memory-holed RBF, by removing even the option to enable it?
At least I know the difference between the Schweizerische Eidgenossenschaft and a democracy. That's pathetic, given that you live in the Confoederatio Helvetica!
January 19, 2016, 03:13:13 AM
What's the Classic position on opt-in RBF?
Our polling shows that there is almost no support for it (and lots of opposition towards it). For this reason, opt-in RBF will not be included in Bitcoin Classic.
I hope you aren't giving votes to people like me. We know nothing!
I hope they will. Such is democracy. Here in Switzerland, wherever the entire population can vote on individual acts, everything works better than elsewhere on the planet where experts and Politbüros are deciding.
The Core developers and cheerleaders prefer to speak on armed squares. The Bitcoin Classic people prefer those squares:
http://www.myswitzerland.com/en-ch/landsgemeinden.html
Did you vote to get rid of banking secrecy?
Did you vote to betray all those who trusted Swiss banks to protect their families' saving from predatory governments?
Did you vote to peg the Franc to the Euro? Did you vote to suspend/relax that peg?
Did you vote for negative interest rates?
We can vote to everything, as soon as we decide to, you noob. Educate yourself!
January 19, 2016, 03:10:45 AM
What's the Classic position on opt-in RBF?
Our polling shows that there is almost no support for it (and lots of opposition towards it). For this reason, opt-in RBF will not be included in Bitcoin Classic.
Classic is censoring supporters of RBF! It's literally worse than the Khmer Rouge!
Good luck with your Toomin dictatorship and its (feature) killing fields. You can take our RBF, but you will never take our freedom!
Says the one who supports censorship the most and opens threads that are censored by himself. Noone with half a brain listens to your orwellian BS.
January 19, 2016, 03:04:21 AM
What's the Classic position on opt-in RBF?
Our polling shows that there is almost no support for it (and lots of opposition towards it). For this reason, opt-in RBF will not be included in Bitcoin Classic.
I hope you aren't giving votes to people like me. We know nothing!
I hope they will. Such is democracy. Here in Switzerland, wherever the entire population can vote on individual acts, everything works better than elsewhere on the planet where experts and Politbüros are deciding.
The Core developers and cheerleaders prefer to speak on armed squares. The Bitcoin Classic people prefer those squares:
http://www.myswitzerland.com/en-ch/landsgemeinden.html
Did you vote to get rid of banking secrecy?
Did you vote to betray all those who trusted Swiss banks to protect their families' saving from predatory governments?
Did you vote to peg the Franc to the Euro? Did you vote to suspend/relax that peg?
Did you vote for negative interest rates?
Jump to: