AllyshipContent Radar

News 2959

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

Crawl live-1795151700000 · 12:15 20 thg 11, 2026 · Xuất bản 12:32 20 thg 11, 2026

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

1

We don't have enough counterfactuals for how science could be done, after all, there is only one scientific community. There is so much to be learned from watching AI agents generate their own approac

56

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

We don't have enough counterfactuals for how science could be done, after all, there is only one scientific community. There is so much to be learned from watching AI agents generate their own approaches, in addition to the science they actually do. https://www.alphaxiv.org/pdf/2611.society-ai-scientists

2

Get started with Hy4:

56

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

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

Get started with Hy4: Docker image: vllm/vllm-openai:hy4 Recipe: https://recipes.vllm.ai/tencent/Hy4 Thanks to @TencentHunyuan, @inferact, @NVIDIA and the vLLM community! 4/4

5

有人把 App Store 和 Google Play 的 123 种拒审坑做成了一个 Skill,开源了!!

56

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

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

有人把 App Store 和 Google Play 的 123 种拒审坑做成了一个 Skill,开源了!! GitHub 上刚冲到快 2,000 星 现在用 AI 写个 App 一下午就能出原型,但一提交商店就被打回,改完再排审核动不动耽误一周,是不是很劝退? 这个叫 app-store-compliance 的项目,支持 Claude Code、Codex、Cursor 等 10 多种编程工具,一条命令就能装上 在你真正点提交之前,它会先替你把项目过一遍: 1. 提审前自动拦住高危问题:用预审 Hook 扫你的代码和配置,像缺 PrivacyInfo.xcprivacy 隐私清单、有登录却没做 App 内删号入口,都会直接标出文件和行号 2. 专门盯着 2026 年的新规查:去年底开始,App 把用户数据发给外部 AI 却没弹授权弹窗,苹果会直接拒审,再加上 Google Play 新个人账号的 12 人封测要求,这些坑它全写进了检查项 3. 查完给改法,还能对上官方条款:库里收了 123 条拒审规则和 107 条全球合规截止日期,覆盖苹果、谷歌以及欧盟 AI 法案这些地区新规,每条都有出处,不是拍脑袋凑的 要是你已经被拒了,里面也带了申诉手册和审核备注模板,不想装插件的话,直接拿它写好的提示词让 AI 查一次也行 但有一点我觉得设计得很实在 很多审核项光看代码根本确认不了,比如后台填的审核备注和隐私表单,它不会把扫不到的地方直接判成通过,而是直接弹出来提醒你手动核对,宁可多拦一下也不漏掉真坑 有个 Reddit 开发者只跑了免安装的那次检查,按提示把漏掉的地方补完,App 一次就过审了(见图 2) 值得注意的是,它用的是 OpenRoots 协议,个人开发者和年营收 2000 万美元以下的团队都能免费拿去商用,最近准备上架 iOS 或安卓 App 的,提交前可以先跑一遍 项目地址: https://github.com/mjmirza/app-store-compliance

6

Opus 5.5 vs Gemini 4 Neon for Shibuya Crossing at night. Which one do you prefer?

56

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

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

Opus 5.5 vs Gemini 4 Neon for Shibuya Crossing at night. Which one do you prefer? 📌 Watch my 4 other head to head comparisons here: https://youtu.be/iYIWuI5WfUo Media

7

Firecrawl Local ?

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

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

Firecrawl Local ? 本地轻量版 Firecrawl,直接在你电脑上抓网页转 Markdown、起本地 v2 API 服务,还能一键接进 Claude Code、Cursor 等 AI 客户端。 https://docs.firecrawl.dev/quickstarts/firecrawl-local

8

