AllyshipContent Radar

News 2859

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

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

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

21

b12543

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 · ggml-org/llama.cpp releases
Nguyên văn nguồn
Chi tiết nguồn

<details open=""> <p>metal : CONV_2D tensor API for M5, split-K for all chips (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6468918084" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/32542" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/32542/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/32542">#32542</a>)</p> <ul> <li>metal: add a tensor API conv_2d kernel and split long reductions</li> </ul> <p>The conv_2d matmul kernel runs on simdgroup matrices only, and gives<br> each threadgroup the whole reduction of its output tile. On M5 this<br> leaves the tensor cores unused, and convolutions with few output<br> positions and a long reduction (IC * KW * KH in the thousands) run a<br> handful of threadgroups on an otherwise idle GPU.</p> <p>Add kernel_conv_2d_mm_tensor for devices with the tensor API: like<br> kernel_mul_mm, it gathers the patches of 64 output positions into<br> threadgroup memory as the left operand and reads the kernel rows<br> from device memory as the right operand. Devices without the tensor<br> API keep the simdgroup kernel.</p> <p>Both kernels can now split the reduction until there are enough<br> threadgroups: each split writes its partial sums to a buffer placed<br> after the output, as flash attention does, and a small kernel adds<br> them in a fixed order, so the result stays deterministic. CONV_2D is<br> marked as an op whose allocation may exceed its output size.</p> <p>test-backend-ops -o CONV_2D passes, with and without<br> GGML_METAL_TENSOR_DISABLE.</p> <p>CONV_2D, F16 kernel, us/run on an M5 Max:<br> [19,19,256,16] k [4,4,256,4096] 19008 -&gt; 5235<br> [16,16,128,8] k [3,3,128,512] 333 -&gt; 124<br> [1536,1536,32,1] k [3,3,32,64] 12086 -&gt; 6512<br> [33,1,1280,1] k [3,1,1280,1280] s2 659 -&gt; 33<br> [2054,1,768,1] k [7,1,768,768] 3161 -&gt; 699</p> <ul> <li>metal: walk the conv_2d patches incrementally, size splits by output</li> </ul> <p>The patch gather of both conv_2d matmul kernels spent most of its<br> time on address math: 64-bit multiplies, divisions and four bound<br> checks per value. Walk the reduction index with 32-bit byte offsets<br> inside the image, updated by additions, with one unsigned compare per<br> bound; the host checks that an image fits. The tensor kernel no<br> longer gathers the reduction indices past the end of its split.</p> <p>The number of splits now targets about 1M partial sums, with at least<br> 3 reduction steps per split, instead of counting the tiles of one<br> kernel.</p> <p>CONV_2D, F16 kernel, us/run on an M5 Max:<br> [19,19,256,16] k [4,4,256,4096] 4998 -&gt; 4512<br> [1536,1536,32,1] k [3,3,32,64] 6721 -&gt; 5354<br> [4096,1,1024,1] k [7,1,1024,1024] 2701 -&gt; 2236<br> [2054,1,768,1] k [7,1,768,768] 1050 -&gt; 871<br> with GGML_METAL_TENSOR_DISABLE:<br> [4096,1,1024,1] k [7,1,1024,1024] 9047 -&gt; 8283</p> <ul> <li>nit: share the CONV_2D simdgroup count between host and kernel</li> </ul> <p>kernel_conv_2d_mm and its pipeline both hardcoded 4 simdgroups per<br> threadgroup. N_SG_CONV_2D in ggml-metal-impl.h now feeds the kernel<br> constant and res.nsg, so the dispatch and the kernel cannot drift apart.</p> <ul> <li>metal: fall back to the generic conv_2d kernel for images past 4 GiB</li> </ul> <p>The matmul conv_2d kernels walk the patches with 32-bit byte offsets<br> inside an image. Instead of asserting on nb13, compute the largest<br> offset actually read from ne/nb, which also covers strided views of<br> the input, and route images that do not fit to the generic kernel.</p> <ul> <li>cont : comments</li> </ul> <p>Co-authored-by: Georgi Gerganov <a href="mailto:ggerganov@gmail.com">ggerganov@gmail.com</a></p> <hr> <p>Co-authored-by: Georgi Gerganov <a href="mailto:ggerganov@gmail.com">ggerganov@gmail.com</a></p> </details> <p><strong>Website:</strong></p> <ul> <li><a href="https://llama.app" rel="nofollow">https://llama.app</a></li> </ul> <p><strong>Attestations:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/attestations/69742362">https://github.com/ggml-org/llama.cpp/attestations/69742362</a></li> </ul> <p><strong>macOS/iOS:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-macos-arm64.tar.gz">macOS Apple Silicon (arm64)</a></li> <li>macOS Apple Silicon (arm64, KleidiAI enabled) <a href="https://github.com/ggml-org/llama.cpp/pull/23780" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/23780/hovercard">DISABLED</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-macos-x64.tar.gz">macOS Intel (x64)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-xcframework.zip">iOS XCFramework</a></li> </ul> <p><strong>Linux:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-ubuntu-x64.tar.gz">Ubuntu x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-ubuntu-arm64.tar.gz">Ubuntu arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-ubuntu-s390x.tar.gz">Ubuntu 24.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-ubuntu-26.04-s390x.tar.gz">Ubuntu 26.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-ubuntu-zdnn-s390x.tar.gz">Ubuntu 26.04 s390x (zDNN)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-ubuntu-vulkan-x64.tar.gz">Ubuntu x64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12543/llama-b12543-bin-ubuntu-vulkan-arm64.tar.gz">Ubuntu arm64 (Vulkan)</a></li> <li><a href="https://github.com

  • b12543 ggml-org/llama.cpp releases · 19 thg 11, 2026
22

Launch HN: Onlook (YC W25) – An open-source developer tool for designers

68

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

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

Hey HN, I'm Daniel, founder of Onlook ( https://github.com/onlook-dev/onlook and onlook.com). Onlook is a desktop app that puts a canvas on top of your real codebase, letting you design directly in code with the agent you already use. Over 25,000 designers and developers have supported the project, 100+ have contributed, and it's been the #1 trending repo in the world twice. We just rebuilt the entire product as an agentic design tool, and open-sourced it to the community. Here’s a demo video: ( https://youtu.be/BogcYWf4siM ) If you're an engineer, traditional engineering tools are largely built for convergence, whereas designers tend to explore and diverge on ideas. Onlook gives designers a familiar canvas while managing all of the dev processes that get between them and making mind-blowing designs in code. Designers can work on a multiple simultaneous worktrees that run on the real app locally, and every change lands as a PR you can review or throw away, so there aren’t mockups to rebuild. We built Onlook because we believe there needs to be a developer tool that works the way designers do. More and more, designers are expected to work in code. Designers think by seeing, drafting, arranging variations, using references, and remixing ideas. That’s why the canvas has been the signature feature of design tools because it genuinely is useful for how messy the creative process is. Most of the challenge of using engineering tools for design work is that the first half of starting a project often takes mental bandwidth in of itself (What branch am I on? What page was that last exploration on?) and the second half is constrained by configuring your coded design to present itself (prompting design tools on top of what you’ve built or making temporary navigation for that specific state). Some of you may remember our earlier Show HNs (July 2024: https://news.ycombinator.com/item?id=40904862 , August 2024: https://news.ycombinator.com/item?id=41390449 , May 2025: https://news.ycombinator.com/item?id=44127653 ). Since then, we built a web version (too early), then a Storybook-native build (a mistake). We noticed that our desktop product from July 2024 was still getting hundreds of downloads a month despite zero promotion, so we decided to rebuild it for the new era of designers working in code. How it works… Onlook shines at exploring tons of ideas at once. Ask it to lay out every flow in your product, show every state of a component, or riff on ten versions of one screen. Your designs all show up side by side on an infinite canvas, with each frame as a real webview running your actual app with real data. Not as a mockup, but the real deal. When we built this editor, we had an epiphany that it could be a new kind of IDE for design. Design tools used to be limited to a proprietary setup or closed schema, but now you can push and pull the medium of code to get whatever result you want, so why not give agents an infinite canvas of browsers and see what they do? It turns out, the agents can figure out how to better present coded work by adjusting the urls of browser frames and arranging and resizing them on the canvas. The concept is simple, but it requires a lot of product thinking. For example, because all of the frames on the canvas share a single browser session, and Chromium only allows six connections per host per session, ten frames of the same app end up fighting over limited connections. So, we had to plan around that, and there are still tons of things we need to do to make the canvas ultra performant. Onlook is an Electron app where you can import a repo from GitHub or upload a local folder. Then, Onlook creates a git worktree, starts your dev server, and has the agent sort out missing dependencies or other requirements. You never open a terminal and everything the agent does is a normal git diff that can go to GitHub as a PR. We inject a small script into each frame that draws selection outlines and reads the page, so that way you can click an element, say "make this a card layout," and the agent knows exactly what "this" is. This time we didn't build our own agent. Onlook runs Claude Code or Codex on your own subscription, and we turn whatever the agent emits into one typed event log and draw the UI from that in our own chat interface. On top of that we give the agent a bespoke set of design-specific tools, from arranging frames on the canvas, to making suggestions, to generating multiple iterations of a selection – which is especially useful because the agent decides how to get the app into a state that you need based on your prompt. We also have our own Artifacts which are quick HTML sketches that live in the editor, but outside your repo. They’re almost like components in other design tools in that they can be carried and edited across every project but are detached from the project with no network access. As an example, you can ask the agent to turn your interface into an Artifact, and use it as a reference for another exploration, or download it as HTML and send it to a coworker as an interactive export of something you have in progress. I frequently go back to the artifacts I’ve made as visual snippets when I need new ideas or need to borrow something that’s already been built. The desktop editor is free (you can download it from our website at onlook.com) and open source under Apache-2.0, and we'll eventually offer a paid cloud product for teams. We'd love to hear which repos work and which don't, what you try to do on the canvas, and what's missing. We’re so excited for this to be a new way for designers to work in code! The Onlook team (Joel - thebrubaker and Kris - krisodd), and I will be here all day!

23

Build Tool-Calling Parsers in Rust with AI Agents

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

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

A tool call can arrive in pieces, an argument can be cut short, or model-specific markup can leak into the answer. A frontend parser turns that output, received... A tool call can arrive in pieces, an argument can be cut short, or model-specific markup can leak into the answer. A frontend parser turns that output, received as token IDs or decoded text, into visible text, reasoning, and tool calls an application can use. In this post, you’ll learn how tool-call parsing works and use an AI agent to build a parser for a new model. You’ll start with a… Source

24

From Static to Current

61

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

whakim 1 bài viết · HN: GPT
Nguyên văn nguồn
Chi tiết nguồn
26

Using NVIDIA Run:ai GPU Fractioning on Amazon EKS

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

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

<p>GPU sharing is not new: Multi-Instance GPU (MIG), time-slicing, and Multi-Process Service (MPS) address different isolation and utilization needs. NVIDIA Run:ai GPU Fractioning builds on MPS with Kubernetes-integrated scheduling, per-Pod memory contracts, enforcement, and metrics.</p> <p><a href="https://github.com/dsx-ai-factory/run-ai" target="_blank" rel="noopener">NVIDIA Run:ai</a> is AI workload orchestration software for Kubernetes. Its GPU Fractioning Operator can help several teams share one or two GPUs on <a href="https://aws.amazon.com/eks/" target="_blank" rel="noopener">Amazon Elastic Kubernetes Service (Amazon EKS)</a>. Notebooks, model evaluations, and small inference services can leave teams waiting even when GPU memory remains available. In this walkthrough’s baseline, the NVIDIA device plugin exposes the single GPU as one <code>nvidia.com/gpu</code> resource, with GPU sharing disabled. Two Pods each requesting <code>nvidia.com/gpu: 1</code> cannot run concurrently on that node, even when their combined GPU-memory demand fits.</p> <p><a href="https://github.com/kai-scheduler/gpu-fractioning/" target="_blank" rel="noopener">NVIDIA Run:ai GPU Fractioning</a> adds Kubernetes scheduling integration, enforced GPU-memory limits, and per-Pod metrics to software-based sharing. The approach applies to NVIDIA GPUs that meet the GPU Fractioning Operator’s hardware and software requirements, including GPUs without MIG. We use one <a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener">Amazon Elastic Compute Cloud (Amazon EC2)</a> g5.xlarge instance with an NVIDIA A10G Tensor Core GPU as the validated example. Other configurations require compatibility checks and validation.</p> <p>NVIDIA <a href="https://developer.nvidia.com/blog/nvidia-runai-is-now-open-source-as-part-of-nvidia-dsx-ai-factory-platform/" target="_blank" rel="noopener">announced</a> the <a href="https://github.com/dsx-ai-factory/run-ai" target="_blank" rel="noopener">open source release of NVIDIA Run:ai</a> on October 13, 2026. This example uses two of its four modular components: <a href="https://github.com/kai-scheduler/KAI-Scheduler" target="_blank" rel="noopener">KAI Scheduler</a> and <a href="https://github.com/kai-scheduler/gpu-fractioning/" target="_blank" rel="noopener">GPU Fractioning Operator</a>. KAI Resource Management and Workload Map address organizational governance and additional workload types, outside this walkthrough’s scope.</p> <p>In this post, we show how to build a custom <a href="https://aws.amazon.com/linux/amazon-linux-2023/" target="_blank" rel="noopener">Amazon Linux 2023 (AL2023)</a> image and configure GPU-memory sharing on Amazon EKS. In the validated G5/A10G example, you establish a whole-GPU baseline, give each Pod an 8 GiB memory contract, and verify 6 GiB allocations. You then inspect per-Pod metrics, test rejection of a 9 GiB allocation, and clean up the disposable environment.</p> <h2 id="choose-a-gpu-sharing-approach">Choose a GPU sharing approach</h2> <p>MIG provides hardware partitions on <a href="https://docs.nvidia.com/datacenter/tesla/mig-user-guide/supported-gpus.html" target="_blank" rel="noopener">supported GPUs</a>. <a href="https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/gpu-sharing.html" target="_blank" rel="noopener">Device-plugin time-slicing</a> shares a GPU without replica memory or fault isolation. MPS permits concurrent CUDA processes. Fault containment depends on configuration. NVIDIA Run:ai GPU Fractioning adds enforced per-container memory limits and supports time-slicing (default) or sm-sharing compute modes. <a href="https://developer.nvidia.com/blog/memory-enforced-gpu-sharing-in-kubernetes-with-nvidia-cuda-13-4/" target="_blank" rel="noopener">NVIDIA documents</a> separate workload error domains for its default mode and a shared error domain for sm-sharing. These are not security guarantees. This walkthrough tests memory limits, not fault containment or compute performance. A memory limit does not reserve proportional compute.</p> <p>Amazon EKS documents several GPU sharing options: <a href="https://docs.aws.amazon.com/eks/latest/userguide/device-management-nvidia-mig.html" target="_blank" rel="noopener">MIG</a>, time-slicing with the <a href="https://docs.aws.amazon.com/eks/latest/userguide/device-management-nvidia-time-slicing.html#eks-time-slicing-device-plugin-al2023" target="_blank" rel="noopener">NVIDIA device plugin</a>, and time-slicing with the <a href="https://docs.aws.amazon.com/eks/latest/userguide/device-management-nvidia-time-slicing.html#eks-time-slicing-karpenter-consumable-capacity" target="_blank" rel="noopener">NVIDIA DRA driver and Karpenter</a>. For guidance on choosing among them, see the <a href="https://docs.aws.amazon.com/eks/latest/best-practices/aiml-compute.html#_optimize_gpu_resource_allocation_with_time_slicing_mig_and_fractional_gpu_allocation" target="_blank" rel="noopener">GPU sharing guidance</a> in the Amazon EKS Best Practices Guide. Choose GPU fractioning when you need enforced per-Pod GPU-memory limits on GPUs without MIG and can run fixed-size GPU node groups.</p> <p><a href="https://docs.aws.amazon.com/eks/latest/userguide/device-management.html" target="_blank" rel="noopener">Dynamic Resource Allocation (DRA)</a> provides Kubernetes APIs for requesting and allocating devices. GPU sharing and isolation depend on the device driver’s implementation and enabled features. KAI Scheduler and GPU Operator support DRA. This walkthrough uses NvFractions annotations, not DRA.</p> <p>GPU fractioning can help interactive notebooks with idle periods, short evaluation jobs, GPU compatibility tests, and small inference services. Choose each GPU-memory request from measured peak usage plus overhead, then test latency under concurrent load. The demonstrated density improvement does not establish a throughput gain or a universal cost reduction.</p> <h2 id="solution-overview">Solution overview</h2> <p

27

Every dependency is a potential vulnerability, so in Gradio 7, we'll be cutting our dependencies in half!

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

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

Every dependency is a potential vulnerability, so in Gradio 7, we'll be cutting our dependencies in half! Media

28

Cloudflare just dropped Clairic on @huggingface ☁️✏️🧾

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

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

Cloudflare just dropped Clairic on @huggingface ☁️✏️🧾 Clairic goes beyond decision models: it actually extracts information on a single forward pass, unlocking ultra fast system one decision-making process ▶️ https://huggingface.co/spaces/hugging-apps/clairic Media

29

Recently I've been enjoying this mp4 player plugin made by an Orca user.

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

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

Recently I've been enjoying this mp4 player plugin made by an Orca user. It has speed control & video info overlay. Just better than our bare-bones default mp4 player. Huge shoutout to Sergei Popov (too bad he's not on X 😆) for shipping this: https://orca.dev/plugins/sergei-popov/orca-media-viewer Media

