By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code written by Claude will actually have a warning sigil

[jplebreton@mastodon.social]

@mcc [Adam West Batman] The telltale mark of The Slopper, my dear Robin...

[silvermoon82@wandering.shop]

@mcc
Hey, it worked today! The last few times I tried, it hung my browser instead.

[lexfeathers@tenforward.social]

@mcc unusually satisfying block

[gudenau@hachyderm.io]

@mcc Thanks for the reminder.

[trzyglow@mastodon.social]

@mcc reminded me to nuke my bluesky account, thanks!

[gutmunchies@dragon.style]

@mcc

oh, that's interesting & useful. thank you!

[mactunag@gts.eunach.scot]

@mcc will be nice to see if many repos don't use claude

[chfkch@ruhr.social]

@mcc
That is just a trick to get people sign up for ShitHub and login.

[coralineada@ruby.social]

@mcc I actually built the feature that warns you about blocked users, back when I worked for Github for a minute. Could not have predicted this use case!

[micha@23.social]

@mcc @mardor can't i do this on mobile view? I can't find such button/menu ...

[eve@evecodes.com]

@mcc

I just chuckled inside

[mardor@ruhr.social]

@micha
There is a tiny link at the left, below the achievements, no button.
@mcc

[bmartin427@techhub.social]

@mcc done, although in the process of blundering around looking for the block button I have apparently inadvertently opted into copilot ‍️

[mcc@mastodon.social]

@bmartin427 github is basically now a website-sized dark pattern to opt you into copilot without your knowledge

[mozziediver@mastodon.social]

@mcc Thanks!

[aho@mastodon.social]

@mcc those a good way to figure out bad code...

[micha@23.social]

@mardor @mcc wow didn't catch that. Thx!

[beemdvp@techhub.social]

@mcc oh great idea actually, it means we can do a double take on a project's reliability

[m@martinh.net]

@CoralineAda @mcc Thank you so much for this, Coraline - you may have just saved humanity!

Hmmm. Perhaps we could use the GH API to give us an early warning when a much loved codebase is compromised. Maybe starting with something like this:

curl -s -H "Authorization: Bearer $AUTH_TOKEN" \
  -H "Accept: application/vnd.github+json" \
  "https://api.github.com/search/issues?q=is:pr+is:merged+author:claude&per_page=100&page=1" \
  | jq -r '.items[].repository_url | sub("https://api.github.com/repos/";"")' \
  | sort \
  | uniq -c

This gets us a very lazyweb list of recently infected repos, although there are only ten results returned, with no pagination. That's a bit less than the 2.3 million commits reported in the web UI

      1 biner88/chart_sparkline
      1 davidray/twitter-bootstrap-calendar
      1 laudspeaker/laudspeaker
      1 ripienaar/free-for-dev
      4 segmentio/action-destinations
      2 uptech/flutter_app_analytics
      (etc)

Also author:claude is of course but one vector for the hungry ghosts...

[stelar@mas.to]

@mcc amazing tip