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

标签:#AR

找到 4642 篇相关文章

开发者

Building and Scaling a Platform with Project-as-a-Service

When a platform started with total developer autonomy, teams felt overwhelmed and ended up solving the same problems in completely different ways. The company shifted to enablement over support, working together with teams intensively, and helping teams feel confident and capable, turning the right way into being the easiest way. By Ben Linders

2026-06-11 原文 →
科技前沿

Enhanced License Plate Tracking

The surveillance company Leonardo wants more data : A surveillance company plans to add sensors to automatic license plate readers (ALPRs) that would mean the devices, as well as capture the license plate of passing vehicles, would also sweep up unique identifiers of mobile phones, wearables, and other Bluetooth-enabled devices in those cars, potentially letting law enforcement identify specific drivers or passengers. The technology, called SignalTrace, would turn ALPR cameras from devices focused on tracking cars to ones that can more readily track the location of particular people. ALPR cameras have become a commonly deployed technology all across the U.S.; SignalTrace would make some of those cameras capable of collecting much more data...

2026-06-11 原文 →
AI 资讯

Anthropic Fable 5's silent downgrade got walked back in 24 hours, that should concern you even more

A lot of discussion about Fable 5 has focused on the visible restrictions: cybersecurity, biology, certain chemistry. You hit a wall, you get a notification, you get redirected to Opus 4.8. That's frustrating, but at least it's honest. At least you know the model stepped back. Here's the part that's really disturbing, buried in a 319-page system card: There's a second category of restriction. For AI development and research work, Fable 5 doesn't redirect you. It doesn't notify you. It responds. It just delivers a deliberately weakened answer, and the system card describes this explicitly as "not visible to the user." Anthropic walked this back within 24 hours after fierce backlash. They apologized. "We made the wrong tradeoff." Good. But sit with what actually happened here, because the reversal is being treated as the end of the story when it's the beginning of a much harder problem. We now know three things we cannot unknow: Anthropic built this. They shipped it. And they only reversed it when the backlash was loud enough. The question isn't whether this specific invisible downgrade still exists. The question is what else might they be doing, in categories that don't generate the same backlash, that isn't disclosed in a document most people will never read anyway. This is a new kind of problem. And to understand why, you have to take a step back for a second. The pattern In January 2026, OpenAI announced that they would retire GPT-4o. Hundreds of thousands of daily users had built working relationships with that model over months: preferences it learned, corrections they made, communication styles that developed through hundreds of sessions. Gone. In February 2026, Gemini users found their chat histories had quietly vanished. No warning. No export. In April, Anthropic cut off Claude Pro and Max subscribers from using their subscriptions with third-party tools. Workflows that people depended on broke overnight. Each of these was framed differently. Model retirement

2026-06-11 原文 →
AI 资讯

Within a few years, owning the smartest AI will mean nothing — everyone will have it. The edge is knowing how to run it.

Every layer of AI solved the problem the last one left behind. The unsolved one: a shared, measurable standard for how to RUN intelligence — yours and the AI's, together. I spent 10+ years writing it down and it's falsifiable (pre-registered tests, failure lines locked before data). Asking for your strongest critiques Essay: https://joshmason573557.substack.com/p/colive-the-missing-standard-for-the submitted by /u/Useful-Ad-7895 [link] [留言]

2026-06-11 原文 →
AI 资讯

Is this music AI?

I think it is but I'd just like to get some second opinions, especially from music creators. This is their spotify page https://open.spotify.com/artist/4dSJvPjnA1RU6KcngvaZ96 The artwork is definitely AI and there's no real composer name so some red flags there already. submitted by /u/WelderRound2925 [link] [留言]

2026-06-11 原文 →
AI 资讯

[P] Extreme Imbalance Data from 100K dataset only have 56 failure [P]

as in the title, my goal is to predicting failure and RUL of machine, dataset is timestamp and when machine is failure it will labeled with 1 that only have 56 https://preview.redd.it/plbydmenmm6h1.png?width=1205&format=png&auto=webp&s=2fefe3cc2e3fe554b81c9e0b4012c5345e73ec3f From this data im ditching operating hours and humidity because it didnt show correlation for machine failure, what algorithm or deeplearning suit for it? submitted by /u/False-Seesaw-1899 [link] [留言]

