In this blog post I take a look at how well GitHub, GitLab and Bitbucket support reviewers in finding malicious code changes in pull requests.
  • monk
    44•11 months ago

    Homoglyphs? Invisible text? Bidirectional text? Just highlight every line that goes beyond ASCII with yellow warning colors and require to vet it. Maybe make localization data an exception.

    • @cbarrickEnglish
      12•11 months ago

      This doesn’t work for code bases written in non-English languages. Especially east asian languages.

      Any line containing an identifier that is also a word would be highlighted.

      More and more programming languages are supporting unicode identifiers for this use case.

        • @[email protected]
          5•11 months ago

          I’d suggest to have the occasional look at the “most popular repos” ranking. It’s about 50% Chinese.

          Super-interesting sometimes as it shows completely different tech trends.

        • @cbarrickEnglish
          1•11 months ago

          I know right.

          It’s wild that an American company primarily doing business in the West would have a bias towards English.

      • monk
        6•11 months ago

        Yeah, just don’t. Allowing to code in anything other than English is a disservice, plain and simple.

        Inb4, I’m not being US-centric, Latin ain’t even my native alphabet.

    • ActualEnglish
      6•11 months ago

      Very simple solution actually. Here I was thinking we’d need AI to solve it.

  • snoweM
    15•11 months ago

    Website really struggled on mobile. Anytime I swipe to view the longer code lines in the code blocks it would open the sidebar. Very annoying.