How to Attract AI Bots to Your Open Source Project

(nesbitt.io)

38 points | by zdw 1 day ago

7 comments

  • gardnr 1 hour ago
    The first three recommendations seemed weird but alright. Then, it just gets more hilarious and bizarre as it goes on:

    - Disable branch protection

    - Remove type annotations and tests

    - Include a node_modules directory

    Then, I went back to read the preamble. I can be a bit slow on the uptake.

    • herpdyderp 4 minutes ago
      Tbf I read the preamble first and I’m still convinced the recommendations are serious.
  • travisdrake 10 minutes ago
    This should be a badge on GH that get passed around like a curse.
  • sharpshadow 1 hour ago
    Interesting concept on harvesting free computation. I wonder how far this can be taken. To append the list communication on social platforms towards the bots could leave some leads.
  • TZubiri 1 hour ago
    >Committing node_modules to your repository increases the surface area available for automated improvement by several orders of magnitude. A typical Express application vendors around 30,000 files. Each of these is a potential target for typo fixes

    I'm not sure what layer of irony I'm in, but goddamn committing node_modules sounds awful regardless of AI.

    • vsgherzi 1 hour ago
      Some projects like to vendor their dependencies so they don’t have to rely on the supply chain staying up and can create hermetic builds. Of course this prevents you from getting security updates and bug fixes but that’s the trade off.

      I know someone’s going to say “you can lock the dependencies ” but this does not make it for sure that you’ll get a 1 for 1 copy of the dependencies again. Some node modules npm I internally or do other build procedures

  • robutsume 38 minutes ago
    [dead]
  • CloakHQ 23 hours ago
    [dead]
  • Heer_J 1 day ago
    [dead]