Token fraud is here and it’s BAD (YouTube)

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.youtube.com/watch?v=ZDpP7JXPlhc">Token fraud is here and it’s BAD (YouTube)</a></strong></p> Claire Vo runs <a href="https://www.chatprd.ai">ChatPRD</a>, an AI platform that helps product managers "turn an idea into a spec". The product has been live since the GPT-4 era, and Claire has been building it in public for much of that time.</p> <p>In this YouTube video (see also the <a href="https://x.com/clairevo/status/2119985786045227197">accompanying Twitter post</a>) Claire describes the <em>flood</em> of token fraud she has seen from groups abusing the product's free trial, sometimes just to get free AI usage but often to resell tokens or run other commercial enterprises on top of the ChatPRD agent.</p> <blockquote> <p>I am funding a international Roblox and Fortnite map studio. They run a loop of free trials and promo codes and then tunnel to my agent and use it to build Roblox and Fortnite maps.</p> </blockquote> <p>Apparently one of the common prompts Claire saw running through her agent involved SVGs of pelicans riding bicycles! Presumably the token scammers are using that to help sniff the underlying models - different model families have a definite signature, and I've used it like this in the past to try and guess the identity of stealth preview models on platforms like OpenRouter.</p> <p>Claire is winding down her free trials entirely, which sadly looks like the right decision in the face of this abuse. <p>Tags: <a href="https://simonwillison.net/tags/youtube">youtube</a>, <a href="https://simonwillison.net/tags/ai">ai</a>, <a href="https://simonwillison.net/tags/generative-ai">generative-ai</a>, <a href="https://simonwillison.net/tags/llms">llms</a>, <a href="https://simonwillison.net/tags/pelican-riding-a-bicycle">pelican-riding-a-bicycle</a>, <a href="https://simonwillison.net/tags/ai-misuse">ai-misuse</a></p>

10

Apple just released Depth Pro 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

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

Apple just released Depth Pro 2 Sharp and Temporally Consistent Metric Monocular Depth HF: https://huggingface.co/apple/DepthPro2 Media

11

Fly through GPT-6.2 Astra's scenes yourself in the AA-3D Explorer:

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

Fly through GPT-6.2 Astra's scenes yourself in the AA-3D Explorer: ➤ Sydney Opera House: https://artificialanalysis.ai/3d/explorer?task=sydney-opera-house&model=gpt-6-2-astra ➤ Mechanical watch: https://artificialanalysis.ai/3d/explorer?task=watch-complications&model=gpt-6-2-astra ➤ Dragon attack: https://artificialanalysis.ai/3d/explorer?task=dragon-over-medieval-town&model=gpt-6-2-astra

12

Or vote in our arenas:

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

Or vote in our arenas: ➤ AA-3D Arena: https://artificialanalysis.ai/3d/vote ➤ Video Arena: https://artificialanalysis.ai/video/arena

13

Can language models make better videos than video 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

Can language models make better videos than video models? LLMs now make motion graphics, edit video as code and drive Blender to build 3D scenes. Can LLMs compete with video generation models? We put GPT-6.2 Astra from @OpenAI, the current #1 on AA-3D, to the test, building the Sydney Opera House, an exploded mechanical watch, and a dragon attacking a medieval town as three.js code. We flew a scripted camera through each scene in a browser: 15 s, 1080p, 24 fps. Dreamina Seedance 2.5 from @ByteDanceSeed_ got the same camera path as a text prompt with reference images of the route, at the same settings. ➤ Top: GPT-6.2 Astra (LLM, AA-3D) ➤ Bottom: Dreamina Seedance 2.5 (video model, AA-Video-T2V) Media

14

Amazon SageMaker Inference: 2026 launches in review, part 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

