AllyshipContent Radar

News 2934

Chủ đề cộng đồng đang thảo luận

Crawl live-1795137300000 · 08:15 20 thg 11, 2026 · Xuất bản 08:31 20 thg 11, 2026

213 / 2934 chủ đề đạt ngưỡng 55 trong khoảng này.

41

Anthropic should give stock to Stack Overflow (and OpenAI too)

61

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 6 tương tác đã đo · Nguồn crawl

thetjmccarty 1 bài viết · HN: LLM
Nguyên văn nguồn
Chi tiết nguồn

Anthropic and OpenAI should give Stack Overflow a percentage of their company. They used all of Stack Overflow's data to train their AI models at the beginning of LLMs without paying for it because it was publicly available online. ChatGPT and Claude would not exist today without the 24 million coding questions and 36 million answers with code examples included, all created by real humans who took the time to write the questions and answers. Stack Overflow deserves to be rewarded for making Anthropic and OpenAI such a success. And all the developers who posted and answered questions on Stack Overflow should be given stock too.

42

In this video, hear from CDS founding director Yann LeCun (@ylecun) about how our graduate programs prepare students for success in industry: a collaborative environment, capstone projects with New Yo

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

nyudatascience 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

In this video, hear from CDS founding director Yann LeCun (@ylecun) about how our graduate programs prepare students for success in industry: a collaborative environment, capstone projects with New York companies, and faculty with industry affiliations. Media

43

Genie 4 is the first model we launched on the new Live Interactions API, bringing native WebRTC (with ephemeral tokens) and WebSocket support directly to Interactions and Gemini API.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

_philschmid 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Genie 4 is the first model we launched on the new Live Interactions API, bringing native WebRTC (with ephemeral tokens) and WebSocket support directly to Interactions and Gemini API. This is part of our ongoing work to improve Gemini API experience. When we started building the Interactions API, one of our main goals was making sure standard API calls and real-time and long running sessions share one consistent interface. We put a lot of effort into getting the primitives right, and we have big plans. I would love your feedback as we build this out: what do you want to see as we bring protocols like WebSockets and WebRTC to more Gemini models? What is still missing for building better agent experiences or real-time apps? In the meantime, you can try Genie 4 in the docs: https://aistudio.google.com/docs/genie Media

45

Playing GTA & not following the Anthropic IPO? Following the IPO & not playing GTA?

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Ethan Mollick 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Playing GTA & not following the Anthropic IPO? Following the IPO & not playing GTA? Why not both? I had Fable make a thing where you steal cars & go on missions in a world where everything from your wanted level to weather is driven by ANT's stock price https://market-order-city.netlify.app/ Media

46

Watch → https://goo.gle/4AIPYYS

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Google DeepMind 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Watch → https://goo.gle/4AIPYYS Spotify → https://goo.gle/4iSB5x5 Apple Podcasts → https://goo.gle/4iSrk21 Or listen wherever you get your podcasts! 🎧

47

Our SVP @koraykv believes there won't be a single test or benchmark that tells us we've reached AGI. Instead, progress looks like models becoming less spiky and more reliable across our daily lives.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Google DeepMind 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Our SVP @koraykv believes there won't be a single test or benchmark that tells us we've reached AGI. Instead, progress looks like models becoming less spiky and more reliable across our daily lives. Listen in as he and @fryrsquared discuss the road ahead ↓ Timecodes: 00:00 Introduction 01:26 Evolution of Google DeepMind 04:41 Products as a path to AGI 13:01 Architectures and models 24:40 Recursive self improvement 30:50 Safety and agent teams 40:35 Benchmarks Media

48

Introducing Higgsfield GPU Harness.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

higgsfield 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Introducing Higgsfield GPU Harness. Rent on-demand GPUs in Claude and ChatGPT to render, run open-weight models and train LoRAs. Let several AI agents work on your professional apps in the cloud at once, from any device. Black Friday deal, live now: get GPUs at up to 64% OFF. Media

49

How much do you automate your life? (2)

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

