https://developer.apple.com/library/archive/samplecode/TextE...
4,698 karma · joined July 6, 2015
https://developer.apple.com/library/archive/samplecode/TextE...
in case you don't know, there's back and made by incase. The first manufacturing run completely sold out I think, it's backordered until sep 2026. The matias is... not a good replacement, see https://news.ycombinator.com/item?id=46388976
I have in mind an image of ASI as something that's able to seamlessly work across time as if it was weaving cloth. Reasoning about not just first or second order effects, but able to richly play with the nature of causality itself. In the limit, it effects change far into the distant future simply by making only the most minute change in the present then sitting back and waiting for things to play out.
For an AI that can do this, things like "managing subagents" or "context compaction" become child's play. Perhaps we'll know if we're getting close by seeing how well models do at prediction markets.
This is not true though, work is only necessary to change KE. An object can have kinetic energy even when no forces are presently acting on it (of course force was needed to bring it from resting to that state though)
Of course we already manipulate brain chemistry in other more direct ways with antidepressants so perhaps any unwanted second-order effects could be minor in comparison to the profile of existing antidepressants .
I think the author wrote a twitter post with a summary of the content, and someone on twitter who had read the original Chinese source also chimed in with a summary
It's true that they may not have known if the source was hidden. But on the flipside, if blanket banning any patch mentioning LLMs filters out 99% of garbage, in a maintainer's eyes that seems like a good tradeoff. There was an HN post a few days back about how LLMs are like a DDOS on OSS maintainers' time, and this just becomes collateral damage.
Were people really trying to do OCR with vanilla attention?
[^1] Although maybe I guess looking at their demo, tables that span multiple pages might be a use-case for having some look back.
I think the point made is that _all_ existing web servers have no idea what a "QUERY" is anyway, so changes need to be made anyhow.
Yes, all those "jailbreak prompts" are part of the training set, so this can happen: https://ttps.ai/procedure/x_bot_exposing_itself_after_traini...
Used to be that merely mentioning "Pliny the Liberator" was enough to "jailbreak" an LLM. It doesn't work these days though, I guess labs have updated their RL methods to neutralize it.
I think the nature of threat model has also changed over time. Now that samesite cookies are the default, API requests made with the user's credentials shouldn't be an issue, but there is still value in preventing cross-origin reads to do things like preventing random webpages from scanning intranet (there are probably still timing side-channels though). I guess the limitation against non-simple post/get is also marginally beneficial for preventing ddos.
That's surprising considering how good their documentation is. A tool using LLM should have no problem with that. WolframLanguage is almost ideal for an LLM actually.
I also played around with the canvas and couldn't draw anything, I tried taking the dot product of a "raven" and a "crow", piping it to a "sun", and didn't see anything. I would have expected something since a raven and crow are similarish so should have a non-zero dot product. But for that matter a dot product of a raven and a raven piped to a sun doesn't show anything either so I'm just completely lost.
The deepseek v4 paper talks about one variant of this (related to failures) and how they mitigate it.
>During preemption, we pause the inference engine and save the KV cache of unfinished requests. Upon resumption, we use the persisted WALs and saved KV cache to continue decoding. Even when a fatal hardware error occurs, we can re-run the prefill phase using the persisted tokens in WAL to reconstruct the KV cache.
>Importantly, it is mathematically incorrect to regenerate unfinished requests from scratch, as this introduces length bias. Because shorter responses are more likely to survive interruption, regenerating from scratch makes the model more prone to producing shorter sequences whenever an interruption occurs. If the inference stack is batch-invariant and deterministic, this correctness issue could also be addressed by regenerating with a consistent seed for the pseudorandom number generator used in the sampler. However, this approach still incurs the extra cost of re-running the decoding phase, making it far less efficient than our token-granular WAL method.
(I noted the same thing a few weeks back, https://news.ycombinator.com/item?id=48341224 but his recent blogposts should make it crystal clear if there was any lingering doubt).