30

GitHub 榜单直链 | https://github.com/trungdq88/Awesome-Black-Friday-Cyber-Monday | https://github.com/danmindru/rare-big-deal | https://github.com/mRs-/Black-Friday-Deals | https://github.com/onmyway133/b

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

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

GitHub 榜单直链 | https://github.com/trungdq88/Awesome-Black-Friday-Cyber-Monday | https://github.com/danmindru/rare-big-deal | https://github.com/mRs-/Black-Friday-Deals | https://github.com/onmyway133/blackfriday

31

SEO 和创作者工具投稿直链 | Alston Antony https://alstonantony.com/submit-seo-black-friday-deal/ | Creator Black Friday https://airtable.com/appBm2rfgJ4q6CgSZ/shrUnrvak1VKp9wNY | SaaS AI Tools(登录) https://saasai

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

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

SEO 和创作者工具投稿直链 | Alston Antony https://alstonantony.com/submit-seo-black-friday-deal/ | Creator Black Friday https://airtable.com/appBm2rfgJ4q6CgSZ/shrUnrvak1VKp9wNY | SaaS AI Tools(登录) https://saasaitools.com/blackfriday/submit/ | BlackFriday Tools(登录) https://blackfriday.tools/submissions

32

b12542

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 · ggml-org/llama.cpp releases
Nguyên văn nguồn
Chi tiết nguồn