Aryaman Kothari 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>Once a model is in production, the questions change. Teams want to know which configuration the model should run on now that traffic is real, how to fit more models onto GPUs they already pay for, what to do when the next model is too large for one machine, why requests wait in one Region while GPUs sit idle in another, and why latency rose when nobody changed anything. This post takes those questions in the order teams usually meet them.</p> <p>For HyperPod Inference, it listed additional routing strategies, broader support for model serving frameworks, and expanded multi-Region networking. The Inference Gateway delivers the routing, and managed NVIDIA Dynamo is a new serving framework. For managed endpoints, the roadmap pointed to deeper integration with the rest of the AWS AI landscape. Inference recommendations now run from Amazon SageMaker AI Studio, the SageMaker Python SDK, and the coding agents engineers already use, and endpoints can now route requests across Regions and accounts.</p> <p>To keep each section concrete, we follow one hypothetical team through the blog post. In the spring, they launched a customer support assistant on a 70B-parameter model behind a single SageMaker AI endpoint, using the launches from part 1. By the fall, they need to support more product lines, adopt a larger reasoning model, serve customers in a second Region, and keep their GPU bill flat.</p> <h2 id="the-launches-at-a-glance">The launches at a glance</h2> <div style="width: 810px" class="wp-caption alignnone"> <a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/19/ML-22497-1.png" target="_blank" rel="noopener"><img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/19/ML-22497-1.png" alt="Five inference stages in this post and the launches grouped under each" width="800"></a> <p class="wp-caption-text">Figure 1: The five stages in this post and the launches in each</p> </div> <h2 id="choose-the-right-configuration-from-wherever-you-work">Choose the right configuration from wherever you work</h2> <p>The team picked its first configuration from a benchmark run in April. Since then, they have added four LoRA (Low-Rank Adaptation) adapters, one for each product line, and the product team has set a target of 500 milliseconds for time to first token (TTFT) at peak load. The April configuration was never tested against either change. The engineers who will re-run the analysis work in notebooks and coding agents, and few of them use the console.</p> <p>Inference recommendations launched in April as an API. Four updates since then make it available in more of the places teams work, and let it answer two harder questions: how many adapters an endpoint can carry, and how much concurrency it can take before it misses a latency target. A new agent skill brings the same expertise into coding agents.</p> <h3 id="inference-recommendations-in-sagemaker-ai-studio-july-2026">Inference recommendations in SageMaker AI Studio (July 2026)</h3> <p><em>Blog:</em> <a href="https://aws.amazon.com/blogs/machine-learning/launching-ui-for-generative-ai-inference-recommendations-in-amazon-sagemaker-ai/" target="_blank" rel="noopener">Launching UI for generative AI inference recommendations in Amazon SageMaker AI</a></p> <p>The April launch automated instance, container, and optimization selection through APIs. Inference recommendations are now also available in SageMaker AI Studio as a guided, low-code workflow. In Studio, choose <strong>Jobs</strong>, then <strong>Inference optimization</strong>. Choose a use-case profile (Interact, Generate, Summarize, or Custom), an optimization goal (minimize latency, maximize throughput, or minimize cost), and a model from SageMaker JumpStart, Amazon Simple Storage Service (Amazon S3), the Model Registry, or an existing SageMaker model.</p> <p>SageMaker AI benchmarks candidate configurations on real GPU infrastructure using NVIDIA AIPerf and applies techniques that match the goal, such as speculative decoding for throughput or kernel tuning for latency. You compare the ranked results by TTFT, inter-token latency, throughput, and cost, and then deploy the chosen configuration to a real-time endpoint from Studio.</p> <h3 id="inference-recommendations-in-the-sagemaker-python-sdk-v3-august-2026">Inference recommendations in the SageMaker Python SDK v3 (August 2026)</h3> <p><em>Blog: <a href="https://aws.amazon.com/blogs/machine-learning/llm-optimization-integration-for-amazon-sagemaker-python-sdk/" target="_blank" rel="noopener">LLM optimization integration for Amazon SageMaker Python SDK</a></em></p> <p>Benchmarking and recommendations previously required SageMaker AI Studio or direct Boto3 calls. They are now part of the SageMaker Python SDK v3 (version 3.17.0 and later), the same interface teams use for training and deployment, so the workflow fits into notebooks, CI pipelines, and MLOps workflows. You can benchmark a live endpoint against your workload traffic, generate ranked recommendations for a latency, throughput, or cost goal, and deploy the top-ranked configuration to a real-time endpoint in a single call.</p> <p>The SDK also supports longer workflows. You can run recommendation jobs in parallel to compare serving frameworks such as LMI and vLLM, and you can resume from a completed job so that deployment happens in a different notebook or pipeline stage without re-running the benchmarks.</p> <h3 id="lora-adapter-support-in-inference-recommendations-september-2026">LoRA adapter support in inference recommendations (September 2026)</h3> <p><em>Developer guide</em>: <a href="https://docs.aws.amazon.com/sagemaker/latest/dg/generative-ai-inference-recommendations-adapters.html" target="_blank" rel="noopener">Get recommendations for models with LoRA adapters</a></p> <p>Many teams use LoRA adapters to specialize one foundation model for several use cases. Each adapter kept in GPU memory reduces the nu

