| 1. | | Two-for-one: Amazon.com’s Socially Engineered Replacement Order Scam (htmlist.com) |
| 478 points by disillusioned on Dec 18, 2012 | 143 comments |
|
| 2. | | How to Download Your Instagram Photos and Kill Your Account (wired.com) |
| 389 points by mtgx on Dec 18, 2012 | 146 comments |
|
| 3. | | Instagram's official response (blog.instagram.com) |
| 334 points by kurtvarner on Dec 18, 2012 | 254 comments |
|
| 4. | | Wil Wheaton on Instagram's new ad policy (plus.google.com) |
| 288 points by mtgx on Dec 18, 2012 | 133 comments |
|
| 5. | | Why was Pinball removed from Windows Vista? (msdn.com) |
| 271 points by pavel_lishin on Dec 18, 2012 | 142 comments |
|
| 6. | | Whose bug is this anyway? (codeofhonor.com) |
| 267 points by experiment0 on Dec 18, 2012 | 42 comments |
|
| 7. | | How I Made $600K in the iOS Education Market (2012 update) (lescapadou.com) |
| 268 points by ja27 on Dec 18, 2012 | 116 comments |
|
| 8. | | Perl is 25 years old today (perl.org) |
| 260 points by kamaal on Dec 18, 2012 | 130 comments |
|
| 9. | | The Real Silicon Valley (jfornear.co) |
| 256 points by jfornear on Dec 18, 2012 | 148 comments |
|
| 10. | | The New Firebase Security API (firebase.com) |
| 265 points by mayop100 on Dec 18, 2012 | 51 comments |
|
| 11. | | AWS: the good, the bad and the ugly (awe.sm) |
| 226 points by brkcmd on Dec 18, 2012 | 85 comments |
|
| 12. | | Top ten algorithms in data mining (2007) [pdf] (googlecode.com) |
| 218 points by daoudc on Dec 18, 2012 | 41 comments |
|
| 13. | | Google Pays for Drones To Bust African Rhino Poachers (slate.com) |
| 199 points by wslh on Dec 18, 2012 | 83 comments |
|
| 14. | | A Python Compiler for Big Data (continuum.io) |
| 156 points by bluemoon on Dec 18, 2012 | 34 comments |
|
| 15. | | W3C finalizes HTML5 specification (w3.org) |
| 154 points by experiment0 on Dec 18, 2012 | 25 comments |
|
| 16. | | Mozilla Game On (gameon.mozilla.org) |
| 152 points by lee337 on Dec 18, 2012 | 34 comments |
|
| |
|
|
| 18. | | How far has Microsoft fallen? (computerworld.com) |
| 137 points by dmoney67 on Dec 18, 2012 | 150 comments |
|
| 19. | | Facebook Users Must Be Allowed To Use Pseudonyms, Says German Privacy Regulator (techcrunch.com) |
| 138 points by iProject on Dec 18, 2012 | 93 comments |
|
| 20. | | Philosophy of Computer Science (stanford.edu) |
| 118 points by FarhadG on Dec 18, 2012 | 22 comments |
|
| |
|
|
| |
|
|
| 23. | | 2012: The year Rubyists learned to stop worrying and love threads (tonyarcieri.com) |
| 99 points by bascule on Dec 18, 2012 | 26 comments |
|
| 24. | | Finding and Fixing a Five Second Stall (the-witness.net) |
| 95 points by jamesmiller5 on Dec 18, 2012 | 37 comments |
|
| 25. | | Germany orders changes to Facebook real name policy (bbc.co.uk) |
| 83 points by tchalla on Dec 18, 2012 | 115 comments |
|
| 26. | | GitHub Game Off Winners (github.com/blog) |
| 79 points by remi on Dec 18, 2012 | 17 comments |
|
| 27. | | Report: data caps just a “cash cow” for Internet providers (arstechnica.com) |
| 79 points by Libertatea on Dec 18, 2012 | 43 comments |
|
| 28. | | Deploying New Image Formats on the Web (igvita.com) |
| 79 points by igrigorik on Dec 18, 2012 | 5 comments |
|
| 29. | | A programmer’s guide to big data: tools to know (gigaom.com) |
| 79 points by mwetzler on Dec 18, 2012 | 29 comments |
|
| 30. | | JQuery Core 1.9 Upgrade Guide (jquery.com) |
| 71 points by robin_reala on Dec 18, 2012 | 35 comments |
|
|
| More |
Ah, the quantum tunneling pinball!
We ran into this while writing the original code at Cinematronics in 1994. Since the ball motion, physics, and coordinates were all in floating point, and the ball is constantly being pushed "down" the sloped table by the gravity vector in every frame, we found that floating point error would gradually accumulate until the ball's position was suddenly on the other side of the barrier!
(To simplify collision detection, the ball was reduced to a single point/vector and all barriers were inflated by the ball radius. So, if the mathematical point got too "close" to the mathematical line barrier, a tiny amount of floating point rounding or truncation error could push the point to the other side of the line)
To mitigate that, we added a tiny amount of extra bounce to push the ball away from the barrier when it was nearly at rest, to keep the floating point error accumulation at bay. This became known as the Brownian Motion solution.
Since much of the original code was written in x86 asm to hand tailor Pentium U/V pipelines and interleave FPU instructions, but wiki says Microsoft ported the code to C for non-Intel platforms, I'm sure the code had passed through many hands by the time it got to you. The Brownian Motion solution may have been refactored into oblivion.
http://blogs.msdn.com/b/oldnewthing/archive/2012/12/18/10378...