2026-06-11 原文 →
开发者

Why China is betting on big nuclear reactors

It’s a tale of two nuclear industries. In China, large reactors are coming together at a stunning pace. The country has nearly doubled its nuclear fleet since 2016, reaching nearly 60 gigawatts of total power capacity. The new facilities are nearly all gigawatt-scale pressurized-water reactors. Meanwhile, the US has built just two reactors in that…

2026-06-11 原文 →
AI 资讯

Practice exams are a diagnostic, not a scoreboard: how to study for Security+ (SY0-701)

Most people studying for Security+ use practice questions the wrong way. They take a 90 question set, score a 74, feel bad, take another set the next day, score a 76, and call that progress. Two weeks later the number has barely moved and they have no idea why. The score is the least useful thing a practice exam gives you. What you actually want is a map of what you do not know yet. Here is the approach that worked for getting through SY0-701 without burning out on endless question sets. Start cold, on purpose Before you study a single domain, take a full practice exam and do not look anything up. It will feel bad. That is the point. A cold score tells you where you actually stand, not where your notes say you should be. SY0-701 is split into five domains, and they are not weighted evenly: 1.0 General Security Concepts (12%) 2.0 Threats, Vulnerabilities, and Mitigations (22%) 3.0 Security Architecture (18%) 4.0 Security Operations (28%) 5.0 Security Program Management and Oversight (20%) Domain 4 alone is more than a quarter of the exam. If you bomb Security Operations and ace General Concepts, splitting your time evenly between them is a mistake. A cold diagnostic shows you that split in about an hour. If you want one to start with, there is a free diagnostic exam at secplusmastery.com/diagnostic that breaks your result down by domain so the holes are easy to see. Review the wrong answers, and the right ones too This single habit moved my scores more than anything else: for every question I missed, I wrote down why each wrong option was wrong, not just why the correct one was correct. Security+ loves distractors that are real terms used in the wrong context. A question about a control that prevents an attack will offer you a control that detects one, and a control that corrects after the fact, all as plausible answers. If you only learn that the answer was C, you learn nothing you can reuse. If you learn that B was a detective control and the scenario asked for a p

2026-06-11 原文 →
AI 资讯

What Is RAG? Why LLM Memory Alone Is Never Enough

Ask a large language model for a specific statistic, then ask where it found that number. More often than not, the citation it gives you doesn't exist. The model will hallucinate a plausible-looking reference, confidently present outdated conclusions, or simply make things up without any internal signal that something is wrong. This failure mode has a well-known name — hallucination — and the most widely adopted engineering solution for it is RAG. RAG in One Sentence RAG stands for Retrieval-Augmented Generation. The idea is straightforward: before the LLM generates an answer, retrieve relevant document chunks from an external knowledge base, then feed those chunks to the model as context so it can compose its response based on real source material rather than parametric memory alone. Think of it like writing a research paper. You don't cite statistics from memory; you look them up first, then write your argument around verified data. RAG gives language models the same "look it up, then write" workflow. Three Structural Limitations of LLMs To understand why RAG is necessary, we need to identify the specific gaps it fills. Knowledge cutoff. Every model has a training data deadline. GPT-4's cutoff is late 2023; Claude's is early 2025. Anything that happened after that deadline simply doesn't exist in the model's world. It will either admit ignorance or, more dangerously, fabricate an answer that sounds current. Bounded parametric capacity. Even a 100-billion-parameter model can only "memorize" so much. Long-tail facts, niche domain knowledge, your company's internal documentation, yesterday's meeting notes — none of these are in the weights. No built-in fact-checking. Token generation is probabilistic sampling. The model has no mechanism to distinguish whether it's recalling a training fact or pattern-matching its way into a plausible-sounding fiction. RAG addresses all three: it supplies up-to-date, verifiable, externally sourced evidence at inference time. How RAG W

2026-06-11 原文 →