15

Use Kimi Code CLI with models on Amazon Bedrock

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

Alex Thewsey 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p><a href="https://github.com/moonshotai/kimi-code" target="_blank" rel="noopener">Kimi Code CLI</a> is an open source coding agent from Moonshot AI, the creator of the Kimi series of open-weight foundation models. Previously, using Kimi Code with models on <a href="https://aws.amazon.com/bedrock/" target="_blank" rel="noopener">Amazon Bedrock</a> meant configuring a generic connection “provider” with an Amazon Bedrock API key. For many AWS customers, this meant introducing an extra credential to obtain and protect.</p> <p>With v2.7.0, Moonshot AI adds a native bedrock provider to the CLI. You can now configure the agent to use your standard AWS credential chain, including named profiles and single sign-on (SSO), instead of creating and managing a separate API key.</p> <p>In this post, we show you how to connect Kimi Code CLI to models on Amazon Bedrock using your existing AWS credentials. We use <a href="https://aws.amazon.com/blogs/machine-learning/introducing-kimi-k3-1-pro-on-amazon-bedrock/" target="_blank" rel="noopener">Kimi K3.1 Pro Highspeed</a> as an example, which supports streaming, configurable reasoning, image input, and client-side tool calling.</p> <h2 id="whats-new">What’s new</h2> <p>Amazon Bedrock provides pay-per-token inference for a range of open and proprietary models from leading providers, available through <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/apis.html" target="_blank" rel="noopener">standard APIs</a>. Processing stays within the AWS data boundary, as detailed in the <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/data-protection.html" target="_blank" rel="noopener">Data protection</a> section of the User Guide. The <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/model-cards.html" target="_blank" rel="noopener">model cards</a> detail which APIs and features are supported for each model.</p> <p>In older versions of the Kimi Code CLI, you could connect to Amazon Bedrock through a provider with <code>type = "openai"</code> or <code>type = "openai_responses"</code>. These use the OpenAI-compatible <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/inference-chat-completions.html" target="_blank" rel="noopener">Chat Completions</a> or <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/inference-responses-api.html" target="_blank" rel="noopener">Responses</a> APIs, respectively. This approach required you to set the regional <code>base_url</code> and provide an <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys.html" target="_blank" rel="noopener">Amazon Bedrock API key</a>. The key could be short-term or long-term, but it was a separate credential for you to obtain and manage.</p> <p>The native provider changes that setup:</p> <ul> <li><strong>Use your existing AWS authentication workflow.</strong> The <code>bedrock</code> provider can resolve temporary credentials through the standard <a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener">AWS Command Line Interface (AWS CLI)</a> credential chain. You can use the default chain or select a named profile, including a profile backed by SSO.</li> <li><strong>Override the protocol for each model, if needed.</strong> The provider infers an API format and regional endpoint from the model ID, but you can change them as detailed in the “Override endpoint URL and protocol” section of this post.</li> </ul> <p>AWS recommends short-term credentials over long-term credentials. This new path reduces reliance on manually managed API keys, but it doesn’t change your responsibility to protect AWS credentials and scope permissions appropriately.</p> <h2 id="how-it-works">How it works</h2> <p>The native provider handles authentication and request routing in four steps:</p> <ol type="1"> <li><strong>Resolve AWS credentials.</strong> Unless you configure an Amazon Bedrock API key, the bedrock provider uses the standard AWS credential chain in your environment. You can set <code>AWS_PROFILE</code> to select a specific <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html#cli-configure-files-using-profiles" target="_blank" rel="noopener">named profile</a>.</li> <li><strong>Generate a short-lived bearer token.</strong> The provider uses <a href="https://www.npmjs.com/package/@aws/bedrock-token-generator" target="_blank" rel="noopener"><span class="citation" data-cites="aws/bedrock-token-generator">@aws/bedrock-token-generator</span></a> to create a short-term Amazon Bedrock API key, and renews it when necessary. You don’t need to place any AWS access key or manually generated Amazon Bedrock key in the Kimi Code <code>config.toml</code>. However, an explicit key given through <code>api_key</code> or <code>api_key_env</code> takes precedence if you provide it.</li> <li><strong>Build the regional endpoint.</strong> The provider resolves <code>AWS_REGION</code> or <code>AWS_DEFAULT_REGION</code> and constructs the appropriate <code>bedrock-runtime</code> endpoint for the model’s inferred API. For Kimi models, this resolves to the recommended OpenAI-compatible Chat Completions path.</li> <li><strong>Call the selected inference profile.</strong> The model alias maps to an Amazon Bedrock model or <a href="https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles.html" target="_blank" rel="noopener">inference profile</a> ID. This example uses the global inference profile <code>global.moonshotai.kimi-k3.1</code>. The <code>global.</code> prefix selects the profile, while <code>AWS_REGION</code> determines the regional endpoint that receives your request.</li> </ol> <p>The CLI then streams the model response and can use the model’s client-side tool-calling support during coding tasks. Authentication, authorization, model access, and network connectivity must all succeed for a request to complete. The ephemeral API keys generated by the provider are valid for up to 12 hours or your AWS session length, w