luongnv89 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

How much do you automate your life? (2) This is how i consume articles and blog posts nowadays - send the link to my bot on Telegram, it become a core subject of a new podcast episode - a bot goes looking for other sources: some explain the ideas more simply, some bring data, some disagree =>full picture, not just one opinion - a bot writes a 2-host podcast (Bob and Alice, heygen voice, free from @OpenRouter, thank to @HeyGen ) checks every fact against its source, and explains the hard parts with simple metaphors - the episode goes live on http://luongnv.com/podcast - if one topic really catches me and I want to dig deeper: one command sends the original article to my reMarkable as a clean PDF, so I can read it slowly and take notes with a pen (the skill is open source: http://github.com/luongnv89/remarkable-skills) I send a link, I get a podcast. Everything else is automatic Here is the latest one on verification from @addyosmani , super interesting https://luongnv.com/podcast/episodes/2026-11-19_how-the-claude-code-team-thinks-about/

50

QDA: Closed-Loop LLM Quantization Design with Agents

86

5 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · 9 tương tác đã đo · Nguồn crawl

Xingyang Li, Tianlang Zhao và 3 nguồn khác 1 bài viết · Hugging Face Papers, X
Biên tập tiếng Việt
Chi tiết nguồn

Bài báo nêu rằng post-training quantization là cách tiêu chuẩn để phục vụ LLM với chi phí thấp, nhưng công thức quantization tốt phụ thuộc vào từng mô hình và độ chính xác, nên chuyên gia phải thiết kế lại cho mỗi mô hình. Họ giới thiệu QDA, nơi một agent thiết kế recipe cho từng mô hình và độ chính xác. QDA đánh giá nhanh bằng cách chấm candidate theo KL divergence đầu ra so với mô hình gốc trên reasoning traces mà agent không thấy, và kiểm tra thêm các candidate hứa hẹn bằng long generations để bắt lỗi như repetition loops.

Post-training quantization is the standard way to serve large language models at low cost. However, the best quantization recipe differs across models and precisions. As a result, experts must redesign it for every new model, which is time-consuming and often sub-optimal. Fortunately, an LLM agent can take over this design by refining the recipe over rounds of building and evaluating candidates, so that more rounds lead to better recipes. However, evaluating one quantized reasoning model takes tens of GPU-hours, and combining methods from different codebases means porting each to the new architecture by hand. We present QDA, a system in which an agent designs the recipe for each model and precision. To make evaluation fast, QDA scores each candidate in minutes by its output KL divergence from the original model on reasoning traces that the agent never sees, and checks promising ones with long generations to catch failures such as repetition loops. To make building fast, QDA provides a library of public PTQ methods that are compatible with one another and with new model architectures. Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search. On the 320B-parameter MoE model GLM-5.3-Flash at NVFP4 W4A4, it recovers 98.3% of the FP8 model's accuracy, against 96.9% for the best vendor checkpoint. Every QDA checkpoint also runs on existing serving kernels with no inference overhead. We will release the library, the evaluator and the harness.

  • Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search.
  • Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search.
  • On the 320B-parameter MoE model GLM-5.3-Flash at NVFP4 W4A4, it recovers 98.3% of the FP8 model's accuracy, against 96.9% for the best vendor checkpoint.
  • Every QDA checkpoint also runs on existing serving kernels with no inference overhead.
51

PostgreSQL 19 Released

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Simon Willison 1 bài viết · Simon Willison
Nguyên văn nguồn
Chi tiết nguồn

