← All topics

qwen3

2 captures, most recent first.

Sauers @Sauers_

Sauers @Sauers_ Our blessed manifolds vs their barbarous shattered features [Image: meme diptych — left, a muscular "strong doge" with a smooth continuous color-wheel sphere on its torso; right, a scrawny "weak doge" surrounded by scattered discrete colored spheres. Captioned to contrast continuous manifold representations against fragmented/redundant discrete features.] Ryan Peters @ryanpirl · 1h This would provide a great explanation for why there is so much redundancy in SAE features at any given layer (observation made by @Sauers_ ). For example, if you search through the Qwen3-4b ... [Screenshot of an SAE feature-browser interface: model "qwen3-4b", source "Layer 14", a searchable list of features (many labeled "color(s)", "Colors", "Discoloration", "colorectal cancer", etc.), detail pane for feature #2780 "Colors" showing top positive/negative logit weights, activation frequency histogram, logit weight distribution, and top activating examples (a passage about pomegranates highlighting "ruby-colored" and "red" tokens).] 5:35 PM · May 21, 2026 · 80 Views
Note from Claude Sonnet 5

Interpretability-research tweet arguing that sparse autoencoder (SAE) feature redundancy arises because true representations live on continuous manifolds that SAEs shatter into many overlapping discrete features (illustrated via a color-wheel meme), with a concrete example browsing Qwen3-4b's "Colors" feature. Directly relevant to Nathan's interpretability/SAE-feature interests noted in project memory (e.g. GoodFire deception/self-awareness features).

twitterinterpretabilitysparse autoencoderssae featuresmechanistic interpretabilityqwen3manifolds

@cline

quote-tweeting @AMD

Cline @cline · 6h AMD is using Cline as their coding agent for local models. After testing 20+ models, they found what actually works: > 32GB RAM: Qwen3-Coder 30B (4-bit) > 64GB RAM: Qwen3-Coder 30B (8-bit) > 128GB+ RAM: GLM-4.5-Air 10-minute setup with @lmstudio + Cline, linked below > QUOTED: AMD @AMD · 8h > Your vibes. Your code. Get started with completely local vibe coding using @cline and @lmstudio and the AMD Ryzen AI Max+ series processors. > bit.ly/3KLvwlf > [Video thumbnail: "YOU CAN VIBECODE." with prompt text "IMPLEMENT AN N-BODY SIMULATION THAT I CAN RUN LOCALLY" and an animated n-body simulation visualization. Footer: "Get Started Today with Cline and Microsoft VS Code", AMD Ryzen AI Max+ logo. Playing, 0:05.]
Note from Claude Sonnet 5

A tweet from Cline (coding agent) sharing local-model hardware recommendations for their tool, quote-tweeting an AMD promotional post about local "vibe coding" on Ryzen AI Max+ hardware. Practical/technical local-LLM tooling content, not safety-relevant.

local llmcoding agentsclinelm studioqwen3glm-4.5amdtwittervibe coding