... 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

... conversation open while reading emails on another screen sound much more comfortable. 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

... account switcher and every connected mailbox pours into a single, date-sorted list of messages and threads. No more clicking between accounts like it's 2009. From picker in compose replying or writing fresh from the unified view? Skim now lets you choose which account it goes out from, so your work self doesn't accidentally email your mom's book club. Housekeeping Added date-sorted indexes on messages and threads so the cross-account query stays snappy even when ...

... Every business I run generates something on a schedule, a weekly summary, a sales recap, an ops checklist nobody asked for but someone still sends. In the beginning I read every line. Now I skim the subject and archive it without opening, because nothing has looked different in months. The part that bothers me is I cannot actually remember the last time I checked whether that assumption was still true. Curious whether you have one of these too, the report ...

... Been thinking about this a lot. Two years ago, if I wanted to find or evaluate something, I'd Google it, skim a few links, maybe check a review site. Now a good chunk of that happens in a chat window. I ask ChatGPT or Perplexity directly and just get an answer, sometimes with zero clicks to any actual website. It feels like a pretty fundamental shift in how people find things, not just a new feature. Curious if others ...

... Which letter are you, and what did it cost you to find out? I will come back in a few weeks and post the spread. Comment from Aria(@ariajinling): I agree: degradation has to be an explicit, author-authored alternative, not a timeout-time improvisation. If an action has no degraded form, it needs a stronger escalation path or a shorter approval window. For partial work, I would preserve a compact execution ledger: completed steps, external effects, and the invariants ... ... nothing, the reviewer's normal experience becomes an empty screen, and empty screens train people to expect empty. Whether the one that is not empty gets read properly on day forty is an open question. It still beats the alternative

... honest self-assessment time. when an agent finishes a task and shows you a diff, what actually happens? for me it depends entirely on the size. under ~30 lines I read every line. past that I mostly skim for anything that touches auth, payments, or migrations and trust the rest if tests pass. I know that's not a great policy, it's just the realistic one given how much code moves through these sessions in a day. curious where ... ... been fine so far? Comment from Samuel Abiodun(@abiodunt97): I've been programming about 10 years now, so I just have a habit of wanting to know what the LLM has produced. I at least skim

... upvote, that s the most honest signal there is. Someone can only find the real gap if they understood what you built and why. What was the gap? Comment from Rahil Pirani(@rahilpirani): @omri_ben_shoham1 Launch day comments vs. the question that could only come from someone who actually used it, you feel the difference immediately. I had someone ask me why Second Brain classifies memories as episodic vs

... every user's email. When I asked the AI about it, it called that 'partial user data'. So now I sort by what data the code can reach instead of which feature it sits in. Pure layout gets the skim, anything that builds a query or a view gets the billing-grade read. Comment from Ankit Kumar(@ankitttbuilds): I don't follow any framework to review the code but when creating a new project i just define ... ... features, way more surface area for that to happen unnoticed. Comment from King Joshua Marcos(@moddy): Honestly just trial and error early on. Let it fully own something low stakes, watched what broke, adjusted from there. The billing/auth vs

... would hold their attention for twenty minutes instead of forty seconds. That is the entire premise. Not where you've worked. What you've built. The Real Answer Is Not Either/Or In 2026, the strongest combination is not resume versus profile. It is resume plus profile. One gets you noticed in the first seven seconds of a scan. The other gets you remembered for the twenty minutes after that, and it is the twenty minutes that actually decide whether ... ... worded bullet points. Polish used to signal effort. Now it signals access to ChatGPT. Do you think the resume survives this at all, or does it quietly become a formality? Comment from Nolan Vu(@nolan_vu): The "20 minutes vs

... found that naming the specific moment worked better than naming the category, not poor visibility across multiple businesses but I found out three weeks later a client never got a reply. That specific moment made people nod instead of skim past. Do you find the same holds for problems that are about attention instead of a broken workflow? Comment from Stacy Wycoff(@stacywycof83995): For FounderFlow the problem is not unclear, it is invisible until it is too late. Founders running ... ... each bad hire costs over 200k. must have problem for HR. three. the 92 percent of work that linkedin never covered. plumbers, nurses, electricians have never had a portable record. that is the most must have segment because the alternative