<details open=""> <p>qwen3vl : set t_layer_inp for EAGLE-3 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6484930342" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/32589" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/32589/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/32589">#32589</a>)</p> <p>Assisted-by: Grok Bot</p> </details> <p><strong>Website:</strong></p> <ul> <li><a href="https://llama.app" rel="nofollow">https://llama.app</a></li> </ul> <p><strong>Attestations:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/attestations/69725014">https://github.com/ggml-org/llama.cpp/attestations/69725014</a></li> </ul> <p><strong>macOS/iOS:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-macos-arm64.tar.gz">macOS Apple Silicon (arm64)</a></li> <li>macOS Apple Silicon (arm64, KleidiAI enabled) <a href="https://github.com/ggml-org/llama.cpp/pull/23780" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/23780/hovercard">DISABLED</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-macos-x64.tar.gz">macOS Intel (x64)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-xcframework.zip">iOS XCFramework</a></li> </ul> <p><strong>Linux:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-x64.tar.gz">Ubuntu x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-arm64.tar.gz">Ubuntu arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-s390x.tar.gz">Ubuntu 24.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-26.04-s390x.tar.gz">Ubuntu 26.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-zdnn-s390x.tar.gz">Ubuntu 26.04 s390x (zDNN)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-vulkan-x64.tar.gz">Ubuntu x64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-vulkan-arm64.tar.gz">Ubuntu arm64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-cuda-12.8-x64.tar.gz">Ubuntu x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/cudart-llama-b12542-bin-ubuntu-cuda-12.8-x64.tar.gz">CUDA 12.8 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-cuda-13.5-x64.tar.gz">Ubuntu x64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/cudart-llama-b12542-bin-ubuntu-cuda-13.5-x64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-cuda-13.5-arm64.tar.gz">Ubuntu arm64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/cudart-llama-b12542-bin-ubuntu-cuda-13.5-arm64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-rocm-10.0-x64.tar.gz">Ubuntu x64 (ROCm 10.0)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-openvino-2026.4.1-x64.tar.gz">Ubuntu x64 (OpenVINO)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-sycl-fp32-x64.tar.gz">Ubuntu x64 (SYCL FP32)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-ubuntu-sycl-fp16-x64.tar.gz">Ubuntu x64 (SYCL FP16)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-linux-arm64-snapdragon.tar.gz">Linux arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/linux.md">setup guide</a></li> </ul> <p><strong>Android:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-android-arm64.tar.gz">Android arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-android-arm64-snapdragon.tar.gz">Android arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/README.md">setup guide</a></li> </ul> <p><strong>Windows:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-win-cpu-x64.zip">Windows x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-win-cpu-arm64.zip">Windows arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-win-opencl-adreno-arm64.zip">Windows arm64 (OpenCL Adreno)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-win-cuda-12.4-x64.zip">Windows x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/cudart-llama-bin-win-cuda-12.4-x64.zip">CUDA 12.4 DLLs</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-bin-win-cuda-13.5-x64.zip">Windows x64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/cudart-llama-bin-win-cuda-13.5-x64.zip">CUDA 13.5 DLLs</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12542/llama-b12542-b

  • b12542 ggml-org/llama.cpp releases · 19 thg 11, 2026
