Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #10257

R

Redirecting...

Personal blog · hot3eed.github.iosecurityprogramming

Redirecting... is a personal blog at hot3eed.github.io about security and programming. Since 2020, 7 different Hacker News readers have linked it 10 times, most often “Reverse Engineering Snapchat (Part I): Obfuscation Techniques (2020)”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
10mentions?
7HN people?
2020–2025first – last linked?
Links on Hacker News per year · peak 7 in 2020

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

Linked as examples of reverse engineering Snapchat's API obfuscation, in a multi-part series with a follow-up on TikTok. Commenters cite or link the posts without judging the writing.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. Reverse Engineering Snapchat (Part I): Obfuscation Techniques (2020)
    3 people · 3 mentions · first linked 2020-06-20
  2. Reverse Engineering Snapchat: Obfuscation Techniques
    3 people · 3 mentions · first linked 2020-06-17
  3. Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable
    2 people · 2 mentions · first linked 2020-06-21

What Hacker News says?

  1. > An argument against obscurity is that it adds additional pains for your "regular" users (as in developers/3rd party developers/app developers) No one should be applying obscurity to public-facing APIs or anything for which documentation is widely distributed outside the company. A better example would be Snapchat's intense and always evolving obfuscation strategies: https://hot3eed.github.io/snap_part1_obfuscation…

    Comment linking /snap_part1_obfuscations.html

    on “Security by obscurity is underrated”
  2. Submitted Reverse Engineering Snapchat: Obfuscation Techniques as a story · 497 points

    HN discussion
  3. CORRECT LINK: https://hot3eed.github.io/2020/06/18/snap_p1_obfuscations.ht...

    Comment linking /2020/06/18/snap_p1_obfuscations.html

    on “Reverse Engineering Snapchat: Obfuscation Techniques”
  4. Submitted Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable as a story · 295 points

    HN discussion
  5. It's easier to follow if you read part I of the series first: https://hot3eed.github.io/2020/06/18/snap_p1_obfuscations.ht...

    Comment linking /2020/06/18/snap_p1_obfuscations.html

    on “Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable”
  6. Submitted Reverse Engineering Starling Bank (Part I): Obfuscation Techniques as a story · 2 points

    HN discussion
  7. Snapchat's API call obfuscation: https://hot3eed.github.io/snap_part1_obfuscations.html This one about TikTok was recently on the HN front page: https://www.nullpt.rs/reverse-engineering-tiktok-vm-1

    Comment linking /snap_part1_obfuscations.html

    on “Twitter API hacked, user database being sold online”
  8. Submitted Reverse Engineering Snapchat (Part I): Obfuscation Techniques (2020) as a story · 1 points

    HN discussion
  9. Submitted Reverse Engineering Snapchat (Part II): Deobfuscating the Undeobfuscatable as a story · 1 points

    HN discussion
  10. Submitted Reverse Engineering Starling Bank (Part II): Jailbreak Detection and Mitigations as a story · 1 points

    HN discussion

Search all of HN for hot3eed.github.io