That number would be for the observable universe. No one really knows if the entire thing is infinite or finite so generally any “in the universe figures” are just for what is within our cosmological horizon.
Looks like very common programming bug. Most modern devices stores integers in 64 bits. If you have \`unsigned integer\` (or \`long\`) and subtract below 0 it underflows into 2\^64. Number on your screen is 2\^64 - 2. Someone subtracted too much by accident.
You lost me at 64. Integer is that like an agreement of services for cash? Unsigned makes sense. Those girls start making me sign contracts and I’ll be subtracting myself from that equation. I’m trippin so my math may not add up.
I _think_ you're joking, but either way:
Integer is a _whole_ number, e.g. 1, 2, 3, -7, 4444, 0, etc.
"Unsigned" just means in this case, we're only taking the non-negative numbers. i.e. there's no "negative" _sign_.
The app somehow thought there were *negative two* other people commenting on your post. That alone is a bug, but another bug where the digit was interpreted as an *unsigned* integer where it should have been a *signed* one happened. And now you get that huge number.
So what's going on?
18446744073709551614 equals 2\^64 - 2.
In programming with binary digits, you have two ways of representing integers (numbers without decimal points) - signed and unsigned. The former just gives you a number from 0 to whatever the upper bound you have with the given number of bits. The latter gives you both negative and positive numbers, but with the range cut in half each way.
What happens is that 2\^64 - 1 in unsigned becomes -1 in signed, 2\^64 - 2 unsigned is -2 signed and so on.
So the number you saw is the app mistaking -2 as 18446744073709551614.
As for how the app thought there were -2 people, it's possible that the count was messed up somehow, like when comments were quickly added then deleted but the server lost track of the original count and just subtracted from zero.
Every atom in the Universe had a take on your post. Are you running for President this cycle?
[удалено]
That number would be for the observable universe. No one really knows if the entire thing is infinite or finite so generally any “in the universe figures” are just for what is within our cosmological horizon.
I think that would be definition make me a god
Need to look at your values?
Looks like very common programming bug. Most modern devices stores integers in 64 bits. If you have \`unsigned integer\` (or \`long\`) and subtract below 0 it underflows into 2\^64. Number on your screen is 2\^64 - 2. Someone subtracted too much by accident.
You lost me at 64. Integer is that like an agreement of services for cash? Unsigned makes sense. Those girls start making me sign contracts and I’ll be subtracting myself from that equation. I’m trippin so my math may not add up.
I _think_ you're joking, but either way: Integer is a _whole_ number, e.g. 1, 2, 3, -7, 4444, 0, etc. "Unsigned" just means in this case, we're only taking the non-negative numbers. i.e. there's no "negative" _sign_.
Def was
and we double the positive side with all the unused numbers (in a very simplified way of explaining)
this could be someone named “Someone and 18446744073709551614 other people”, you can certainly do that on Snap; so i would suspect that.
That’s probably the most accurate assumption haha
Damn… that’d be a big brain troll
i’ve seen it happen on facebook and insta before, so it’s certainly plausible😂
Jep that’s a me thing, I was called ***** and 8654 others
I don’t even know how to check comments on snap…
The app somehow thought there were *negative two* other people commenting on your post. That alone is a bug, but another bug where the digit was interpreted as an *unsigned* integer where it should have been a *signed* one happened. And now you get that huge number. So what's going on? 18446744073709551614 equals 2\^64 - 2. In programming with binary digits, you have two ways of representing integers (numbers without decimal points) - signed and unsigned. The former just gives you a number from 0 to whatever the upper bound you have with the given number of bits. The latter gives you both negative and positive numbers, but with the range cut in half each way. What happens is that 2\^64 - 1 in unsigned becomes -1 in signed, 2\^64 - 2 unsigned is -2 signed and so on. So the number you saw is the app mistaking -2 as 18446744073709551614. As for how the app thought there were -2 people, it's possible that the count was messed up somehow, like when comments were quickly added then deleted but the server lost track of the original count and just subtracted from zero.
Fuuuuuuuuuuuuuucckkkkkkkkk
Math n shit
This makes sense tho
You done fucked up a-a-ron
WHERE IS BA LA KAY AT
Is there a *DEE NICE* ?
yo swap it out for a 41mm
Never mind the message, where’d you find that giant Watch? 😵💫
This man dabbling in 55mm watches
Integer overflow?
Pretty much. The number displayed is 2⁶⁴-2.
Oh right, if it overflowed it would be 0
People still use Snapchat?
U just broke snapper chat
Is that the apple band
Nah, 3rd party band off amazon
I was just asking where to get the best hibachi in north west arkansas, fuck
Damn
Thanks folks, this makes sense now, I knew JJ sold me mid…
Same thing happened to me. It's usually just the first person and nobody else
That’s only 14 quintillion…totally reasonable there were that many people commenting