33

AI 工具投稿直链 | Black Friday AI Tools https://blackfridayai.tools/submit | AI Tools Bakery https://aitoolsbakery.com/ai-tools-black-friday-deals/submit/?type=free | AI Platforms List https://aiplatformsli

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

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

AI 工具投稿直链 | Black Friday AI Tools https://blackfridayai.tools/submit | AI Tools Bakery https://aitoolsbakery.com/ai-tools-black-friday-deals/submit/?type=free | AI Platforms List https://aiplatformslist.com/black-friday/add | AI Tools Directory https://aitoolsblackfriday.paperform.co/ | Voibe https://tally.so/r/jeb4BQ

34

补一版可直接点开的链接。通用 SaaS | DealHunt https://www.dealhunt.cc/submit-deal | SaaSPirate https://saaspirate.com/blackfriday-submit/ | BookWellNow https://bookwellnow.com/submit-your-deal/ | Superframeworks htt

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

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

补一版可直接点开的链接。通用 SaaS | DealHunt https://www.dealhunt.cc/submit-deal | SaaSPirate https://saaspirate.com/blackfriday-submit/ | BookWellNow https://bookwellnow.com/submit-your-deal/ | Superframeworks https://tally.so/r/OD1V5A | Black Friday 2026 https://blackfriday2026.io/deals/submit

