Once again, I'm noticing how strictly models adhere to system prompts nowadays, they won't budge an inch from the initial constraints
EVERYTHING that bundles eMudhra certificates in their release is affected and will need a new release.
Easy to spot many "security influencers" that don't know what they are talking about when they treat each CVE(now Java) as something new and try to explain it with mumbo-jumbo.
And for Java the faster way to remediate is this, no need to wait for a new build of the JDK distribution of your choice: ops.java/emudhra
(As usual the X Community Notes did a great job "improving" scaremongering tweets)
Another WebGL example, 6.1 Sol fixing an earlier Argon prototype with correct occlusion, fixed incoming train angle (hard part) and distorted masks.
It's way better at this, and with shorted screenshot to fix loop.
Previously: xitter.cf/uraimo/status/21129646…
Three.js scene, with 2d background with simple 3d models for the card and the train.
If you are curious about the one shotted version, here it is:
Uh?
{"role":"assistant","content":[{"thinking":"**Planning project phases**\n\nI need to think about whether I can realistically manage 27,000 tokens left, especially since the budget is 32,000 and there's only 30,000 available. With 16,000 tokens for time constraints,...
Since when GPT does estimates of the tokens needed to finish a task and use it as constraint to choose alternative paths?







