[{"channel_id":1309924870,"post_id":2330,"date":1789671049000,"forwards":"6","views":"2.1K","text":"GigaChat 3.5 Reasoning<\/b>: Advanced step-by-step problem solving
\u00a0
GigaChat 3.5 Reasoning is a new open-source LLM designed to reason<\/b>, not just respond. Built on GigaChat 3.5 Ultra, it processes math and coding tasks by exploring multiple step-by-step reasoning paths, using automated verification to reinforce correct trajectories<\/b>. This enables autonomous multi-step planning, external tool invocation, and self-correction.

The model features a proprietary linear attention architecture, optimizing long-context efficiency by retaining key processed points rather than re-matching from scratch. It is highly token-efficient, consuming on average 37% fewer tokens than DeepSeek V4 Flash Preview<\/b> on math problems.

Benchmark gains over the non-reasoning version:
\u2022 IFBench: 44 \u2192 77
\u2022 Natural Plan: 64 \u2192 80
\u2022 LiveCodeBench v6: 56 \u2192 85

Open-sourced under the MIT license. Weights available on Hugging Face: fp8<\/u><\/b><\/a> | <\/b>bf16<\/u><\/b><\/a>","text_length":913,"media":{"root":"\/013\/GgkAAAbeE04AAAAAMqK73gmybm4","video":{"duration":30,"w":1080,"h":1920,"is_animation":false,"is_round":false,"mime_type":"video\/mp4","size":9433365,"thumbs":{"m":{"w":180,"h":320,"hash":"bwaTdM9-dwiLn_1gp7rOhg&ts=1789857462"},"i":{"bytes":"AoABY|DKpaKKAEopaKAEop+w0m00AJRUqxEiiiwFnaPSmmMZoopJmF2OAxRRRVXHdn\/\/2Q=="}},"streamable":true,"televisor_hash":"g_DwSSZfCjBCWONU1HnXpg&ts=1789857462"}}},{"channel_id":1309924870,"post_id":2329,"date":1789671049000,"forwards":"1","views":"2.0K","text":"#promo","text_length":6},{"channel_id":1309924870,"post_id":2328,"date":1789569616000,"forwards":"7","views":"3.5K","text":"Dates Are Not Data, They Are Context \u00b7 Nikhil Gautam<\/b><\/a>
<\/a>
A developer recounts a bug where a billing report showed bills from the wrong day due to a timezone mismatch: the frontend sent plain calendar dates (e.g. '2026-01-01') without timezone context, and the backend converted them directly to JavaScript Date objects while MongoDB stored timestamps in UTC. The core lesson is that a calendar date is not the same as a timestamp - a date needs a timezone to be meaningful, and query boundaries should be computed in the user's local timezone before converting to UTC. Also covers using half-open [start, end) ranges to avoid excluding the last day of a range, and a mental model separating calendar dates, timestamps, and local date\/time.<\/a><\/blockquote>","text_length":735,"media":{"root":"\/003\/GAkAAAbeE04AAAAAWNXOBSH-E4Y","photo":{"thumbs":{"m":{"w":320,"h":180,"hash":"gWceQ_dQQDwgCQvYl1zA9A&ts=1789857462"},"x":{"w":800,"h":450,"hash":"sja9iPmkVjUKLW0v30WNNQ&ts=1789857462"},"i":{"bytes":"AXACg|DTefYxXy3OO4FIbkDOI5Dj0WoponNxuVM8g5yKVbYOWLqVLE8A\/X\/GgCwkm6MNtYZ7Ec0u4UiRiJNq9Pemudg3H1A\/M4oAkBzRTVHOeaKAHYpcUUUAIee9Mki8xNpOBkHiiigCSiiigD\/\/2Q=="}}}}},{"channel_id":1309924870,"post_id":2327,"date":1789408882000,"forwards":"3","views":"5.2K","text":"\ud83e\uddf2 Forty tabs open and none of them is the answer.

Docs, someone's gist, a five-year-old Stack Overflow thread. The search isn't the work \u2014 putting it together is, and that part is still on you.

Create your own AI agent inside Telegram in about a minute.

\u25ab\ufe0f paste the error and get the reason explained, not another snippet to try
\u25ab\ufe0f send a repo link or a doc page and ask what it actually does
\u25ab\ufe0f it writes the throwaway script you need and runs it right in the chat \u2014 parser, converter, quick report
\u25ab\ufe0f describe the task by voice on the way home, read the answer when you are back
\u25ab\ufe0f it keeps your project, your stack and your past decisions in memory for months
\u25ab\ufe0f any model from the world's providers, switched with one command

Setup takes a minute: open the link and name your agent.
Free to use \u2014 no card needed.

\ud83e\uddf2 Try your own agent<\/a>","text_length":845,"media":{"root":"\/00d\/FwkAAAbeE04AAAAAQEXMw-gYUQs","video":{"duration":14,"w":848,"h":848,"is_animation":false,"is_round":false,"mime_type":"video\/mp4","size":2534647,"thumbs":{"m":{"w":320,"h":320,"hash":"xBpHhHJO2l2SITEY_3atgQ&ts=1789857462"},"i":{"bytes":"AoACg|DLGKXj0pKUAkgDqaRoBHtTDxWsG077MAQPM2c8HOcVlMCGIPUUyRpxRSUUCJBS0gp1Iq4pc9cDd\/e71GRUmKaRVITGYop2KKdiRVxTqKKgoKQ4ooqkJiE8YzRRRVCP\/9k="}},"streamable":true,"televisor_hash":"Knx6igpkdFvpC7oDPMrWag&ts=1789857462"}}},{"channel_id":1309924870,"post_id":2326,"date":1789408882000,"forwards":"1","views":"4.3K","text":"#promo","text_length":6},{"channel_id":1309924870,"post_id":2325,"date":1789396821000,"forwards":"4","views":"5.0K","text":"React 19.3 \u2013 React<\/b><\/a>
<\/b>
React 19.3 is now available on npm, stabilizing two previously experimental APIs: View Transitions and Fragment Refs. The new <ViewTransition> component animates elements entering, exiting, moving, or resizing using the browser's View Transition API, with support for custom animations via addTransitionType and integration with Suspense for coordinated loading of fallbacks, images, and fonts. Fragment Refs let developers attach DOM behaviors (event listeners, focus management, IntersectionObserver\/ResizeObserver) to a group of sibling elements without needing a wrapper div, by passing a ref to a Fragment. React DOM adds a new browser() API to opt components out of server-side rendering when they depend on browser-only APIs, plus Trusted Types support to prevent DOM-based XSS. Server Components can now render Context directly from a 'use client' module without a wrapper Provider. The release also includes numerous other changelog items and bug fixes across react, react-dom, and react-server<\/blockquote>","text_length":1022,"media":{"root":"\/012\/FQkAAAbeE04AAAAAdwkNYtUDtPg","photo":{"thumbs":{"m":{"w":320,"h":168,"hash":"CJWU5jUb9C0-vXCe2Zvs-w&ts=1789857462"},"x":{"w":800,"h":420,"hash":"9aVCKfdHP28aakywhjAuYA&ts=1789857462"},"i":{"bytes":"AVACg|CiuzHIP4Gg4zxnHvSo6BcNHk565xThJGGz5WRjoWpiIjSU5iD0GKbQMSiiigBc8UUUUAFJRRQAUUUUAf\/Z"}}}}},{"channel_id":1309924870,"post_id":2324,"date":1789234522000,"forwards":"8","views":"6.0K","text":"Scaling Down Costs, Not Performance: How We Migrated from Couchbase to PostgreSQL<\/b><\/a>
<\/b>
Trendyol's product content team details a phased, zero-downtime migration of five 'helper bucket' datasets (2.24 billion documents across two clusters) from Couchbase to PostgreSQL to cut infrastructure costs while preserving read performance. The strategy combined dual-writes via Kafka consumers, a custom CDC-based migrator tool for historical backfill, and feature-flagged cutover of read traffic. Key production challenges included a mysterious TPS spike traced to PgBouncer's server_reset_query_always setting, a connection-limit incident causing a primary node failover, and a hidden scaling issue where PgBouncer's own horizontal autoscaling multiplied backend connections beyond expectations (20 pods \u00d7 150 default_pool_size = 3000 potential connections). Final production benchmarks showed stable P50 latency and only a brief P99 spike (200ms to 400ms) under peak load, validating the migration.<\/blockquote>","text_length":987,"media":{"root":"\/00e\/FAkAAAbeE04AAAAAx1g8cIJsBIk","photo":{"thumbs":{"m":{"w":320,"h":158,"hash":"cbJyorTdfDzwznqjYmD6aw&ts=1789857462"},"x":{"w":800,"h":395,"hash":"JUUTlCgO7dIpSbEFJiPj8g&ts=1789857462"},"i":{"bytes":"AUACg|DIVSx4pWQrToWKngdalaUgAbR+VK7uaqMXG5XCk1MI1A5BPOOKd9pbGNif98inBi8RYqPlNbRSOeTdyvIoU8UUjsWbOKKh7lIEPJ+lK5OBRRUdTZfCNBNSKTt69aKK2iYSI260UUVDGj\/\/2Q=="}}}}},{"channel_id":1309924870,"post_id":2323,"date":1789224170000,"forwards":"3","views":"5.6K","text":"Bun v1.4.2<\/b><\/a>
<\/b>
Bun v1.4.2 patches two regressions introduced in v1.4.1: a bun build variable name collision that broke Elysia imports with a SyntaxError, and an AsyncLocalStorage memory leak affecting timers and promises created inside store.exit() or nested store.run<\/a>(). It also fixes a worker_threads 'online' event ordering bug that caused @discordjs<\/a>\/ws to hang, adds CMYK\/YCCK JPEG decoding support to Bun.Image, pulls in roughly 350 upstream WebKit\/JavaScriptCore commits fixing Intl, TypedArray, and Proxy correctness issues, and resolves several crash and hang bugs including a rare JIT crash, a musl GC crash, a bun install panic, and a double-close file descriptor bug on Linux<\/blockquote>","text_length":682,"media":{"root":"\/001\/EwkAAAbeE04AAAAAprshwa7jb_4","photo":{"thumbs":{"m":{"w":320,"h":168,"hash":"k-a81eNum07wft1jOEdX1g&ts=1789857462"},"x":{"w":800,"h":420,"hash":"7V9ZB3UTySVtLqsy-xca9A&ts=1789857462"},"i":{"bytes":"AVACg|DUZZSxKygD025xUtUp77yLnyzGSuByPelW+VwSInHzbef8\/WgC5TJGKjjvVZb0ExfLgOvJ7A46ZqWB\/tNursMbs9D70AKko3qpOd2QOKKckKI5YAljxkkk\/rRQA\/k9yKOfU0UUALj3NFFFABRRRQB\/\/9k="}}}}},{"channel_id":1309924870,"post_id":2322,"date":1788978020000,"forwards":"7","views":"7.9K","text":"Build with Tailscale using tsnet, APIs, and automated sharing<\/b><\/a>
<\/b>
Tailscale is expanding from a network you configure into a platform you build with and on. The tsnet Go library lets applications embed Tailscale connectivity directly, giving each app its own tailnet identity, MagicDNS name, and automatic TLS certificates without opening ports or managing proxies. A tailscale-rs library is in pre-alpha, promising bindings for Rust, Python, Elixir, and C. On the automation side, the Tailnets API lets teams provision isolated tailnets on demand for per-customer or per-test isolation, and the same APIs power a new admin console so ACL updates, key rotation, and provisioning can be scripted rather than clicked. A new Declarative Node Sharing feature turns manual cross-tailnet sharing into GitOps-managed policy, currently available via waitlist.<\/blockquote>","text_length":847,"media":{"root":"\/001\/EgkAAAbeE04AAAAAprshwa7jb_4","photo":{"thumbs":{"m":{"w":320,"h":165,"hash":"pBdyXqx-pDdfytOyklT5Tg&ts=1789857462"},"x":{"w":800,"h":413,"hash":"0ei9J1-_sH73ZqpzHA-Ebg&ts=1789857462"},"i":{"bytes":"AUACg|DPV4gmGiLN67sUjPEcbYyPX5s1IjDyQpC899oz\/OmCNP7x\/T\/GgBbdVdwpXtz70bk7IKdbBRPwSeO9QjPNBO7HlwRgIBRTQpIzg4HeigTsIJXUYBwB\/jSmRmBBPUelFFBY1XZGyp5xUnnP7fkKKKCJC+axUg4wfaiiigk\/\/9k="}}}}},{"channel_id":1309924870,"post_id":2321,"date":1788891618000,"forwards":"1","views":"8.4K","text":"What\u2019s new in Svelte: September 2026<\/b><\/a>
<\/b>
Svelte 5.57 adds new SvelteMap methods (getOrInsert, getOrInsertComputed), a createContext has function, select defaultValue support, and new svelte\/server type exports. SvelteKit 3's next release candidate continues iterating with several breaking changes including reworked cross-page form actions, split Vite plugin hooks, defineParams relocation, and route filtering for test files. The sv CLI replaces its mcp add-on with a broader ai-tools add-on and ships a task-based sveltekit-3 migration command that rewrites $lib imports to #lib and bumps dependencies. The roundup also covers stable SvelteKit 2.x patches, language tools updates, and a community showcase of Svelte apps, UI libraries, and dev tools.<\/blockquote>","text_length":749,"media":{"root":"\/00d\/EQkAAAbeE04AAAAAQEXMw-gYUQs","photo":{"thumbs":{"m":{"w":320,"h":168,"hash":"UGWddmjGGvJOJaAbrNkkRg&ts=1789857462"},"x":{"w":800,"h":420,"hash":"Jx4-OGesHpi1IOFoDvi60Q&ts=1789857462"},"i":{"bytes":"AVACg|DUklKMR8v4nFJ53P8AD9d1SMuTnJ\/A07igBiSo2BuGT2BpjzhTtVSxzg+gqQuo6sPzrMnuNs8mCME+pGaTGlc0I5g5II2kcnNFU7UGZ9zAhcYGOBRTQMdG0svWUinm1Ei4d2YUUUyST7LHwTkkdKf5EZ6opx6jNFFAyRVAooopAf\/Z"}}}}},{"channel_id":1309924870,"post_id":2320,"date":1788805223000,"forwards":"8","views":"8.2K","text":"First Look at <\/b>@nestjs<\/b><\/a>\/observe in NestJS 12
<\/b>
<\/a>
NestJS<\/a> 12 comes with some solid updates, no doubt about that. But if you haven\u2019t looked at the new observability features yet, it is worth a close look.
Setting up APM tools in Node has always felt a bit clunky. Most agents sit outside the app, monkey-patching HTTP drivers and database packages to guess what is happening under the hood. It works, but you usually lose framework context along the way.
Full Article : https:\/\/lnkd.in\/p\/gP53bYmC<\/a><\/blockquote>","text_length":488,"media":{"root":"\/00d\/EAkAAAbeE04AAAAAQEXMw-gYUQs","photo":{"thumbs":{"m":{"w":320,"h":180,"hash":"DeY6bl4O8C0pLnJkp6TXJg&ts=1789857462"},"x":{"w":800,"h":450,"hash":"6qet15aKc9Rs_msiCk8xTw&ts=1789857462"},"i":{"bytes":"AXACg|DJooqZYUZM+coOOhoAiyMYxz60lTCFCSPOXikMSBC3mgkdhQBFRRRQAUUUUAFFFFABRRRQB\/\/Z"}}}}},{"channel_id":1309924870,"post_id":2319,"date":1788728596000,"forwards":"5","views":"12.0K","text":"Hello everyone some of you may not know but now we started to expand to WhatsApp and we are inviting you to join our WhatsApp channel link here \ud83d\udc47\ud83d\udc47\ud83d\udc47\ud83d\udc47\ud83d\udc47<\/del>

WhatsApp Computer Science and Technology <\/a>

We welcome you all to be part of this family<\/del>","text_length":243},{"channel_id":1309924870,"post_id":2318,"date":1788718801000,"forwards":"9","views":"9.3K","text":"New system views in PostgreSQL 19<\/b><\/a>
<\/b>
PostgreSQL 19 introduces four new system views for observability: pg_stat_lock provides cumulative cluster-wide lock contention statistics per lock type, including a fastpath_exceeded counter useful for partition-heavy workloads; pg_stat_recovery gives a single atomic snapshot of standby recovery state (replay LSNs, timelines, pause state, promotion status), replacing the need to combine several inconsistent functions;pg_stat_autovacuum_sc exposes the new per-table scoring system (based on XID age, multixact age, dead tuples, inserts, and analyze staleness) that now determines autovacuum table processing order, replacing the old pg_class ordering; and pg_dsm_registry_allocations lists dynamic shared memory registry entries (name, type, size) used by extensions that no longer need shared_preload_libraries and a restart. The piece walks through each view's schema and runs live demo queries showing sample output. PostgreSQL 19 is still in beta and details may change before GA.<\/blockquote>","text_length":1022,"media":{"root":"\/00b\/DgkAAAbeE04AAAAAqBm7FFhvF9Q","photo":{"thumbs":{"m":{"w":320,"h":168,"hash":"RC20QtsWdi8rV7Xn0FNUgA&ts=1789857462"},"x":{"w":800,"h":419,"hash":"EIfhZbIY8cnKKitqtRfCSQ&ts=1789857462"},"i":{"bytes":"AVACg|DREilipZgc9xxTwy\/3gaovZZd28sNuJPb\/AApF08bsMg2+wU\/0rl5Y9xk2obTbAMTtZgDis3yIPWX8hVm+BgsIl6EOOM57Gqi3EqoNpODzxWsFoBAVIzwcfSilkkaRst1xiitBHR7aNtFFc93YZR1Z1SNA6bxk98VjmQ7jsJVc8AHpRRW0PhEIXY8FiQfU0UUVYH\/\/2Q=="}}}}},{"channel_id":1309924870,"post_id":2317,"date":1788456875000,"forwards":"5","views":"10.7K","text":"The best dark mode toggle is probably none \u2022 Lea Verou<\/b><\/a>
<\/b>
Building on an earlier post advocating two-state (rather than tri-state) dark mode toggles, the author now argues that most websites shouldn't have a persistent dark mode toggle at all \u2014 the setting should default to following the OS and live in a settings panel instead. The piece responds point by point to Bramus's counter-argument for tri-state toggles (a scenario involving OS auto-switching plus reverted selections), calling it rare, cheaply recoverable, and a case of developers overweighting their own edge cases (IKEA effect meeting false-consensus bias). It also surveys community-designed alternative toggles (Vale's 3-in-2 design,<\/blockquote>","text_length":698,"media":{"root":"\/00b\/DQkAAAbeE04AAAAAqBm7FFhvF9Q","photo":{"thumbs":{"m":{"w":320,"h":242,"hash":"tdWzHAgZnH75EyHsndyitA&ts=1789857462"},"x":{"w":800,"h":604,"hash":"BPi7vnsW_CzPtCzHfYzjiQ&ts=1789857462"},"i":{"bytes":"AeACg|DZooqrcysmEiA8xs49sUDSuWqKz0DvHvjlcuOqt6\/SrcMolhV14z2oG42JaKKKCQqtcI29JEUsyZ49Qas0UAnYzndnlDRRukh4O4YB+tW7aLyoFQ4OPSpqKCnK6sFFFFBJ\/9k="}}}}},{"channel_id":1309924870,"post_id":2316,"date":1788328209000,"forwards":"3","views":"11.4K","text":"Cancel In-Flight Form Submissions in Inertia.js v3.7<\/b><\/a>
<\/b>
Inertia.js v3.7.0 adds a cancelOnUnmount attribute and a cancel method to the Form component so in-flight submissions can be aborted when a form unmounts or via a button click. usePoll now exposes a reactive polling value across Vue, React, and Svelte. Once props no longer lose their value during instant visits, and navigation no longer cancels background async visits aimed at other pages. Three fixes address a React back_forward stale-props bug, prop identity issues in replaceProp\/appendToProp\/prependToProp, and a Form unmount crash in React.<\/blockquote>","text_length":602,"media":{"root":"\/013\/DAkAAAbeE04AAAAAMqK73gmybm4","photo":{"thumbs":{"m":{"w":320,"h":160,"hash":"KXKa84Qb96h0ZXKc3F4JMw&ts=1789857462"},"x":{"w":800,"h":400,"hash":"69CxRTt77ea871KOWgQbcw&ts=1789857462"},"i":{"bytes":"AUACg|Cns4oWPI4qUYNWopIxjKrXSxFVFKHNWFmJ6mnySxkA7Fqm8wAYBBknr6Ug3JZZcd6Kqb8nmikwsSKTigsciiiqGIztzzUJPNFFJgOVvkZcDk9e9FFFZos\/\/9k="}}}}}]