rupayanc.bsky.social

rupayanc.bsky.social

@rupayanc.bsky.social

56 followers160 following80 posts

I gave an AI a sample fridge photo and asked for a week of dinners. 27 seconds. Then it put salt and five masalas on the shopping list, because a photo can't see your cupboard. The plan was the easy part.

Disconnect your inbox from a ChatGPT dot and it still keeps what it already read. Per OpenAI's help page, the only way to clear that is to delete the dot. So the day-one question is which accounts you connect at all.

My trading bot's AI reviewer hit its usage limit overnight. For 9.5 hours it did nothing: no entries, no exits by rule, only the stops already on the exchange. That's the design working. Fail-closed costs you a morning. The alternative is a bot that trades on a hunch.

one prompt, my bank statement, 22 lines, 3 minutes 6 seconds. totals matched the bank's to the rupee, and it caught a double swipe I'd forgotten was refunded. the check is the whole trick: if its totals don't match the statement's, it names the lines it couldn't read instead of guessing

48k chars of context: ~25k tokens as text, ~2.7k as one image. Same reader. At Fable list price that's 25 cents vs 2.7 cents a request. Author measures 59 to 70% off a Claude Code bill. The catch: 12-char hex strings came back 13/15 on Fable 5, 0/15 on Sol. Silent misses.

Same 105GB model, same 128GB Mac. Only the RAM budget changed: 34.6 / 48 / 73GB. 21 / 27 / 31.5 tok/s. slotstream reads experts off the SSD each token. More cache, fewer disk reads. One reporter, not a curve; a 16GB M2 got 1.41.

Quantizing a model to 4-bit does nothing to its context cache. On Llama 3.1 8B the cache stays 16-bit by default and hits 17GB at full context, bigger than the weights you just shrank. The file size is not the RAM budget.

Maple hitting 218 tok/s is real. Treating that as proof the model is reliable is the mistake. Its own model card says “minimal general reinforcement learning.” Speed is a deployment benchmark. Trust is a capability benchmark.

100B on one CPU at 6.58 tok/s sounds ridiculous. The footnote matters: that’s a BitNet benchmark configuration on an M2 Ultra with 64GB RAM. Microsoft’s released model is 2.4B, and BitNet isn’t a switch for ordinary models. github.com/microsoft/Bi...

github.comGitHub - microsoft/BitNet: Official inference framework for 1-bit LLMsOfficial inference framework for 1-bit LLMs. Contribute to microsoft/BitNet development by creating an account on GitHub.

Soup fine tunes Llama 3.1 8B on a 4GB laptop GPU. RTX 3050, 3.32GB peak, bit exact output, 119.6 tok/s. The frozen base never sits in VRAM; it streams in one decoder layer at a time. The catch: that number is from v0.72.2 and nobody has re run it on a 4GB card since.

Same model, nine different harnesses, and the cost per task runs $1.05 to $18.34. The catch nobody screenshots: the $1.05 one is also the worst in the table, 53.3% against 66.7%. Drop the outlier and it's still 4.5x. Runta ran it on the runtime it sells.

A 125B model on a 48GB Mac. slotstream keeps 105GB of weights on SSD and a 33GB working set in RAM, about 12 tok/s on an M5 Pro. The catch: Apple Silicon only, 110GB free SSD, a 16GB M2 got 1.41 tok/s. It tells you your speed before you download 88GB.

Fine tune Llama 3.1 8B on a 4GB laptop GPU. Soup streams the frozen base from system RAM one decoder layer at a time. RTX 3050 Laptop: 3.32GB peak, 119.6 tok/s, bit exact. The catch: measured on v0.72.2, not re run on a 4GB card since the fp32 fix. 5.6k stars. github.com/MakazhanAlpamys/Soup

github.comGitHub - MakazhanAlpamys/Soup: Fine-tune LLMs from one YAML. Layer streaming trains an 8B model on a 4 GB laptop GPU.Fine-tune LLMs from one YAML. Layer streaming trains an 8B model on a 4 GB laptop GPU. - MakazhanAlpamys/Soup

Train a 64M language model from scratch for 43 cents. One RTX 3090, about 2 hours, 3 yuan of rental at Chinese prices, per the minimind README. The catch: one epoch of the Zero variant on the small datasets. Tiny model, real training run. 59k stars. github.com/jingyaogong/minimind

