Live data from Hacker News

Viewing profile — moshetanzer

moshetanzer

HN member
Joined
Thu, Jan 08, 2026, 6:23 PM UTC
HN karma
6
Public activity
25 items

About moshetanzer

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #46792728

    Yeah that is what we also figured. We are using https://forwardmyinbox.com which works quite well.

  3. story
    Ask HN: How are you handling Gmail ending POP3 and Gmailify?

    Starting January 2026, Gmail is removing support for POP3 and Gmailify. This means millions of people who rely on Gmail to consolidate emails from other accounts will suddenly lose…

  4. story
    Show HN: Forward My Inbox – IMAP‑to‑Gmail Forwarding After Gmail Kills POP3

    Google is killing POP3/Gmailify in January 2026, breaking workflows for fetching email into Gmail. I built Forward My Inbox ( https://forwardmyinbox.com ) as a replacement: connect…

  5. story
    Ask HN: Why do we wait for PR to review obvious slop

    It drives me crazy the amount of noise there is on all the PR ai code reviews. There is so much that could be caught by reviews before - maybe at commit time? Is this just me??

  6. story
    Ask HN: Why does it still make sense to review stupid bugs at PR time?

    Ask HN, Code reviews are essential, but I keep seeing the same pattern: PR reviews are full of comments about trivial bugs, lint issues, and convention mismatches that could have b…

  7. comment
    Comment #46629830

    Ask HN, It feels increasingly backwards that PR reviews are where we catch basic bugs, style issues, and convention violations. With AI writing a large chunk of code now, the volum…

  8. story
  9. story
  10. comment
    Comment #46589236

    https://commitguard.ai code reviews that are faster than linter that auto run pre commit and fully configurable.

  11. comment
    Comment #46589166

    Most code review happens at PR time, after code is already written, tested, and context is gone. With more AI-written code, tests pass but logic issues still slip through. Would ea…

  12. story
  13. story
  14. story
  15. comment
  16. comment
    Comment #46573514

    Linters are great for style and syntax, but logic errors still rely heavily on human review. Do you think a linter for code logic - for example: risky condition changes, missing er…

  17. story
  18. comment
    Comment #46570467

    Hi HN, I spent some time improving the CommitGuard landing page to make it clearer and more direct about what the tool does. I’d love your honest feedback, does it make sense at a …

  19. story
  20. comment
    Comment #46569187

    Yip this won’t help them. Though I sure help there aren’t a lot of them ;)

  21. story
    Show HN: Commit-based code review instead of PR-based

    Hi HN, I’m experimenting with commit-based code review as an alternative to PR-based review. Instead of analyzing large PR diffs, this reviews each commit incrementally, while cont…

  22. comment
    Comment #46545156

    i like the idea v nice

  23. comment
    Comment #46544950

    its not :)

  24. comment
    Comment #46544551

    I have found that PR based code reviews are two noisy and non configurable. Also unpredictable as to when they will run or if all is ok. Also it is never clear who’s problem it is …

  25. story