HomeSearchPrevious dayNext day

00:38:05etnguyen03 (etnguyen03) joins
00:40:53Exorcism0666 quits [Quit: Ping timeout (120 seconds)]
00:41:06Exorcism0666 (exorcism) joins
00:41:11DigitalDragons quits [Client Quit]
00:41:29DigitalDragons (DigitalDragons) joins
00:53:11etnguyen03 quits [Client Quit]
01:03:36yasomi is now known as Xe
01:05:06etnguyen03 (etnguyen03) joins
01:14:38Juest quits [Ping timeout: 276 seconds]
01:23:06Juest (Juest) joins
01:51:37nexusxe2 joins
02:19:45etnguyen03 quits [Remote host closed the connection]
02:47:38nexusxe2 quits [Remote host closed the connection]
03:13:09lemuria quits [Read error: Connection reset by peer]
03:13:38lemuria (lemuria) joins
04:04:03nine quits [Quit: See ya!]
04:04:16nine joins
04:04:16nine quits [Changing host]
04:04:16nine (nine) joins
04:22:13Exorcism0666 quits [Quit: Ping timeout (120 seconds)]
04:22:28Exorcism0666 (exorcism) joins
04:22:33DigitalDragons quits [Quit: Ping timeout (120 seconds)]
04:22:52DigitalDragons (DigitalDragons) joins
04:58:37beardicus quits [Read error: Connection reset by peer]
04:58:50beardicus (beardicus) joins
05:05:38DogsRNice quits [Read error: Connection reset by peer]
05:08:26<BlankEclair>i'm so tired of ai slop now that i'm using google scholar surprisingly often
05:23:59Umbire quits [Remote host closed the connection]
05:24:29Umbire (Umbire) joins
05:59:23<nicolas17>https://overengineer.dev/blog/2021/04/25/usb-c-hub-madness/
06:06:53<BlankEclair>funny, the laptop i'm using has two usb-c ports and one usb-a port
06:18:11Irenes quits [Ping timeout: 276 seconds]
06:23:56<nicolas17>it seems all accessory companies are merely sticking their logo on a whitelabel product an unknown chinese company designed
06:34:34kedihacker joins
07:16:02<@arkiver>BlankEclair: yeah i'm starting to doubt more and more if something is real or made by AI
07:16:24<@arkiver>i guess AI is not leading to the feared "all fake stuff seems true", but perhaps more to the "all true stuff seems fake"
07:16:28<BlankEclair>it also doesn't help that i specifically want information on testosterone suppression on 5 mg of cyproterone acetate
07:16:31<@arkiver>... which is perhaps worse in some ways
07:16:35<BlankEclair>but even for general gaht stuff, i just go to google scholar
07:16:56<@arkiver>BlankEclair: ah yeah for that Google Scholar makes sense anyway :P
07:17:30<BlankEclair>i wish i had more of an appetite for reading journals
07:17:36<BlankEclair>but oh well :p
07:19:08<BlankEclair>this might be WP:BEANS, but i swear, one of the biggest factors that smells fishy about ai slop websites is the related articles section
07:19:38<BlankEclair>i find it highly improbable that a website can focus on ssh, health, hrt, and matresses
07:21:07<@arkiver>yeah :P
07:23:05ATinySpaceMarine quits [Quit: No Ping reply in 180 seconds.]
07:24:24ATinySpaceMarine joins
07:24:34lemuria quits [Read error: Connection reset by peer]
07:24:59lemuria (lemuria) joins
07:48:32Juest quits [Ping timeout: 276 seconds]
07:49:31Juest (Juest) joins
08:02:50HP_Archivist quits [Ping timeout: 276 seconds]
08:07:00Umbire quits [Remote host closed the connection]
08:07:29Umbire (Umbire) joins
08:20:28Webuser643332 joins
08:36:38Umbire quits [Ping timeout: 276 seconds]
08:42:23Dada joins
08:48:53Webuser643332 quits [Client Quit]
08:59:37HP_Archivist (HP_Archivist) joins
09:01:19Juest quits [Ping timeout: 260 seconds]
09:16:41Juest (Juest) joins
09:26:24Juest quits [Ping timeout: 260 seconds]
09:43:57<Hans5958>Random idea: Custom nick for webusers to identify from which page do they access IRC
09:43:59<Hans5958>https://chat.hackint.org/#/connect?join=%23windowfixer&nick=Archive%20Team%20Reader:%20Page%20Name
09:46:47<Hans5958>or username https://chat.hackint.org/#/connect?join=%23windowfixer&username=Archive%20Team%20Reader:%20Page%20Name
10:02:34HP_Archivist quits [Ping timeout: 260 seconds]
11:07:08lemuria quits [Read error: Connection reset by peer]
11:07:51lemuria (lemuria) joins
11:11:24midou quits [Ping timeout: 260 seconds]
11:19:45<BlankEclair>interesting proposal tbh
11:21:26midou joins
11:39:11Exorcism0666 quits [Quit: Ping timeout (120 seconds)]
11:39:17DigitalDragons quits [Quit: Ping timeout (120 seconds)]
11:39:27Exorcism0666 (exorcism) joins
11:39:33DigitalDragons (DigitalDragons) joins
12:13:05Xe quits [Ping timeout: 276 seconds]
12:16:55yasomi (yasomi) joins
12:17:42yasomi is now known as Xe
12:18:42Juest (Juest) joins
12:25:04<nyakase>how about the realname (mostly because of spaces)? could tack on the following to the url in {{IRC channel}}: &realname=ArchiveTeam%20Reader%20-%20{{urlencode:{{FULLPAGENAME}}}}
12:32:16<nyakase>...i tested that multiple times without noticing i missed the space between "archive team"
12:34:17DigitalDragons quits [Client Quit]
12:34:17Exorcism0666 quits [Client Quit]
12:34:33DigitalDragons (DigitalDragons) joins
12:34:33Exorcism0666 (exorcism) joins
12:34:42<FireFly>not sure what the gecos maxlength is on hackint, but that might exceed it and get clipped.. guess we'll find out
12:39:59<nyakase>50, so 29/30 for the page. i think that should be good enough
12:42:20<nyakase>oops, off by one for the page length. i had calculated that based on colon separator, but i changed it to a hyphen in mine because of namespaces
12:43:57Exorcism0666 quits [Client Quit]
12:44:08DigitalDragons quits [Client Quit]
12:44:14Exorcism0666 (exorcism) joins
12:44:25DigitalDragons (DigitalDragons) joins
12:55:56sec^nd quits [Remote host closed the connection]
12:56:18sec^nd (second) joins
13:55:45lemuria quits [Read error: Connection reset by peer]
13:56:50lemuria (lemuria) joins
14:20:36@OrIdow6 is now known as @OrIdow6-utm_source-Archiveteam3
14:20:50@OrIdow6-utm_source-Archiveteam3 is now known as @OrIdow6-utm_source-AT3AIRC
14:21:39@OrIdow6-utm_source-AT3AIRC is now known as @OrIdow6-utm_source-AT^3AIRC
14:24:00@OrIdow6-utm_source-AT^3AIRC is now known as @OrIdow6
14:24:05<@arkiver>ah interesting
15:13:16grill (grill) joins
15:14:39arch quits [Ping timeout: 260 seconds]
15:15:23<anarcat>Xe: i've been looking at the deployment options for nginx, and from what i can tell, you're supposed to plug anubis between nginx and itself? can't i just plug nginx and the backend directly? like in my case, i would put it between nginx and gitlab-workhorse, for instance
15:16:19<anarcat>Xe: also, has there been any thought given to an integration that does *not* make *all* traffic go through anubis? like just having anubis as an advisory thing on the side that the webserver would check?
15:16:47<anarcat>i have actually no idea how that could work, and any time i try to come up with a tweak for that, i end up with sharing a secret between the frontend, anubis, and the client, and that won't work anyways
15:17:17<anarcat>but in our case, we're pushing loads of traffic (including firefox git clones) through nginx, gitlab-workhorse and gitaly already, and i'm relunctant in adding yet another layer, since our problem is load anyways
15:17:29<anarcat>anyways, feel free to tell me to bugger off and get a subscription or something :)
15:20:13arch (arch) joins
16:06:46DigitalDragons quits [Quit: Ping timeout (120 seconds)]
16:07:04DigitalDragons (DigitalDragons) joins
16:16:06midou quits [Remote host closed the connection]
16:16:16midou joins
16:29:11midou quits [Ping timeout: 276 seconds]
16:34:13midou joins
16:46:05grill quits [Ping timeout: 276 seconds]
16:47:43grill (grill) joins
17:06:04grill quits [Ping timeout: 260 seconds]
17:21:15grill (grill) joins
17:25:23BornOn420 quits [Remote host closed the connection]
17:25:56BornOn420 (BornOn420) joins
17:36:20<Xe>anarcat: I have been learning increasingly horrifying things about the gitlab omnibus container, i need to take the time to try and set it up. It's probably going to involve horrifying crimes.
17:36:24<steering>BlankEclair: the problem is, nonsense related articles predate AI slop because they're just another place for paid advertisements :P
17:36:42Exorcism0666 quits [Quit: Ping timeout (120 seconds)]
17:36:43DigitalDragons quits [Client Quit]
17:36:48<steering>Xe: s/omnibus container// :P
17:36:56Exorcism0666 (exorcism) joins
17:36:58DigitalDragons (DigitalDragons) joins
17:37:06<Xe>steering: the omnibus container is a specifically unique brand of horrifying though
17:37:10<steering>fair
17:43:36HP_Archivist (HP_Archivist) joins
17:49:51<anarcat>Xe: i have also been horrified by the gitlab omnibus container, if you have any familiarity with it whatsoever, i would recommend using k8s and helm instead :p
17:50:00<anarcat>they have sane containers down there, you just ned to hunt for them
17:50:11<anarcat>i just deployed gitaly on its own with podman and systemd in a VM, it works
17:54:52DigitalDragons quits [Client Quit]
17:54:52Exorcism0666 quits [Client Quit]
17:55:07Exorcism0666 (exorcism) joins
17:55:10DigitalDragons (DigitalDragons) joins
17:56:36<Xe>anarcat: but yeah basically think of Anubis as you'd think of a Rack middleware
17:56:42<Xe>just in HTTP reverse proxy form
17:56:57<anarcat>Rack as in Ruby?
17:57:08<anarcat>not sure i'm familiar with rack
17:57:15<Xe>ah okay so
17:57:28<Xe>a Rack middleware is some code that runs before and after a HTTP route
17:57:37<Xe>usually it does things like check access tokens
17:57:59<Xe>in Anubis' case, it's a HTTP reverse proxy where all traffic goes in, filtered traffic goes out
17:58:19<anarcat>right
17:58:34<Xe>it's a weird infrastructure layer, usually this would be put directly into the HTTP server but that would make it only work with Nginx / Apache / Caddy / etc
17:58:58<anarcat>right
17:59:22<anarcat>i keep thinking "surely there's a standard way to delegate such AAA decisions to a third-party server"
17:59:29<anarcat>and then i laugh at my naivety
17:59:47<anarcat>whatever that name is for naive
17:59:51<anarcat>english hard is
18:20:06<steering>the problem is that Anubis needs to be able to send its own response back, right? (whether it modifies or just replaces the response)
18:20:30steering hasn't paid attention at all to what it actually does
18:23:35tzt quits [Ping timeout: 276 seconds]
18:24:19tzt (tzt) joins
18:24:57<nicolas17>if it decides to block, it needs to send the proof-of-work interstitial page yeah
18:26:21<Xe>steering: I would implore you to read https://anubis.techaro.lol, i spent a lot of time making the docs better than any of the docs for things I have to deal with professionally
18:27:21<steering>I just... don't have any cause to actually interact with it yet :) I'm sure I'll get around to it once IP blocking stops working well enough for me
18:30:05lemuria quits [Read error: Connection reset by peer]
18:30:34lemuria (lemuria) joins
18:32:30<Xe>fair enough, but really
18:32:35<Xe>the docs do answer your questions :)
18:42:36<anarcat>i did read essentially the entirety of anubis' docs
18:42:52<anarcat>they are excellent
18:43:12<anarcat>what confused me is the diagram in, say, https://anubis.techaro.lol/docs/admin/environments/apache vs https://anubis.techaro.lol/docs/admin/environments/traefik
18:43:59<anarcat>the traefik one is how i would expect: anubis sits between the frontend proxy and the backend, but the apache (and nginx) ones are *weird*, it's as if anubis *must* return the queries back to the webserver, before the webserver passes it back to the backend
18:44:19<anarcat>actually, now that i look at the traefik one again, it also looks weird
18:44:31<anarcat>ah it's the caddy one that looks right
18:44:35<anarcat>https://anubis.techaro.lol/docs/admin/environments/caddy
18:45:03<anarcat>although it doesn't explicitly have a box labeled "caddy" which is a tad confusing (i suspect it's the box labeled TCP 80/44)
18:45:19<anarcat>i'd be happy to throw in some MRs about this btw, if i can understand what i'm missing here
18:45:47DigitalDragons quits [Client Quit]
18:46:03DigitalDragons (DigitalDragons) joins
18:46:06<nicolas17>I switched windows and read "techbro.lol" there for a second
18:47:20<anarcat>.lol
19:16:14tzt quits [Ping timeout: 276 seconds]
19:17:26tzt (tzt) joins
19:21:57Dada quits [Remote host closed the connection]
19:29:09<Xe>nicolas17: so do you want to know the deep lore
19:29:31<Xe>Techaro was originally a startup i made up for industry satire
19:29:40<Xe>a fake startup*
19:30:59<Xe>anarcat: yeah that's a bit of the rough edge of the docs, maybe the caddy/nginx bits need to be in a subgraph? IDK
19:36:33DigitalDragons quits [Client Quit]
19:36:47DigitalDragons (DigitalDragons) joins
19:41:58arch quits [Remote host closed the connection]
19:42:11arch (arch) joins
19:42:20Dada joins
19:45:37Dada quits [Remote host closed the connection]
19:47:39grill quits [Ping timeout: 260 seconds]
19:48:31Dada joins
19:49:24ThreeHM quits [Ping timeout: 260 seconds]
19:51:06ThreeHM (ThreeHeadedMonkey) joins
19:55:14Dango360 quits [Ping timeout: 260 seconds]
19:58:59Dango360 (Dango360) joins
20:06:19Dango360 quits [Ping timeout: 260 seconds]
20:07:34Dango3604 (Dango360) joins
20:11:34Dango3604 is now known as Dango360
20:25:01nine quits [Quit: See ya!]
20:25:14nine joins
20:25:14nine quits [Changing host]
20:25:14nine (nine) joins
20:26:26Guest58 joins
20:29:11Dada quits [Remote host closed the connection]
21:16:35Irenes (ireneista) joins
21:20:52<BlankEclair>> [18/07/2025 03:36] <steering> BlankEclair: the problem is, nonsense related articles predate AI slop because they're just another place for paid advertisements :P
21:20:59<BlankEclair>yeah, but ai slop also doesn't help :p
21:49:29HackMii quits [Remote host closed the connection]
21:49:48HackMii (hacktheplanet) joins
21:53:01Exorcism0666 quits [Quit: Ping timeout (120 seconds)]
21:53:17Exorcism0666 (exorcism) joins
21:53:20DigitalDragons quits [Client Quit]
21:53:38DigitalDragons (DigitalDragons) joins
22:16:58atphoenix__ (atphoenix) joins
22:19:19atphoenix_ quits [Ping timeout: 260 seconds]
22:42:05lemuria quits [Read error: Connection reset by peer]
22:42:57lemuria (lemuria) joins
23:15:11etnguyen03 (etnguyen03) joins
23:23:29NotGLaDOS quits [Ping timeout: 260 seconds]
23:37:49NotGLaDOS joins
23:39:24etnguyen03 quits [Client Quit]
23:39:45etnguyen03 (etnguyen03) joins
23:49:30etnguyen03 quits [Client Quit]
23:58:38etnguyen03 (etnguyen03) joins

HomeSearchPrevious dayNext day