GitHub is not a good solution for Danbooru issue tracking

Maybe it once was, but not anymore. GitHub is problematic for several reasons:

GitHub can unilaterally delete issues created by users whose accounts it later terminates. This has happened multiple times in the past.

For non-technical users, requiring a GitHub account creates extra friction, causing issues to go unreported.

For technical users: GitHub ToS allows at most one free account per person. This means a user can choose between associating Danbooru to their real-life account (questionable, given the nature of this site), or risking their main account by violating ToS and creating a second one just for Danbooru.

Even if you attempt to create a second account, there are more problems:

Some smaller email providers (that do not require CC or phone number to sign up) are blocked.

Even if you find one which GitHub allows creating an account with, that GitHub account will likely get flagged, and flagged accounts are shadowbanned (with created issues only visible to themselves, etc).

Such flags can allegedly be removed, but that requires contacting support, and to even contact support you must: 1. add 2FA to the account (fine), 2. do SMS verification (which means giving them your phone number), so that's out.

I expect the shadowban issue has hit some non-technical users too.

My suggestion (which I was planning to put in a GitHub issue...) would be to move issue tracking into the site itself, or maybe a self-hosted forge (but obviously every option comes with trade-offs).

Side note: the other things I meant to make issues for:

• 'z' hotkey to show posts wider than the viewport at 1x scale no longer works on video posts with the new player, caused by unconditional max-w-full class on the video element.
• Since commit 6ba1040312cb9a4ee81cffe695b6b08d62814ef5 it is no longer possible to set a precise video speed externally (using built-in browser functionality, browser extension or user script). Speed is forcibly rounded to nearest 0.25 by the ratechange event handler.
• POST requests to /iqdb_queries no longer work while logged out, caused by commit 449fea7f38ddff80bc7e920efed15e5301d54909

(if someone with an actual working GitHub account could create issues for those, that'd be appreciated...)

The IQDB change is intentional, because IQDB was one of the endpoint that was getting pummeled by bad bots.

That seems unlikely. The commit in question is from last year ("controllers: ensure all controllers call authorize.") with no mention of IQDB specifically.

You might be thinking of what evazion said recently:

I might have to make the iqdb endpoint login-only anyway though, it's a slow endpoint and bots have been hitting it too hard lately

But based on that I guess it's unlikely to be restored, even if it was unintentional at first.

I don't like being dependent on Github, but I like running my own project infrastructure even less.

I've thought about self-hosting my own Gitlab instance, but it's another responsibility - monitoring it, keeping backups, performing updates - that I don't really want to have. We use Github not just for issues, but also for CI (running tests and building Docker images on every commit) and for hosting our Docker images (Dockerhub is also used as a backup). Codespaces (spin up a dev instance in your browser on demand) and Copilot (spin up an agent that can automatically fix simple issues) are also nice features to have.

We do have a Gitlab instance at https://gitlab.com/danbooru/danbooru as a backup, but I forgot about it and the repository sync broke a long time ago. Maybe I could get it working again. The Github would still be the issue tracker though, unless we migrated everything to Gitlab. But more people use Github, so moving the project to something else would add more friction than it removes.

Maybe the simplest thing to do would be to have a bug report page on Danbooru that just submits an issue to Github.