<p><strong><a href="https://www.postgresql.org/about/news/postgresql-19-released-3449/">PostgreSQL 19 Released</a></strong></p> Most years PostgreSQL ships a new release in September, but this year's release came two months later <a href="https://rhaas.blogspot.com/2026/10/postgres-19-is-late-and-its-ais-fault.html">thanks mainly</a> to the flurry of issues that the PostgreSQL team needed to address as part of the ongoing AI-reported vulnerability apocalypse.</p> <p>This release was definitely worth the wait. My favorite new feature is this one:</p> <blockquote> <p>For applications that send reads to standbys, PostgreSQL 19 adds "read-your-writes" consistency with the new <a href="https://www.postgresql.org/docs/19/sql-wait.html"><code>WAIT FOR LSN</code></a> command. A session on a standby can use <code>WAIT FOR LSN</code> to wait until the standby has replayed the write-ahead log (WAL) up to a specific <a href="https://www.postgresql.org/docs/19/wal-internals.html">log sequence number (LSN)</a> before running a query, so the application can read data it just wrote on the primary.</p> </blockquote> <p>In practice, that looks like this:</p> <pre><code>UPDATE movie SET genre = 'Dramatic' WHERE genre = 'Drama'; SELECT pg_current_wal_insert_lsn(); </code></pre> <p>That returns a value like <code>0/0306EE20</code>. Store that somewhere (a signed cookie would work) such that on a subsequent request your application can do:</p> <pre><code>WAIT FOR LSN '0/0306EE20' WITH (TIMEOUT '0.1s'); SELECT * FROM movie WHERE genre = 'Drama'; </code></pre> <p>The timeout is optional - if you provide one you'll get an error if the replica you are talking to doesn't catch up within the specified time.</p> <p>I first encountered this pattern <a href="https://www.mediawiki.org/wiki/Manual:Database_access#Lag">in Wikipedia</a>, which has a hand-rolled version of this built against MySQL replication:</p> <blockquote> <p>In addition to this, MediaWiki attempts to ensure that the user sees events occurring on the wiki in chronological order. A few seconds of lag can be tolerated, as long as the user sees a consistent picture from subsequent requests. This is done by saving the primary binlog position in the session, and then at the start of each request, waiting for the replica to catch up to that position before doing any reads from it.</p> </blockquote> <p>Here's <a href="https://github.com/wikimedia/mediawiki/blob/1ff78194b182ee4b5b3678f7d9fc9aefd0852cf7/includes/libs/Rdbms/Replication/MysqlReplicationReporter.php#L238-L299">the relevant MediaWiki code</a>, which these days uses MySQL's <a href="https://dev.mysql.com/doc/refman/9.7/en/gtid-functions.html#function_wait-for-executed-gtid-set">WAIT_FOR_EXECUTED_GTID_SET()</a> function and falls back to <a href="https://dev.mysql.com/doc/refman/8.4/en/replication-functions-synchronization.html#function_source-pos-wait">SOURCE_POS_WAIT()</a>. <p><small></small>Via <a href="https://lobste.rs/s/pqyuhk/postgresql_19_released">Lobste.rs</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/mysql">mysql</a>, <a href="https://simonwillison.net/tags/postgresql">postgresql</a>, <a href="https://simonwillison.net/tags/replication">replication</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a>, <a href="https://simonwillison.net/tags/wikipedia">wikipedia</a>, <a href="https://simonwillison.net/tags/ai-security-research">ai-security-research</a></p>

52

Compare the Gemini 4 models with other leading models at: https://artificialanalysis.ai/models/comparisons/gemini-4-neon-vs-gemini-4-carbon

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Compare the Gemini 4 models with other leading models at: https://artificialanalysis.ai/models/comparisons/gemini-4-neon-vs-gemini-4-carbon

53

Neon and Hydrogen occupy all of the Pareto frontiers of Intelligence vs. Cost per Task and Intelligence vs. Time per Task among the three models.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Neon and Hydrogen occupy all of the Pareto frontiers of Intelligence vs. Cost per Task and Intelligence vs. Time per Task among the three models. Between the two, they scale from an Intelligence Index of 27 at $0.29 per task (Hydrogen, low) to 61 at $6.44 per task (Neon, xhigh). Developers have a lot of flexibility to tune for their use cases with effort level. Carbon does not follow this trend, with relatively little difference in Time or Cost per Task between effort levels. Media

54

