My latest and greatest ThinkPad T14s Gen 6 likes to do it sometimes on cachyos, I can't nail it down from a KDE or hardware issue as it never does it while docked or a external mouse
I also noticed they where not using XML for game state output, from what I understand most LLMs still benefit from having outputs like this put into XML tags
I have not very well treated AuADHD and being alone with my thoughts very long is generally not very productive, At least Coding LLMs have helped me get things I wouldn't of had the attention span to make in the past come to life. and a good bit of vibe coding is just yelling at the LLM that what its doing sounds good on paper so keep going, please do the needful, make no mistakes :V
Depends, the SMD caps spread across the board the tiny ones do start to fail and go out of spec over time. they are a right pain to replace and hard to spot one that has gone out of spec to cause the chip to start crashing.
I know a guy who gets a bunch of old hardware as a recycler, We made the Shell On Demand Appliance for DEFCON[1] awhile back and would love to expand it, but power/internet would just cost too much. we have the hardware and software to do this. just not the long term recurring
I've been mostly using Kimi has a hacker of sorts, putting it places I want to attach AI directly as their API for their plans are not completely user hostile. Need to do OCR for scanning Magic the Gathering Cards. Sure!, have it attached to X4: Foundations as a AI manager for some stuff. sounds fun. Can't really do that with claude
Yep, Its pretty damn good compared to classic OCR and even more lightweight ones as well that I can run locally. the cards just vary too much over time.
I'm unsure of the sizes needed for prompt cache, but I suspect its several gigs in size (A percentage of the model weight size), how would the user upload this every time they started a resumed a old idle session, also are they going to save /every/ session you do this with?
The cache is stored on Antropics servers, since its a save state of the LLM's weights at the time of processing. its several gigs in size. Every SINGLE TIME you send a message and its a cache miss you have to reprocess the entire message again eating up tons of tokens in the process