标签：#m

Computex 2026 is underway in Taiwan, and we're expecting all manner of flashy computers with jaw-dropping pricetags (or no pricetags at all) as the entire industry navigates RAMageddon. But for desktop PC gamers, AMD has a different pitch. It's relaunching three old components alongside a big new promise: you won't need to buy a new […]

Dell, Microsoft, and others are unveiling new laptops to compete directly with the Neo, but not all are learning the right lessons from Apple.

Dell is making good on its tease from CES and finally announcing a new XPS 13. The XPS 13 returns as a budget-friendly option, launching in July at a promotional student price of $599 - though that introductory deal only runs until September for back-to-school shopping; it'll start at $699 for everyone else. The $599 […]

Alienware is taking to this year's Computex 2026 in Taipei to announce some cool gaming monitors, most notably two exciting OLED options that are coming at different points this year. First off, the company is debuting the successor to its very first QD-OLED gaming monitor from 2022 with a refreshed design and high-end specs that's […]

You can’t see AC comments yet, but you can see the Accept/Reject consoles. My paper (with scores of 8,6,3) got rejected. submitted by /u/GeeseChen [link] [留言]

submitted by /u/wineandcode [link] [留言]

submitted by /u/Mushroom-Severe [link] [留言]

submitted by /u/fagnerbrack [link] [留言]

You've seen the developer. Maybe you are the developer. They discover DRY — ✨ Don't Repeat Yourself...

I do a fair amount of competitor backlink research, and the workflow always annoyed me: open a dashboard, run a query, export a CSV, eyeball it, copy domains into a doc, switch to email. Lots of tab-hopping for what is fundamentally a data-filtering problem an agent should handle. So I wrapped the backlink API I'd been using into an MCP server. Now I stay in Claude Code (or Cursor, Cline, Zed, Windsurf) and just describe the goal. This is the build: the architecture, the four tools, and the one design decision I'm still not sure about. The data source The server runs on the Common Crawl hyperlink webgraph — about 4.4 billion edges across 120 million domains, published quarterly as Parquet. That matters for an MCP tool specifically: the data is open, so there's no scraped-proprietary-index liability in handing it to an agent, and the same query is reproducible by anyone. The HTTP API in front of it ( CrawlGraph ) does the heavy DuckDB work; the MCP server is a thin TypeScript stdio client over it. Keeping the server thin was deliberate — all the query cost, caching, and quota logic lives server-side, so the MCP package stays a ~300-line wrapper that's easy to audit before you hand it your API key. The four tools backlinks → referring domains for a target, with authority scores gap_analysis → domains linking to your competitors but not to you gap_outreach_targets → the composite play (below) releases → list the Common Crawl snapshots backlinks and gap_analysis map 1:1 to API endpoints. gap_analysis is the interesting primitive: submit your domain plus 2-5 competitors, and it returns every domain that links to at least one competitor but not to you, each tagged with a found_on array listing which competitors it links to. The composite tool, and the decision I'm unsure about Most API-wrapper MCP servers are pure 1:1 mappings. I added one opinionated composite tool, gap_outreach_targets , because the raw gap output isn't the thing you actually want — it's the raw materia

This online game helps you learn keyboard shortcuts for a bunch of different apps/software including VS Code and VIM! submitted by /u/ColterRobinson [link] [留言]

LangGraph Production, RAG Memory Challenges, and AI Agent Patterns Today's Highlights Today's highlights dive into practical LangGraph pipeline construction for agentic AI workflows, reveal critical insights from real-world RAG retrieval failures, and unveil 29 open-source design patterns for building robust AI agents. Building Your First LangGraph Pipeline: A Decision-Maker's Guide (Dev.to Top) Source: https://dev.to/labyrinthanalytics/building-your-first-langgraph-pipeline-a-decision-makers-guide-4e25 This article serves as a comprehensive guide for developers looking to implement their first LangGraph pipeline for agentic AI workflows. LangGraph is highlighted as a leading framework for building complex, stateful multi-actor applications, particularly valued for its production readiness and active maintenance. The guide aims to demystify the initial setup and design choices, providing a structured approach for integrating LangGraph into real-world applications. It addresses the common challenges and decision points faced by teams adopting new AI orchestration frameworks, ensuring a smoother development process. The piece emphasizes the practical considerations for building robust and scalable AI agents. It likely delves into architectural patterns, state management within agentic systems, and how to effectively sequence different AI models or tools into a cohesive workflow. For those focused on production deployment, the guide would cover best practices for reliability, testing, and potential optimizations when scaling AI agents. By offering a "decision-maker's guide," it goes beyond mere syntax, encouraging readers to think critically about the implications of their design choices for long-term maintainability and performance in applied AI contexts. Comment: LangGraph is a critical tool for serious agentic AI development; this guide to building pipelines and making early design decisions is exactly what many developers need to get started right. I Published an A

