| 30 Apr 2025 |
 Sandro | The key difference to the other projects is, that it stores the results in a database, right? | 12:46:24 |
| Sandro | Does it already expose a minimal web ui like nixpk.gs? I have interest in trying to deploy it because the existing pr-tracker performs not so well for me on our hardware due to io constraints | 12:47:30 |
 adamcstephens | This looks great. I see you're suggesting users could subscribe to some events through pr-tracker. If you'll be getting installed as a webhook receiver for the repo, would you be willing to route all webhooks you receive on to other targets on request? e.g. so others could leverage the access you've received to build their own tooling? Or would that be a level of service you'd prefer not to commit to? | 12:54:28 |
| adamcstephens | If not, would that be a standalone app we should consider? | 12:55:03 |
| adamcstephens | Or alternatively, it would be nice to have a formal way to request such webhook integration. I've been tinkering with a similar app of my own to track nixpkgs data, and eventually it would reach the point where I'd like access to the webhook feed. | 13:00:19 |
 Alyssa Ross | In reply to @sandro:supersandro.de
Does it already expose a minimal web ui like nixpk.gs? I have interest in trying to deploy it because the existing pr-tracker performs not so well for me on our hardware due to io constraints Do you make sure your git repo is regularly GCed? | 13:24:25 |
| Sandro | I thought we did but after doinga double check apperantly not 🤔 that explains a LOT...
There was a nixpkgs PR for a module, so that people don't need to copy bits from your config but that kinda went stale. | 13:26:24 |
| Sandro | maybe we should finish that but we are getting OT | 13:26:34 |
 Jeremy Fleischman (jfly) | we have not build a UI. our preference (not set in stone) would be for this to be a backend for other people to build stuff on top of | 15:27:00 |
| Jeremy Fleischman (jfly) | i don't think we'd want to forward all webhooks.
i do think that's something we (the infra team) should enable community members to do, though. do you know if this is a problem other communities have solved? | 15:30:06 |
 K900 | What exactly is the problem with "just ask the infra team" ? | 15:31:13 |
| Jeremy Fleischman (jfly) | i think that's fine. perhaps worth writing it down somewhere | 15:31:45 |
| Jeremy Fleischman (jfly) | i'm not sure if the infra team actually has the perms to do it | 15:31:59 |
| adamcstephens | I don't think they do. | 15:48:08 |
| adamcstephens | I think you need Owner(?) on the repo to add a webhook | 15:49:03 |
 hexa | setting up webhooks on the org? we do not | 15:49:04 |
| hexa | yeah | 15:49:11 |
| hexa | admin | 15:49:13 |
| 1 May 2025 |
| Alyssa Ross | I'm getting 403 Forbidden from Hydra. JS is enabled. | 04:56:49 |
| Jeremy Fleischman (jfly) | We had to disable anubis, and are back to playing whack-a-mole with nginx use agent sniffing :(
https://github.com/NixOS/infra/issues/670 | 05:15:36 |
| Jeremy Fleischman (jfly) | * We had to disable anubis, and are back to playing whack-a-mole with nginx user agent sniffing :(
https://github.com/NixOS/infra/issues/670 | 05:15:48 |
| Alyssa Ross | Guess I need to more aggressively update my Firefox… | 05:22:09 |
| hexa | I'm looking into alternatives, but availbility of hydra-server (the webfrontend) had been spotty yesterday | 10:38:54 |
| adamcstephens | https://git.gammaspectra.live/git/go-away was one i saw yesterday | 13:07:00 |
 symphorien | I saw https://dgl.cx/2025/04/using-haproxy-to-stop-scrapers in pure haproxy | 13:10:02 |
| hexa | i have it packaged locally already since yesterday | 14:35:27 |
| hexa | that uses robots.txt to entrap bots that disregard and abuse the listings in it, not a fan | 14:35:54 |
| symphorien | I think the robots.txt is independent from the hash-based one | 14:43:52 |
| symphorien | but maybe I understood wrong | 14:43:59 |
| hexa | exactly 0 of the bots we filter out right now actually look at robots.txt | 14:44:03 |
