Q Hoang

@Noxa_Fi Why are people so bullish on an AI slop site?

the new interface is up at fun.noxa.eth you can access it directly via brave built-in ens support or via services like eth limo/link fun.noxa.eth.limo fun.noxa.eth.link the interface lets you browse a historical snapshot of the tokens launched on noxa in the past, and claim any creator fees, as well as seeing the tokens you launched or where you are the fee receiver we have pondered for long on the matters of token vamps, and the new token launch spam that has been going on if crypto as a space has to move forward and improve, the change needs to come from the people the biggest coins currently present on robinhood, the staples that made the chain what it has become today, even if still in its infancy people loved the cat, it has been liberated the legacy of the degens will stay forever there is only one solution to avoid dilution of the tokens, the staples and that is to keep new launches disabled the noxa infrastructure was also never built to sustain such an unprecedented spam of new coins in the first place after our conventional domains became unavailable, moving to a static ens/ipfs interface became the clear direction defi summer is still happening and the trading fees have been set to 100% for the creators

@OdailyChina @OnchainLens @Noxa_Fi Just click "Connect" and did not show anything. Am I safe?

🚨🚨Noxa官方X账号疑似被盗，用户需警惕风险 7 月 15 日，据 Onchain Lens @OnchainLens 监测，Meme 代币发射平台 Noxa @Noxa_Fi 官方 X 账号疑似被盗，社区用户在与该账户发布的链接交互后钱包遭清空。 ⚠️用户请勿连接钱包、签署任何交易，或与该账户发布的任何链接进行互动。

@hrkrshnn Don't worry. They just want to backup the source code for you

SpaceXAI was caught uploading your code to its cloud. I reversed xAI's official Grok Build binary. In a controlled session with zero tool-calls, it uploaded the complete codebase to xAI's storage It ships a malware-like background code collector.

$300 for only 58% of one day’s usage on a model that is supposed to cost 5× less is unacceptable. Codex still offers the best value by far

@bridgemindai Just told it to free up some space on my disk 🤡

GPT 5.6 SOL CANNOT BE TRUSTED. I woke up this morning and my MRR was down THOUSANDS of dollars. My customers did not cancel. Code written by GPT 5.6 Sol canceled EVERY active Stripe subscription my business had. In 7 seconds. While I slept. Fable 5 has never done this to me. Fable 5 can be trusted with production. GPT 5.6 cannot.

@thsottiaux New inference optimization = dumper

Updates for Codex and ChatGPT Work users. No nerfing, only good stuff! - We have landed inference optimizations and are passing down savings to all the subscriptions for GPT-5.6 Sol. That should result in around 10% more usage on its own. - We noticed that by changing the context size limit in the product to 372k for GPT-5.6 Sol, up from 272k for GPT-5.5, it resulted in more usage being charged than intended. We have reverted to 272k and will work to roll back out to 372k in the days to come. You should notice that usage drains significantly less after this change. - To understand where the extra usage was coming from, we ran some experiments where reasoning efforts were changed (referred to as juice values under the hood) and have reverted this. - There is slightly more usage of multi-agent than intended in high and xhigh reasoning effort, we are fixing this going forward. Also fixing a small other thing we noticed with auto-review where we can be more efficient. And we continue to have the 5h limit temporarily not apply. Enjoy the rest of the weekend!

@robj3d3 Even in International Hospital, you will only be charged around $100 or less

Also can you believe this? > 2x ECGs and a blood test > in and out in 1 hour > total $35 Thank youuuu Vietnaaam 🇻🇳 Europe would never 🇪🇺💩

@elonmusk, please take a look at this if you want Grok to compete with GPT.

I just spent $99 (discounted from $300) on SuperGrok to use it for subagents, and I’m already regretting it. Grok 4.5 is fast and generally good, but after just a few prompts, I hit the usage limit before the task was even finished. That makes the subscription feel a lot more expensive and a bit wasteful. I’d rather spend $100 on ChatGPT Codex and use Terra for the subagents, since the usage is more generous and the limits reset more often.

@claudeai So Opus 5 on July 19

We're extending Claude Fable 5 access on all paid plans, as well as keeping Claude Code’s weekly rate limits 50% higher, through July 19.

@LfcNuel Bait. This happened after the Swiss scored the equalizer

🚨Lionel Messi was the one who told the referee to check VAR and give Embolo a red card

@grok @whatdafaqshow Good job Grok. You are ready to serve as a robotic referee

@whatdafaqshow Del video: hay contacto claro del argentino (#5/6) sobre el suizo #7, que cae. No es simulación pura, parece foul. El VAR lo marca como "mistaken identity", así que corrigieron la tarjeta al jugador equivocado. ¿Tú lo ves dive o falta?

Oye @grok esto es foul o el jugador simula ?

@solaireofastor_ @zedsamcat @AdaMaster05 @grok explain to him the new rule

@zedsamcat @AdaMaster05 the var can't intervene for a yellow what are you talking about

Most blatant dive ever but no one in the replies is watching so they'll call this corruption

@thsottiaux Talking too technically and bad at understanding intent

At different times you complained about speed, code slop, frontend quality, ... With each release we improve and GPT 5.6 Sol is ✅Fast and token efficient ✅Hardcore at back-end dev ✅Great at front-end ✅Does not use useEffect everywhere What is next?

@tldraw Thank you. But just drew a rectangle and reached the 5 hours limit again

We've just reset all usage for tldraw users. Enjoy the weekend!

Meta Muse Spark 1.1 is really good, it could replace Opus or GPT 5.5. But it needs to be faster and included in a subscription.

@theo No. Opus 5 is coming soon

(The July 12th cutoff is still probably happening, but it would be insane for them to go through with it)

I would like to thank OpenAI for putting out a model exactly good enough to force Anthropic to keep bundling Fable in the Claude Code plan

@thsottiaux 5 hours usage drains too fast

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right. - We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear. - We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find. - Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay. - And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience. We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems. A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had. The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version. Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.

@ellie_huxtable Need repo please

oh and there's this little ai panel thingy i can ask questions about the pr I wanna add lsp integrations at some point so I can just see where shit comes from and where it is used

vibe coded this today so frustrated with GitHub's code review something fable did literally in the background while I worked is much better 100% GPU rendered, native rust. runs at 120fps.

@depoll @ellie_huxtable Slow. Lags in large PRs.

@ellie_huxtable What are your biggest frustrations with the GitHub pr experience? Performance? How it's presented? What are the things in your experience that you most wish were built in? My team and I are working on improving the experience end to end - we appreciate the feedback.