Apple isn't just looking to take on Meta in the smart glasses market; it's looking to upend eyewear as a whole, according to Bloomberg's Mark Gurman. When the Apple Watch launched, it wasn't simply competing against the Pebbles and the Motorolas of the world. The company also had Swatch, Fossil, and Seiko in its crosshairs. […]

submitted by /u/AdvertisingFancy7011 [link] [留言]

This is a submission for the Hermes Agent Challenge , under the Write About Hermes Agent prompt. I've spent the last week testing AI memory failure modes in a public evaluation harness. That work changed how I read agent memory systems. This is a writing submission, not a build submission. I did not build a Hermes Agent project for this challenge. I am writing from the perspective of someone testing how memory failures show up once agents can act. So when I look at Hermes Agent, the question I care about is not only: Can the agent remember useful things? The harder question is: When memory conflicts, which memory is allowed to govern the agent's action? That distinction matters. Hermes Agent is interesting because it is not just a chat interface. Its documentation describes an open-source agentic system with tool use, project context, persistent memory, skills, browser automation, checkpoints, delegation, scheduled tasks, and multiple memory providers. That is exactly the kind of system where memory stops being a convenience feature and starts becoming part of the agent's operating boundary. If an agent can run tools, edit files, browse, delegate work, schedule tasks, and remember across sessions, then memory is no longer just "context." Memory becomes governance. The Memory Problem I Would Watch For In a simple chatbot, bad memory is annoying. In an agent, bad memory can become operational. The failure mode is not only that the agent forgets something. Sometimes the more dangerous failure is that it remembers the wrong thing too confidently. A memory can be: relevant but stale, relevant but low-authority, relevant but superseded, relevant but only context, relevant but not allowed to determine the action. That is the distinction my own tests kept running into. Retrieval systems are usually good at answering: What memory is closest to the user's request? But safety often depends on a different question: What memory is allowed to decide what the agent should do? Thos

i'm trying to train an ASR model using the LibriSpeech recipe from SpeechBrain (without the language model) on a 100-hour dataset of dialectal Arabic speech. the model architecture uses a Conformer-small encoder and a Transformer decoder, with a total of around 13M parameters. the recipe uses a combination of two loss functions: CTC and KL divergence, specifically: 0.3 * CTC + 0.7 * KLDiv during training, both losses drop significantly during the first few weight updates, but then quickly plateau. the CTC loss gets stuck fluctuating around the 60-80 range, while the KL divergence loss remains around the 60s as well for the rest of training. as a result, the model does not converge properly, and the validation WER stays close to 100%. i’ve already tried several things: adjusting the learning rate, changing the number of warmup steps, modifying the number of epochs, tuning the batch size and reducing the vocabulary size from the default 5000 to 1000. none of these changes seem to help. the training dataset is not publicly available and is weakly labeled. the validation and test sets come from the MGB2 dataset. at this point, i genuinely don’t know what the root cause might be. i’ve experimented with many different approaches, but the model still refuses to converge. has anyone encountered a similar issue where their model gets stuck early in training and never improves? if so, what ended up being the cause or solution? any feedback, suggestions, or ideas would be greatly appreciated. submitted by /u/Sweet-Hamster-4991 [link] [留言]

Environmental activist Erin Brockovich has a new mission.

Overview I built Hermes Financial Agent — an AI-powered financial assistant for investors in the Egyptian Exchange (EGX). The goal: not just calculate portfolio value, but explain risks in a transparent, auditable way. Features Real EGX market data via Yahoo Finance Portfolio tracking and valuation Daily financial reports Telegram-user portfolio isolation Cached quote fallback for resilience Explainable risk insights Explainable Risk Intelligence Unlike traditional trackers, Hermes surfaces: Portfolio concentration risk Stale market data exposure Quote coverage percentage Valuation gaps from unavailable data Users understand confidence level behind their valuation — not just the number. Technical Stack Hermes Agent framework Python GitHub Actions (automated smoke testing) Offline-safe quote fallback architecture Repository 🔗 GitHub Repository Future Roadmap News sentiment analysis Investment thesis tracking Market briefing generation Advanced financial reasoning agents hermeschallenge

The premium gaming handheld's price is expected to be around $1,500.

NVIDIA's CEO Jensen Huang is set to take the stage for his GTC Taipei keynote at 8PM PT / 11PM ET. You can watch all the announcements here and embedded below. Rumors have been flying about what to expect from today's presentation, but the big one is the possibility of a partnership with Microsoft and […]