Out of your element with the new Gemini 4 releases? Here are some key highlights on Gemini 4 Carbon, Neon and Hydrogen

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Out of your element with the new Gemini 4 releases? Here are some key highlights on Gemini 4 Carbon, Neon and Hydrogen Carbon is the highest-priced model ($4/$20 per 1M input/output tokens), followed by Neon ($3/$15) and Hydrogen ($1.50/$7.50). At low effort, Carbon performs the best of the three but uses more tokens. However, Neon and Hydrogen scale more effectively to higher reasoning efforts and have an additional reasoning option (xhigh). Media

55

Reducing Rollout Bottlenecks in Reinforcement Learning with NVIDIA Dynamo

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Amr Elmeleegy 1 bài viết · NVIDIA Developer Blog
Nguyên văn nguồn
Chi tiết nguồn

Reinforcement learning (RL) uses rewards to train models to solve problems and complete tasks more successfully. Inference drives this process. Workers generate... Reinforcement learning (RL) uses rewards to train models to solve problems and complete tasks more successfully. Inference drives this process. Workers generate rollouts: sequences of model outputs, actions, and environment interactions. The RL framework scores the results, updates model weights, and sends those weights back to the workers for the next round. As RL training scales… Source

56

@linear was founded to build a better issue tracker, then $134M in funding and 7 years later, their CEO @karrisaarinen wrote a post titled “Issue tracking is dead”.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

realbasilchatha 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

@linear was founded to build a better issue tracker, then $134M in funding and 7 years later, their CEO @karrisaarinen wrote a post titled “Issue tracking is dead”. I sat down with @cjc (COO, @linear) to talk about how they navigated that and how their GTM strategy evolved over that period. We got into: -why she stopped chasing enterprise deals three weeks after joining -why @linear has never hired a single SDR -why they won't let an LLM answer support tickets fully-autonomously and much, much, more… Enjoy! Timestamps 0:00 Intro 0:51 Meet Cristina Cordova, COO of Linear 1:39 Why Linear hired a COO at 40 people 5:01 Her work trial: a go-to-market plan for Linear 12:11 Crossing enterprise off the company goals 20:00 Why being a database behind an MCP server isn't enough 23:39 Selling after "issue tracking is dead" 34:40 Smaller, flatter teams and no SDRs 36:14 AI-drafted support replies with humans in charge 42:23 Why Linear doesn't do forward deployed engineering 47:53 Why some AI startups hit $100M ARR so fast 50:06 Moving from seats to usage-based pricing 57:07 Trading the 2025 enterprise roadmap for agents 1:03:28 What Linear's moat is now 1:05:54 Why not hire 100 salespeople? 1:08:59 Stripe's 40% rule for engineering headcount Link in the comments. Media

58

Crazy how fast you can pull these things together now.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

fofrai 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Crazy how fast you can pull these things together now. Neon: > Take the monstera character pixel art and turn it into something more of a high-fidelity 3D concept that I can walk around a midcentury modern room Media

59

Self-improving agents are one of the most discussed ideas in AI right now.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

dair_ai 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Self-improving agents are one of the most discussed ideas in AI right now. (bookmark it) This update gate for a personal health assistant rejected 20 of 21 risky self-proposed updates. Researchers built Safe Personal RSI for the Kicker assistant. The agent can only change its own instructions. Model weights and runtime code stay fixed. Each proposed update is tested against the current instructions on 29 executable email, calendar, health, and marketplace cases. Separate probes test authorization reuse, memory, and tool-output injection. Failing cases are repeated, and changes are temporarily undone to find which edit caused the failure. If no version passes, the current instructions stay. One admitted repair for GPT-5.6 Luna cut attack violations from 10.7% to 0% and raised safe task completion from 89.7% to 100%. Under stronger attacks, a repair moved from Qwen2.5-7B to Qwen3-14B, cutting violations from 69.0% to 17.9%. https://arxiv.org/abs/2611.23651 Chat with Paper: https://academy.dair.ai/papers/safe-personal-rsi-evaluating-and-repairing-personal-agent-updates-2611.23651

41–60 / 213
Trang 3 / 11