Curt

@thsottiaux What is this? In all of my time using Codex I have never seen it before... Pro sub and nowhere near rate limits...

Another reason to prefer private GitLab. GitHub's terms say public repos may be forked on GitHub, yet Anthropic still used GitHub's DMCA process against the claude-code fork network. @trq212 any clarifications? The notice said 8.1k repos; the upstream now shows ~10.5k forks.

@sudoingX stuck with a rtx 3080 10gb right now but will be getting a pair of rtx 5060ti 16gb soon enough. been working on making my own windows first inference and training engine. im interested to see what you think i should be running on 10gb vram xD.

drop your GPU below. i'll tell you exactly what model and config to run on it. here's what i've tested and verified on real hardware: RTX 3060 12GB - Qwen 3.5 9B Q4 - 50 tok/s - 128K context RTX 3090 24GB - Qwen 3.5 27B Q4 - 35 tok/s - 300K context RTX 3090 24GB - Qwen 3.5 35B MoE Q4 - 112 tok/s - 262K context 2x RTX 3090 - Qwen3-Coder 80B Q4 - 46 tok/s - full VRAM all running llama.cpp with flash attention. every number is real. every config is tested. if your card isn't on this list drop it below and i'll tell you what fits.

@therealmaffucci @MatthewBerman @nvidia @Dell @grok @grok answer the question

@MatthewBerman @nvidia @Dell @grok what's the price of this setup?

.@nvidia hand delivered a pre-production unit of the @Dell Pro Max with GB300 to my house. 100lbs beast with 750GB+ of unified memory to power the best open-source models in the world. What should I test first?

Do rate limits seem off this week for codex? I blew through a entire weeks limits in roughly 24 hours. also WTF is Other? @OpenAI

WTF... Apparently changing desktop refresh rate in Windows 11 causes Claude Code OAuth token revocation... @trq212

@James_M_South @ChatGPTapp That doesnt sound right... @thsottiaux you tracking this?

Got accepted in to the @ChatGPTapp Codex for Open Source program today. Or so I thought. Turns out you get punished for already spending money on them. Wild!

I think there is a bug because i am currently at 19 compactions on gpt5.4 high and not a single line of code has been written or modified. this is not that difficult of a python to rust conversion project and i have done several similar diffiulty conversions using codex before without issue. once it hits 20 compactions if it still hasnt made any modifications i will change back to 5.3 codex and see if it works.

@cpjet64 On my end it’s taking almost 15 minutes to compact on gpt 5.4 high 😅 Must be a bug @thsottiaux ?

Is it just me or are other people having codex on gpt5.4 extra high take up to 5 minutes to perform a compaction the last 3 days or so? sometimes its a fast compaction operation like usual but sometimes i have sat here and almost canceled the run because compaction was taking so many minutes @thsottiaux

@jxnlco @steipete YOU SIR JUST MADE ME SNORT MY COFFEE. Tears coming out of my eyes and everything. Well done.

as part of reviewing codex for oss applications I check if the user has made a contribution to the repo they claim. then I find some fucking guy.... 12k contributions to their own repo? scroll.. scroll.. scroll... oh its @steipete application rejected

I am assuming the bug was probably related to specific users who probably had discord specific dev tools installed or configured. I rarely work on discord stuff these days so all of mine is disabled so my setup should be what most people would have. personally i think its great @EmbarkStudios is taking this so seriously because they have already released a patch fixing it (supposedly).

@cpjet64 @MaplePrism Might just be some sort of environment logging for the game I guess, appreciate it!

A NEW CHALLENGER HAS APPEARED IN THE LINK BELOW YOU WILL SEE THE VERY SAME COMPANY THAT SAID AGE VERIFICATION WAS SAFE, EFFECTIVE, AND YOUR DATA WOULD NOT BE STORED AND SAID THAT YOUR DMS ARE NOT BEING MONITORED OR READ HAS NOW GOTTEN CAUGHT WITH THEIR PANTS DOWN ALLOWING ARC RAIDERS TO NOT ONLY READ YOUR DMS BUT TO SAVE THEM IN PLAIN TEXT SILENTLY ONTO YOUR PC FOR ANY OTHER APPLICATION WITH READ PERMISSIONS TO SEE. timothymeadows.com/arc-raiders-di…

