... with a gpt-5.6-* model and every single round that carried tools came back as a 400 and a wall of English error prose in the chat bubble. Retrying showed you the same wall. Very helpful. ( #40 ) The twist: Skim never sent reasoning_effort at all. The model reasons at medium on its own, then refuses its own default alongside our tools so nothing in our request even named the thing that broke it. We still don't guess ... ... model-name regex, no "is this OpenAI?" sniffing the same base URL serves OpenRouter, Ollama, LM Studio, vLLM and whatever you typed in that box, and half of them would 422 on the "fix". So Skim

... each launch their own installer racing the other three for your install folder. A clean exit before the installer takes over. The updater ends this process with process::exit(0) no goodbyes. So on the way out Skim now parks the sync engines and folds the write-ahead log back into the database, instead of leaving a few megabytes of unfinished business for the next build to untangle on its very first query. The message list stopped lying ... ... Nothing to skim

... Ollama and llama-cpp-python ignore it in complete silence which doesn't fail your request, it just removes the ceiling on the answer. That's strictly worse than an error, because nobody ever finds out. So Skim now opens with the name every server understands, and switches only for an endpoint that asks for the other one by name, in its own error and only when that error names both keys, which is what separates "use the other name ...

... where Skim stops pretending that Microsoft owns exactly four domains on the entire internet. New Work & school accounts are finally recognized. If your company lives on Exchange Online, Skim

... underneath a surface that gives you no reason to look. Reviewing it properly means reconstructing what the code was supposed to do and checking whether it does that which is slower than writing it yourself, and enormously slower than skimming it and hitting merge. Everyone skims

... mainly because I'd rather explain a missing testimonial than a fake one. But it isn't free: option 3 asks the visitor to do work, and most visitors won't. You're trading a claim they'd have skimmed and believed for a proof they have to opt into. For people further along than me: - Did whatever you used pre-proof actually convert, or did conversion only really start once real proof existed? - Has anyone taken option ...

... selecting anything. Tick boxes stay invisible until they're wanted they fade in on hover, and their slot is always reserved, so nothing jumps around. Minimalism is a lifestyle. "Select all" stops at what's actually loaded. Skim has no undo, and archiving 4,000 emails you never laid eyes on is not a feature, it's an incident. Fixed The list no longer eats messages while you scroll. Paging counted from the visible rows, so every optimistic archive quietly ...

... solo dev who's spent way too many nights rage-closing YouTube tabs 8 minutes into a video that had 30 seconds of actual signal. That frustration turned into Focal a browser extension that gives you a WATCH / SKIM / SKIP verdict on any YouTube video before you click play. Hover a thumbnail, it reads the transcript, scores information density, and pulls out timestamped bullets and key moments. You can even apply a "lens" like just the steps or no fluff ...

... scoring candidates against job postings with AI, and I keep going back and forth on this: a bare percentage feels untrustworthy no matter how good the model is, but a full paragraph of reasoning is too slow to skim across 50 profiles. Landed on a point-by-point checklist (what's met, what's missing) as a middle ground, but curious how others handle this. If a tool told you "73% match," would you trust it without seeing why? Where ... ... enough for ranking. If it decides anything on its own, no amount of reasoning text would save it. Your checklist is the right call, but I'd flip the emphasis: show the misses, not the matches. When I skim

... where Skim stops reading the CSS and starts reading the letter. A tiny release: one fix, one heuristic, zero new buttons. Still standing on @gildas-refacto 's shoulders All of v1.0.19 was theirs #30 , their fourth merged PR after #16 , #18 and #29 , where they traced three separate translation bugs down to individual Unicode code points and measured every fix over 20 runs. Which made this release slightly embarrassing to write: they spent all that effort making the translation trustworthy ... ... mail that needs it. Some senders build their plain-text version by ripping the tags out of their own HTML <style> element included so the email "text" opens with a few hundred characters of .bio{margin:auto}. Skim

... message on the last base64 chunk and just walk away, never writing the closing --boundary--. The MIME parser reads that as "this part is broken", quietly demotes your email to an attachment, and hands us nothing to show. Skim now closes those dangling multiparts itself (innermost first, like a polite houseguest turning off the lights) and parses again. Your booking confirmations are back. No more phantom attachment. That mystery .bin full of raw base64 sitting under the empty email ... ... longer latch forever. The old code cached "I fetched this" and "there's genuinely nothing here" as the same thing, so a message that failed to parse once stayed broken until the heat death of the universe. Now Skim

... where Skim stops impersonating a corpse. A self-update could relaunch Skim

... where a foreign-language email stops being a research project. Press T , read it. That's the whole feature. New Translate an email in place Skim now notices when a message isn't in your language and offers to translate it right there : subject and body, in the reading pane, where the email already was. No copy-pasting into the Ask panel, no reading your mail as a chat bubble. Hit T, or click the offer. "Show original ...

... where Skim stops insisting the model is loading while it is, in fact, sitting there thinking very hard. Turns out silence has two meanings, and we only knew one of them. Entirely the work of @gildas-refacto in #28 thank you! Fixed "The model is loading " was a lie. Skim

... years by people who cared about how it feels to use. Dark, considered interfaces. Whitespace that isn't accidental. Content that is the product, not decoration bolted onto a spreadsheet. The short answer to "what's the best LinkedIn alternative in 2026" is this: builders aren't looking for another feed. They're looking for a professional network that was actually designed, not just maintained. That's the gap forg.to is built to close. Here's why the gap exists ... ... launch thread, not a bullet point None of that has a native home on LinkedIn. You end up copy-pasting links into an "About" section that was never designed to hold them, hoping someone actually clicks through instead of skimming

... where Skim learns to smell a phishing email from across the room and does it all locally, offline, without phoning a single reputation service. Your inbox, now with a healthy sense of suspicion. New Phishing detection, built right in. Skim

... where mail can finally go somewhere. Skim has happily read your folders since forever, but putting a message into one? Not supported. Slightly awkward for an email client. Fixed. New Move to folder new toolbar button, or V / Ctrl+K for a palette-style picker. Type, hit Enter, done. Create a folder while moving no folder named "Taxes" yet? Type it, it gets created and the mail lands in it. Works offline too, because of course the move rides ... ... Enter won't accidentally invent a folder while a real match is sitting right there that row never steals the highlight. Rename & delete your own folders a small button next to the list header. Your folders only; Skim

... already downloaded before you click it. Turns out the fastest way to fetch a message is to have fetched it earlier. Nobel committee, we're waiting. Faster New mail arrives with its body attached. When a message lands, Skim quietly pulls the body onto the fetch connection right away newest first, small ones only, three at a time. So tapping that notification is now a read from your own disk instead of a chat with the server. The connection wakes ... ... when you do. Alt-tab back to Skim

... The one where your email finally gets to use the whole window instead of huddling in a 840px column on ...

... where Skim finally admits your mailbox didn't begin 500 emails ago. Turns out there was mail before that. Who knew. New Your whole mail history, actually downloaded. Until now the first sync grabbed the newest window (500 in the inbox, 200 elsewhere) and then only ever looked forward . Everything older sat on the server, invisible to search and to the assistant, forever. Skim

... where Skim finally learns that not every mail server hides behind implicit TLS. Turns out port 143 has feelings too. Fixed IMAP on port 143 now just works. Type 143 and Skim

... where setting up a local AI brain stops being a spelling test pick a chip, done. And it's a special one: this is Skim's first release built on a pull request from an outside contributor . Huge thanks to @gildas-refacto Gildas Pottier found Skim

... monitor while the main app stays usable is a genuinely practical improvement . Comment from Elsie Ramsey(@elsie_ramsey): I've tested plenty of chat apps, and the biggest frustration for me has always been losing momentum during longer discussions. Skim's "Chat, unchained" instantly caught my attention ...

... where Skim stops being picky about which AI you talk to, and the whole app goes on a diet at the same time. Efficiency and choice, in one download. You're welcome. New Bring your own AI endpoint (OpenAI-compatible). A third provider joins Anthropic and OpenRouter: point Skim

... Small update, but a big quality-of-life one: Skim now handles multiple mailboxes at once without turning into a giant multi-account control panel. What's new: Multiple accounts, one calm app. Connect as many mailboxes as you like. A slim switcher shows up in the titlebar only when you have more than one, with a per-inbox unread hint. Ctrl + 1 9 to jump straight to the Nth mailbox. Everything lands in the right place toast clicks, search ... ... that owns the message before opening it. Search & compose stay scoped to the mailbox you're looking at no more "sent from the wrong address" moments. No duplicate accounts try to add one that's already connected and Skim