So, lets play a game of Russian Roulette with a six round cylinder.
You survive the first pull. Are you saying that it's safe to pull it 7.5 more times? After all, nobody died on that first datapoint, and we all know 7.5 * 0 = 0.
The nice thing about shooting at 48 as opposed to 60, is it's much easier to drop it down to 24 - just discard every frame. Hell, you've got the information so you could even merge that discarded frame in during pans to blur it (think oversampling).
With 60-24, you'd have to discard an odd number, likely causing a regular jitter, or halve it like above and then slow everything down (similar to PAL to NTSC)
Indeed, I've got a nice server sitting here in my apartment collecting dust, since I stopped working at the datacenter. (by nice I mean quad core 2.8 with 4gb of ram).
Did you see me advocating the idea or saying it was a good or bad idea? No. The only thing I said was that we have not done what the person I was replying to suggested we have.
Um, did you not see my trying to help? You want help, then perhaps you should help us help. Or, you could just open a bug without doing any preliminary work, and call someone trying to help you a troll.
You're positive that it's not a dying mouse button? Have you tried using xevt to see if the X server is receiving the mouse clicks? (eg, it could be getting lost before even making it to the GUI, and hence not be a gnome bug)
Slashdot Mirror
The distillation of it is to use Google's DNS, or some other public DNS system.
Of course, the best answer if you are sensitive to this kind of thing is to run your own resolver, which isn't all that hard.
So, lets play a game of Russian Roulette with a six round cylinder.
You survive the first pull. Are you saying that it's safe to pull it 7.5 more times? After all, nobody died on that first datapoint, and we all know 7.5 * 0 = 0.
Um.... discard every other frame. I hope you realized what I meant to say.
The nice thing about shooting at 48 as opposed to 60, is it's much easier to drop it down to 24 - just discard every frame. Hell, you've got the information so you could even merge that discarded frame in during pans to blur it (think oversampling).
With 60-24, you'd have to discard an odd number, likely causing a regular jitter, or halve it like above and then slow everything down (similar to PAL to NTSC)
Yes, this is exactly what you are seeing.
Indeed, I've got a nice server sitting here in my apartment collecting dust, since I stopped working at the datacenter. (by nice I mean quad core 2.8 with 4gb of ram).
Erm, why are you assuming VPS means cloud?
Much better rendition of that comic, that I found somewhere.
... burning lake of sulfur? Wow, a 120C blood red pool with blue flame. An interesting visual.
It was not written. He dictated it, which is why it has that rambling, conversationally-telling-a-story feel.
What's that burning smell?
OH GOD PUT IT OUT!
Oh sure, using xevt to determine if the X server was receiving the mouse clicks at all is a totally unnecessary and superfluous diagnostic step.
I suppose you subscribe to the "randomly blame shit" method of troubleshooting?
Did you see me advocating the idea or saying it was a good or bad idea? No. The only thing I said was that we have not done what the person I was replying to suggested we have.
[citation provided], asshole.
We have not tried. If we did, we would have carpet bombed several countries by now.
Lamar Smith, a Rebublican representative of Texas.
Yes, you do. Because if you do not, you just handed them a legitimate charge to use.
You realize Obama is threatening to veto this, because we are all being so noisy about it? The guy is actually listening.
Actually, Obama is threatening a veto on this.
Um, did you not see my trying to help? You want help, then perhaps you should help us help. Or, you could just open a bug without doing any preliminary work, and call someone trying to help you a troll.
What reason is that, that the big companies keep fucking shit up?
That you used the wrong word?
Apparently you've missed all the bitching about people fucking with the UI for no good reason.
You're positive that it's not a dying mouse button? Have you tried using xevt to see if the X server is receiving the mouse clicks? (eg, it could be getting lost before even making it to the GUI, and hence not be a gnome bug)
I voted for Pretentious Porpoise.