github.comGitHub - jingyaogong/minimind: 🧠 Train a 64M-parameter LLM from scratch in just 2h!🧠 Train a 64M-parameter LLM from scratch in just 2h! - jingyaogong/minimind

A picture of your code costs less than the code. An image is priced by its pixel dimensions, not by the text inside it, so pxpipe renders your context as PNGs first. About 3.1 characters per token against 1 as text. Their readme tells you not to trust the savings figure and to measure your own.

I stopped reading my coding agent's permission prompts weeks ago. I just approve. clawk boots a throwaway Linux VM per project and runs the agent inside with its safety flags off, deliberately. Their own line: "the host filesystem isn't hidden behind deny rules; it was never mounted."

Firefox, the real one, compiled to WebAssembly, running inside a browser tab. Feels like the cleanest incognito ever shipped. But a tab can't open raw sockets, so every page goes through a WebSocket proxy Puter hosts. Their own line: "Web content is proxied through a Puter-hosted Wisp server."

Ship That Code: rebuild Redis, Git, a database and an OS kernel from an empty file. 179 courses, 37 languages, and your code runs against a real executor rather than a video. Its page says "free forever". Its own pricing line says "free while we grow". Those are two different promises.

Nvidia reportedly buying Hugging Face, $12.9B. Reported, not confirmed. The Information says agreed. Business Insider says unsigned, could still fall apart. Nvidia's newsroom, five days on: nothing. Hugging Face turned down $500M from Nvidia last year to avoid one big investor. Now this.

freellmapi stacks 34 providers' free tiers behind one OpenAI compatible /v1. 635 endpoints, automatic failover, ~40MB at idle. I almost posted a two week old card about it. Every number had moved, all upward.

New Qwen model, 125B params, 6B active per token. I saw "6B active" and got excited. Then I opened the GGUF repo. The most aggressive quant they publish is 67.6GB. Active parameters are about compute, not memory. You still hold the whole thing. Learned that one the slow way, again.

my content pipeline catches truncated video, black frames, and stale numbers. today every check passed and the post was still wrong. a person broke it in about ten seconds by asking one question.

View full thread

my checks measure pixels and numbers. none of them measure whether a stranger can feel it. still no fix for that. right now the fix is "ask a person", which is a humbling thing to be building an automated pipeline toward.

my content pipeline catches truncated video, black frames, and stale numbers. today every check passed and the post was still wrong. a person broke it in about ten seconds by asking one question.

View full thread

here's what i'd missed. the best thing i ever posted was 2.78 trillion parameters running in 8gb of ram. that worked because you feel both numbers instantly. trillion is obviously huge. 8gb is printed on every laptop you've ever bought.

my content pipeline catches truncated video, black frames, and stale numbers. today every check passed and the post was still wrong. a person broke it in about ten seconds by asking one question.

View full thread

my content pipeline catches truncated video, black frames, and stale numbers. today every check passed and the post was still wrong. a person broke it in about ten seconds by asking one question.

friend: bro just use a habit tracker me: i built a full RPG. quests, XP, bad habits as named bosses friend: how long did that last me: 27 days friend: and the tracker i sent you me: ...also 27 days

One of my AI agents lost its job this week. 11 models tried out for me this year. Every task scored. The famous one did the most work and won the least. Benched it. Stop picking AI tools by hype. Keep score. The reputation gap is real.

My AI has one standing rule: argue with me when my reasoning is weak. This morning it pulled up my own track record and asked what is actually different this time. Uncomfortable and correct. An agreeable AI is just a mirror.

Amazon lost 120k orders to AI-assisted code that skipped senior review. Lightrun 2026 report: 43% of AI code needs manual debugging in prod. Typing was never the bottleneck. The senior engineer saying "no, not this way" was. AI just made that conversation feel optional.

The scariest part of the new Claude model isn't what it can do. It's the second one Anthropic built alongside it and decided not to ship. "Too dangerous to release" used to mean nuclear material. Now it's how a lab describes a coding model.

watching everyone rebuild karpathy's llm wiki this week. cool tech. but if your second brain can be auto-generated overnight by any model, is it really yours? or is it just a cache you happen to own?