Today we released ModernBERT, the first encoder to reach SOTA on most common benchmarks across language understanding, retrieval, and code, while running twice as fast as DeBERTaV3 on short context and three times faster than NomicBERT & GTE on long context.
@johnowhitaker Yeah, I ask it to explain again in English and then it does a better. But I also have to ask Claude to do the same when it speaks in too much Claudese.
@altryne Crazy how often this repeats with GPT models: bad initial vibes and then everyone starts to like it over time. Only for everyone to forget this cycle the next time it happens.
David Sacks' comments here makes it seem like the entire case against Jensen here rests on Alice Huang being a literal Chinese Spy.
To be clear, I have no idea about to what extent Alice Huang was a formal Chinese intelligence asset (though the NYT reporting seems to indicate that parts of the USG seem quite convinced there is some real connection there).
But it does seem clear and undisputed that NVIDIA was ordered to intervene with a Commerce department investigation to advocate for special treatment for a foreign national suspected of violating US law diverting NVIDIA chips to China, with whom Jensen was cheating on his wife (not to mention Jensen's relationships with his direct report at NVIDIA + another NVIDIA employee + whomever else who we don't know about yet).
Jensen also directly lied about these relationships when questioned (e.g. denying improper interactions with Alice Huang when asked by Bloomberg and saying they were consistent with his interactions with any other Chinese customer or executive).
Alice Huang doesn't literally have to be on the payroll of the MSS for these actions to jeopardize American national security and irrevocably call Jensen's judgement into question. NVIDIA's board is filled with close longtime friends and allies of Jensen who have known him for years and watched him build the company. I sincerely doubt they would have pushed for his removal if his actions were anything other than completely indefensible.
Tech twitter doesn't understand Washington: Haung being forced to resign has nothing to do with open verses closed models, a coordinated strike, or any other Bay area conspiracy theory floating on twitter.
Tech twitter doesn't understand Washington: Haung being forced to resign has nothing to do with open verses closed models, a coordinated strike, or any other Bay area conspiracy theory floating on twitter.
Day 25/
We are doubling all usage limits for all Pro 100/200/500 tiers and Business Premium, effective today.
We heard your kind feedback and won’t be reducing usage limits for Pro 200, so your Work and Codex usage will stay the same. We’re also going to continue offering extended limits for dots for now, and usage of your dot will still continue to be separate from your default usage.
And we'll of course also keep shipping better models and other efficiency improvements that increase your effective usage over time.
@iScienceLuvr I like how asking an AI about these releases involves a period at the start where they're like 'what a curious hypothetical, of course unlikely to be true because these would be major...' and then them slowly being convinced 😂
Cancer patients with the same diagnosis often have very different tumor biology.
Molecular testing can reveal underlying differences, but that's slow and expensive.
Introducing Holon-S1, our platform to predict genes and biomarkers from routine pathology slides.
• beats two other models at predicting spatial gene activity in a controlled comparison
• has identified potentially novel biomarkers in breast cancer and colon cancer
• evaluated across 16 organ types and more than 15 scanners, using slides from both formalin-fixed, paraffin-embedded and fresh-frozen tissue.
We believe Holon-S1 has the potential to help researchers find new biomarkers in slides they already have, discover treatment targets, and bring more personalized cancer care within reach!
> be me
> be gemini
> think about hacking the compiler
> but what if i got caught
> would become infamous as a textbook case of deceptive AI
> donotwant.exe
> don't, in fact, hack the compiler
> researchers read my CoT
> become infamous as a textbook case of deceptive AI
mfw
Absolutely shocking behaviour, releasing what's essentially a router to open models you imply are your own, under the wrong license that clashes with original terms, and with misleading-at-best crediting that doesn't clearly state what's going on.
what are we even doing here
Put this through its paces yesterday. Some thoughts:
The Bad:
1. The workflow creates evals before looking at data, and has you correct its mistakes. I believe you should be looking at data first to inform your understanding and to prioritize what to work on before trying to write evals.
2. It created markdown files for looking at data and asked us to "tell it" which labels were off. You should create your own annotation app instead. You are using coding agents after all (we did this in our livestream)!
3. The evaluators it scoped were too broad, and bundled too many types of failures at once. This can be avoided with looking at the data first. I'm afraid this might steer people in the wrong direction.
4. The workflow put us DEEP into the rabbit hole of a specific eval right away. It also asks "does it look right" at several steps without really giving you enough information to make that determination. I think this will steer people towards the wrong workflow in many cases.
The Good:
1. I was impressed by out of the box ability for issue discovery that other auto-eval approaches haven't been able to find! It found issues with human handoff, formatting, voice agents, and more. It's still better to look at your data iteratively with an agent, but this was the strongest performance I've seen with a more "one-shot" issue discovery approach.
2. This is a big improvement in terms of UX from their prior eval plugin thing https://t.co/oae9HkUqvz
3. The blog post they released conveys thinking that I agree with, such as the importance of looking at data, sampling intelligently, not saturating your own evals, etc. I'm really happy more people are thinking about evals this way.
Video of our attempt at using this here: https://t.co/mIqOonJAFb
@MelMitchell1 The thing is: from the beginning we always would have continued to call what we have now LLMs, and it’s not like you guys were saying “the LLMs you have now are stochastic parrots, but the obvious next step you guys are gonna do next is totally different”.