Getting.over.it.with.bennett.foddy.macosx-hi2u May 2026
Bennett Foddy (the philosopher-king of punishing indie games) narrates with smug, soothing encouragement: quotes about failure, clips of weeping Chinese folk songs, and the occasional “You’re doing very badly.” The hi2u tag marks a release from a once-active PC scene group (HI2U — “Hi to you”). By 2017, scene releases for macOS were rarer than a bug-free Bethesda launch. But Getting Over It was a sensation, and Mac users wanted in.
Here’s a draft for an interesting blog post about the release Getting Over It with Bennett Foddy (macOS-X / HI2U) — focusing on the unique appeal of the game, the quirks of the cracked release scene, and why this particular version became a cult download. There are games that test your skills, games that test your patience, and then there’s Getting Over It with Bennett Foddy — a game that tests your very will to exist. But hidden inside the niche corners of torrent forums and scene release archives sits an odd little timestamp: Getting.over.it.with.bennett.foddy.macosx-hi2u . Getting.over.it.with.bennett.foddy.macosx-hi2u
To the uninitiated, it looks like garbled text. To those who remember, it’s a portal to 2017-era macOS gaming, piracy group signatures, and the unique suffering of playing a rage game on a MacBook trackpad. For the two people who haven’t seen a streamer lose their mind: Getting Over It casts you as a man in a cauldron, gripping a Yosemite hammer. You climb an endless, junkyard mountain of rusted cars, furniture, and cosmic debris. There’s no jump button. No reset. Only physics-based, nausea-inducing mouse/wrist movement. One slip sends you tumbling back to the beginning — sometimes losing hours of progress. Here’s a draft for an interesting blog post
So here’s to the masochists, the scene archivists, and the one person still trying to beat this game with a trackpad. You’re doing very badly. But keep climbing. Have a memory of playing the HI2U crack? Did your hammer glitch out at 90% progress? Share your pain in the comments. To the uninitiated, it looks like garbled text










Hi Ben,
Great article and a very comprehensive provisioning guide! Things are moving very fast at snom and the snom 7xx devices (except currently the 715) are now supplied automatically as “Lync ready” and can be easily provisioned straight out of the box. A simple command of text into the Lync Powershell and voila!
You can find all the details here:
http://provisioning.snom.com/OCS/BETA/2012-05-09 Native Software Update information TK_JG.pdf
Regards,
Jason
Link above was broken:
http://provisioning.snom.com/OCS/BETA/2012-05-09%20Native%20Software%20Update%20information%20TK_JG.pdf
Hi Jason, Thanks. It’s good to hear that’s an option, this post was based off a mini customer deployment we had a few months ago…
(Also can’t wait to test out the upcoming BToE implementation)
Ben
Hi Ben,
just stumbled across your great article. Please note the guide still available (now) here:
http://downloads.snom.com/snomuc/documentation/2012-02-06_Update-Guide-SIP-to-UC.pdf
is kind of superseded by the fact that for about 2-3 years the carton box FW image (still standard SIP) supports the UC edition documented MS hardcoded ucupdates-r2 record:
“not registered”: In this state the device uses the static DNS A record ucupdates-r2. as described in TechNet “Updating Devices” under: http://technet.microsoft.com/en-us/library/gg412864.aspx.
In short: zero-touch with DNS alias or A record is possible. SIP FW will not register but ask for the CAB upload based UC FW and auto-pull it if approved (but only if device was never registered: fresh from box or f-reset).
btw: the SIP to UC guide was made as temporally workaround, but I guess the XML templates still provide a good start line.
Also kind of superseded with Lync Inband Support for Snom settings:
http://www.myskypelab.com/2014/07/lync-snom-configuration-manager.html
http://www.myskypelab.com/2014/08/lync-snom-phone-manager.html
another great tool – powershell on steroids with Snom UC & SIP: http://realtimeuc.com/2014/09/invoke-snomcontrol/
(a must see !)
Please dont mind if I was a bit advertising.
Thanks and greetings from Berlin, also to @Nat,
Jan
Fantastic article! Thanks for sharing. We’ll be transitioning our Snom 760s to provision from Lync shortly.
Are there any licensing concerns involved?
Thanks Susan,
From a licensing point of view you need to make sure you have the UC license for the SNOM phones and on the Lync side if you are doing Enterprise Voice need a Plus CAL for the user concerned…
Hope that helps?
Ben
Thanks Jan 🙂
Thanks for the licensing info. It helps a lot!