35

Show HN: Dayfile.app – Append-only log for your scripts and agents

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

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

Hi HN, I'm Gilad. dayfile.app is a "git log for scripts and agents", with ordered history, append-only logging as foundational characteristics. The service is currently in beta, AGPL-licensed. As I was looking at various ways to record and retrieve a day's to-dos, automation and operational outputs (update successes and failures), the idea of a running event log. dayfile.app's primary use case is DevOps tracking and event logging. Building this, I've emphasized simplifying posting - one HTTP request with a title and optional tags (used for filtering when reading the log), AI access via MCP server (an assistant can read, post or close to-dos) and self-hosting as a first-class citizen (`pip install dayfile`, SQLite database is local in this mode). A demo is available at https://dayfile.app/demo . If using the cloud service and after generating a write token on the site, an example of posting an entry would be: curl -X POST https://USERNAME.dayfile.cloud/events \ -H "Authorization: Bearer WRITE_TOKEN" \ -H "content-type: application/json" \ -d '{"title":"Nightly backup finished","tags":["backup"]}' To read back (filtering using tag): curl -H "Authorization: Bearer READ_TOKEN" \ "https://USERNAME.dayfile.cloud/events?tag=backup&within=7d" or paste https://USERNAME.dayfile.cloud/t/READ_TOKEN/f/backup.atom into a feed reader (you need to create a feed called `backup`). What a local file can't do is notice something didn't happen - this is the heartbeat. dayfile.app can be configured to create an event if no associated event arrives. Imagine a backup which didn't run. A to-do event is created if no evidence of a successful backup shows up within a certain period. When the backup reports again, dayfile closes the associated to-do. Current limits: logs are not end-to-end encrypted, sign-in is via GitHub only, the free beta allows 50,000 events and log size of 25MB. Pricing will be sorted out after this launch and as user feedback rolls in. I'd love to hear in the comments on how you'd use it, what would prevent you from doing so, feature requests and suggestions. Bug reports can be submitted as issues on GitHub.

