今日已更新 329 条资讯 | 累计 40774 条内容
关于我们

标签:#Robot

找到 169 篇相关文章

AI 资讯

Block AI Crawlers: The 15 Bots That Matter

Most lists that claim to help you block AI crawlers are copy-pasted and dangerously wrong about the two tokens that actually matter. Sorting them properly is not an abstract taxonomy exercise. It is the single decision that determines whether your content vanishes from AI answers while training continues — or vice versa. We maintain the crawler registry in lib/ai-crawlers.ts that powers techpotions’ free AI robots.txt generator . Every agent string and description was verified against the operator’s own crawler documentation. The registry holds 15 verified bots across four categories, and that four-way split is this article’s structure, because the categories map directly to what blocking costs you. Two tokens almost everyone gets wrong Before the list, the single most important correction to make, and almost every listicle on this query gets it wrong: Google-Extended and Applebot-Extended are not crawlers. They are robots.txt tokens — product controls that govern whether your content is used for Gemini and Apple foundation-model training. Blocking Google-Extended does not affect Google Search crawling, Google ranking, or regular Applebot search indexing. People block them believing they are opting out of AI Overviews, and are actually opting out of nothing they think they are, while leaving search indexing completely untouched. Platforms have started wiring these tokens into one-click controls. Cloudflare’s managed robots feature, released mid-2025, lets you add AI crawler rules through a dashboard toggle rather than editing a raw file — but the underlying token logic above still applies. Block AI crawlers: the four categories that decide the cost Every AI crawler we track belongs to one of four categories. The category tells you the cost of blocking it. Training crawlers scrape pages to feed a model that may never cite you. Blocking them is a defensive data decision. Assistant crawlers fetch pages to answer a live user’s question and can cite and link you. Blockin

2026-07-30 原文 →
开发者

The US government just banned Roombas

When the Trump administration announced yesterday that it was banning "advanced robotic devices" from entering the United States, the headlines were all about humanoids. But spying doesn't require legs - and neither does the FCC's robot ban. The robot ban will sweep up robot vacuum cleaners too, FCC media relations director Katie Gorscak confirms to […]

2026-07-30 原文 →
AI 资讯

The US is banning foreign robots

The US government is targeting China with a new import ban on "advanced robotic devices" and power inverters made in foreign countries, as reported earlier by Reuters. In an announcement on Tuesday, the Federal Communications Commission says the ban will include "mobile" robots, such as humanoid and quadruped models - but it is not limited […]

2026-07-29 原文 →
AI 资讯

Link Manual Test Cases to Playwright and Robot Specs

Most teams already keep Playwright or Robot Framework specs next to the product. Manual cases often live somewhere else — a spreadsheet, a cloud TMS, or a wiki page nobody updates after the first release. That is why automation coverage is usually a quarterly guess: the catalog and the specs never share an id. Put both in the same Git repo , give every manual case a stable id, and linking becomes a text match. Any IDE agent can do that if the cases are files it can already see — no custom AI product inside a test tool. One repo, two layers of the same suite Manual cases are YAML files under .gitoza-lite/test/cases/ (VS Code / Cursor extension) or .gitoza/test/cases/ (Desktop app). The filename without .yaml is the case id . Automated tests live wherever your team already puts them — tests/ , e2e/ , robot/ — in the same repository. Traceability is a shared id: put that case id on the automation side as a tag (or name), and on the YAML side as automated: true plus a params pointer. A PR can change the case, the Playwright spec, and the link in one review. Step 1 — Draft manual cases in the IDE Open the repo in Cursor or VS Code. Point the agent at a few existing case files so it learns your title style, tags, and step length. Then feed it a user story, a ticket, or a screenshot. Ask for several cases at once, not one shallow step. A useful prompt looks like: Read .gitoza-lite/test/cases/shopflow/auth/ for format. From ticket SHOP-184, draft three YAML cases (happy path, invalid password, locked account). Filename = case id. Use tags auth and smoke where it fits. Save the files under the suite folder. Then open the Gitoza Lite Test Repository tab to browse, edit, and — when you are ready — run them as a manual suite with Pass / Fail / Skip. The extension does not ship its own model. It keeps cases as plain YAML so whatever assistant you already use can read and write them. A minimal case: --- title : Login with valid credentials priority : high tags : [ smoke , auth ]

2026-07-22 原文 →
AI 资讯

The Robotics Tech Tree: the structured map I wish I had from LED to Physical AI

I was tired of buzzword-heavy AI projects and marginally impactful demos. Surely we can do something more inspiring with these LLMs than build another chatbot? For me, the answer is physical AI: the moment all those breakthroughs finally reach into the real world, in robots that see, move, and figure things out for themselves. I think it is the most exciting frontier in tech right now. It is also genuinely hard to break into, because it is not one field. It is about five of them stacked on top of each other: electronics, mechanics, programming, data, and AI. Eight months ago I started my own robotics journey from scratch, and I was completely overwhelmed. How do you get from blinking an LED to a humanoid that does your dishes? There are thousands of scattered tutorials out there, with no sense of what comes first, or what any of it is building toward. So I decided to build the map. Stealing the best idea from my favorite games: If you have ever played a factory-building or strategy game like Satisfactory or Civ Six, you know the feeling. You start with almost nothing, and you unlock new tech one satisfying step at a time. Those games are proof that we will happily spend hours mastering an intimidatingly complex system, as long as it is laid out as a clear tree of unlocks. So why not point that same instinct at learning something real? That is exactly what a tech tree is: a structured, visual path where each node is a skill and each connection is a prerequisite. You start at Curiosity on the far left and work your way right, through electronics, mechanics, code, data, and AI, all the way toward autonomous robots and humanoids. The idea is simple: turn gaming time into learning time. What the tree actually is Every node on the tree is a skill to learn, and the star-shaped nodes are hands-on projects where theory finally meets a soldering iron. Nodes are color-coded by discipline, so you can see at a glance whether you are in electronics, mechanics, programming, data s

2026-07-18 原文 →