All jokes aside, this is a very serious question when it comes to Google products [1]. Imagine having spent 5K on a Jamboard... [1] https://killedbygoogle.com/. - Source: Hacker News / 9 days ago

Https://killedbygoogle.com (and https://gcemetery.co ) the list is endless. - Source: Hacker News / 10 days ago

Alright, let's kick another party off: https://killedbygoogle.com/. - Source: Hacker News / 11 days ago

Someday Google could very likely terminate gmail accounts that block youtube ads Then there is this which just scrolls on and on forever https://killedbygoogle.com (or https://gcemetery.co ). - Source: Hacker News / 11 days ago

With Google’s graveyard[1] growing so fast, I’m careful with new Google announcements. An API like this sounds particularly problematic to replace sometime in future. [1]: https://killedbygoogle.com/. - Source: Hacker News / 17 days ago

I don't need/use IDA, Nemlei just used https://obfuscator.io/, which just obfuscates the crap out of the code using various known methods (which I won't go into detail, it's public knowledge) and an un-obfuscation was cooked up by others. The one fucked-up thing the website does is randomizing function names, it just changes every variable/function name. We can't "un-obfuscate" those, so it's up to our brains to... Source: 7 months ago

It's to purposefully makes your code harder to read so it prevents people from stealing your work. Here's a tool that does it: https://obfuscator.io/. Source: over 1 year ago

I just tested it on a little snippet of my code obfuscated with https://obfuscator.io/ and it worked seemingly perfectly. My original code:

  function resizeImage(img) {.

- Source: Hacker News / over 1 year ago

Https://obfuscator.io/ produces a similar result, perhaps that's all they used. Source: over 1 year ago

The obfuscation looks very similar to what you might get from https://obfuscator.io/. Source: over 1 year ago