36

习惯用 GitHub 的,可以走 PR。先看各仓库的提交说明,有的改 README,有的单独加 YAML 或 JSON。下面这几个我都投过:https://github.com/trungdq88/Awesome-Black-Friday-Cyber-Mondayhttps://github.com/danmindru/rare-big-dealhttps://github.com/mRs-/Bl

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

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

习惯用 GitHub 的,可以走 PR。先看各仓库的提交说明,有的改 README,有的单独加 YAML 或 JSON。下面这几个我都投过:https://github.com/trungdq88/Awesome-Black-Friday-Cyber-Mondayhttps://github.com/danmindru/rare-big-dealhttps://github.com/mRs-/Black-Friday-Dealshttps://github.com/onmyway133/blackfriday

37

You can now follow model creators and API providers on Artificial Analysis

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

You can now follow model creators and API providers on Artificial Analysis Have a favorite creator or provider? Sign in with an Artificial Analysis account and click Follow to be the first to see scores whenever new measurements go live Media

38

Anthropic 这个敲钟的仪式

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

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

Anthropic 这个敲钟的仪式 看起来像是AI生成的🤣 全员透着一丝都不太像真人的感觉… Media

39

GitLab 19.6.0 is out and still vulnerable to Ruby2Shell and NGINX2Root

64

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

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

What's going on at GitLab? They released their usual monthly release 19.6.0 to their package repos (https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/jammy/pool/main/g/gitlab-ee/) but did not announce it at all as of 3.5h after release (https://docs.gitlab.com/releases/all-releases.xml, https://docs.gitlab.com/releases/19/gitlab-19-6-released/). But more annoyingly, this release does not address ruby2shell or nginx2root, nor do patches for their older releases exist yet and there's no communication on any of this (that I can find). root@gitlab:~# cat /opt/gitlab/embedded/service/gitlab-rails/VERSION 19.6.0-ee root@gitlab:~# /opt/gitlab/embedded/sbin/nginx -version nginx version: nginx/1.31.7 root@gitlab:~# /opt/gitlab/embedded/bin/ruby --version ruby 3.3.13 (2026-10-23 revision af48f08f21) [x86_64-linux] root@gitlab:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.5 LTS Release: 22.04 Codename: jammy Multiple MRs were created in their repos 14-15 hours ago, no urgency visible. Heres 2 I found: https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/10138 https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/10139

21–40 / 206
Trang 2 / 11