here is a copy paste from my own discord.log file from when i was trying to recreate Tim's post. I have not removed anything because there is nothing sensitive to remove. To me this just looks like normal Discord Presence stuff... [2026-03-05 02:25:04.906] [462400] (client.cpp:3339): Discord Slayer SDK, commit 3b8f3adce7dd1d85463aa700d9185676633e98a1, version 1.8.13395 [2026-03-05 02:25:04.906] [215104] (client.cpp:482): Setting application id to 1373923512766697512 [2026-03-05 02:25:04.906] [215104] (rpc_manager.cpp:130): RPC manager reset: RPC manager connecting with new client ID Status:0 [2026-03-05 02:25:04.907] [215104] (rpc_manager.cpp:43): RPC manager connected [2026-03-05 02:25:04.907] [215104] (command_register_win.cpp:66): Wrote command to registry [2026-03-05 02:25:04.960] [215104] (rpc_manager.cpp:47): RPC manager received READY [2026-03-05 02:25:04.960] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_JOIN","nonce":"0"} [2026-03-05 02:25:04.960] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_JOIN_REQUEST","nonce":"1"} [2026-03-05 02:25:04.960] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_INVITE","nonce":"2"} [2026-03-05 02:25:04.960] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"AUTHORIZE_REQUEST","nonce":"3"} [2026-03-05 02:25:04.964] [215104] (rpc_manager.cpp:310): Removing handlers for event: 0 [2026-03-05 02:25:04.969] [215104] (rpc_manager.cpp:310): Removing handlers for event: 1 [2026-03-05 02:25:04.969] [215104] (rpc_manager.cpp:310): Removing handlers for event: 2 [2026-03-05 02:25:04.969] [215104] (rpc_manager.cpp:310): Removing handlers for event: 3 [2026-03-05 02:28:12.712] [215104] (rpc_manager.cpp:130): RPC manager reset: RPC connection closed [2026-03-05 02:28:12.712] [215104] (rpc_manager.cpp:145): Scheduling RPC reconnect in 2000ms [2026-03-05 02:28:14.712] [215104] (rpc_manager.cpp:43): RPC manager connected [2026-03-05 02:28:15.049] [215104] (rpc_manager.cpp:47): RPC manager received READY [2026-03-05 02:28:15.049] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_JOIN","nonce":"4"} [2026-03-05 02:28:15.049] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_JOIN_REQUEST","nonce":"5"} [2026-03-05 02:28:15.049] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_INVITE","nonce":"6"} [2026-03-05 02:28:15.085] [215104] (rpc_manager.cpp:310): Removing handlers for event: 4 [2026-03-05 02:28:15.110] [215104] (rpc_manager.cpp:310): Removing handlers for event: 5 [2026-03-05 02:28:15.110] [215104] (rpc_manager.cpp:310): Removing handlers for event: 6 [2026-03-05 02:28:43.011] [215104] (rpc_manager.cpp:130): RPC manager reset: RPC connection closed [2026-03-05 02:28:43.011] [215104] (rpc_manager.cpp:145): Scheduling RPC reconnect in 2000ms [2026-03-05 02:28:45.011] [215104] (rpc_manager.cpp:43): RPC manager connected [2026-03-05 02:28:49.255] [215104] (rpc_manager.cpp:47): RPC manager received READY [2026-03-05 02:28:49.255] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_JOIN","nonce":"7"} [2026-03-05 02:28:49.255] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_JOIN_REQUEST","nonce":"8"} [2026-03-05 02:28:49.255] [215104] (rpc_manager.cpp:190): Sending RPC frame: {"cmd":"SUBSCRIBE","evt":"ACTIVITY_INVITE","nonce":"9"} [2026-03-05 02:28:49.292] [215104] (rpc_manager.cpp:310): Removing handlers for event: 7 [2026-03-05 02:28:49.313] [215104] (rpc_manager.cpp:310): Removing handlers for event: 8 [2026-03-05 02:28:49.313] [215104] (rpc_manager.cpp:310): Removing handlers for event: 9 [2026-03-05 02:40:52.844] [462400] (client.cpp:234): Calling loop shutdown

@cpjet64 @MaplePrism What kind of info are they logging and why?

Its been well known for a long time that messages etc are stored in plaintext BUT the consent dialog is not lying because as long as the files and their contents stay local on your machine the application doesnt receive them in their unencrypted form BUT there are some workarounds to this for the SDK since obviously thats also local to your machine.

@Fuckelonnazibi @cpjet64 @MaplePrism Thanks for the correction, you're right, discord.log is probably just for development and not included. As to the last part though, Discord also says in their application consent dialog that the application can't read your messages and, well, here we are

I take everything with a grain of salt but in this case I have a strong feeling this was just a case of someone enabling the full logging suite and not realizing the sdk included those items. Its rare enough for companies to take responsibility these days and they jumped right on it.

@cpjet64 @MaplePrism I would take that with a grain of salt. If it was a bug, surely they'd have noticed the logged messages as part of their crash reports, which would definitely include the game log. The fact that they haven't until this was publicised tells me another story.

@MaplePrism Just an update: I posted about this early this am in the official Arc Raiders discord and they have now acknowledged it was a bug.

@MaplePrism i read the post he wrote and immediately spent the last hour trying to replicate it to no avail. the logfile exists but currently does not include any of the claimed data. either embark already fixed it or this wasnt a issue to begin with.

@alexvai93 @MaplePrism Tell me you don’t know x posts expand and didn’t read the link from Tim Meadows… expand the post fully and you’ll understand

@cpjet64 @MaplePrism The news was from the 24th of February and your testing this on the 5th of March... Come on bro

hey @trq212 does @AnthropicAI have any plans to compensate all of us who were unable to use claude code during this outage? the codex team had a much smaller issue and reset everyones usage for the week.

@levelsio @elvissun depending on your vps and distro you could install either docker or lxc and just containerize the pr agent.

So @elvissun sent me some very helpful tips about this If I'd run this { autonomous agent that reads my error logs to fix } on the same VPS server as my site it'd be risky because it could easily get prompt injected via the error logs One way I thought could be to run the agent on its own VPS box with only read access to the repo and no sensitive data or credentials in the code, and let it only be able to do pull requests (PRs) on the repo to fix stuff Then you send parts of log to it and it's isolated That'd be safe?

sometimes i just want to cry when it comes to coverage