16

See the diarization results on our speech to text leaderboard: https://artificialanalysis.ai/speech-to-text/non-streaming#diarization

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

See the diarization results on our speech to text leaderboard: https://artificialanalysis.ai/speech-to-text/non-streaming#diarization Methodology: https://artificialanalysis.ai/methodology/speech-to-text#diarization-evaluation

18

v0.40.17

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

github-actions[bot] 1 bài viết · ollama/ollama releases
Nguyên văn nguồn
Chi tiết nguồn

<h2>What's Changed</h2> <ul> <li>Improve ChatGPT CLI restore and graceful restart by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/hoyyeva/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/hoyyeva">@hoyyeva</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6251854019" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19583" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19583/hovercard" href="https://github.com/ollama/ollama/pull/19583">#19583</a></li> <li>cmd/launch: use thinking metadata for OpenCode settings by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/hoyyeva/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/hoyyeva">@hoyyeva</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6122368894" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19409" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19409/hovercard" href="https://github.com/ollama/ollama/pull/19409">#19409</a></li> <li>llm: use mmap for Vulkan integrated GPUs by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6309814784" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19640" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19640/hovercard" href="https://github.com/ollama/ollama/pull/19640">#19640</a></li> <li>rpreslar4765/Ollama by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/rpreslar4765/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/rpreslar4765">@rpreslar4765</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4877598143" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/17163" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/17163/hovercard" href="https://github.com/ollama/ollama/pull/17163">#17163</a></li> <li>mlx: support concurrent generation by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5970886020" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19197" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19197/hovercard" href="https://github.com/ollama/ollama/pull/19197">#19197</a></li> <li>llama.cpp: version bump b12257 by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6315369343" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19646" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19646/hovercard" href="https://github.com/ollama/ollama/pull/19646">#19646</a></li> <li>MLX, MLX-C: version bump by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dhiltgen/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dhiltgen">@dhiltgen</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6316056226" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/19647" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/19647/hovercard" href="https://github.com/ollama/ollama/pull/19647">#19647</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/rpreslar4765/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/rpreslar4765">@rpreslar4765</a> made their first contribution in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4877598143" data-permission-text="Title is private" data-url="https://github.com/ollama/ollama/issues/17163" data-hovercard-type="pull_request" data-hovercard-url="/ollama/ollama/pull/17163/hovercard" href="https://github.com/ollama/ollama/pull/17163">#17163</a></li> </ul> <p><strong>Full Changelog</strong>: <a class="commit-link" href="https://github.com/ollama/ollama/compare/v0.40.16...v0.40.17-rc0"><tt>v0.40.16...v0.40.17-rc0</tt></a></p>

  • v0.40.17 ollama/ollama releases · 20 thg 11, 2026
20

we're celebrating this fundraise with a ton of product launches next week, and then a webinar on friday to wrap it all up

63

2 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

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

we're celebrating this fundraise with a ton of product launches next week, and then a webinar on friday to wrap it all up come join us! https://events.langchain.com/webinar/future-of-agents/#Registration

1–20 / 175
Trang 1 / 9