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

标签:#ci

找到 1426 篇相关文章

AI 资讯

Your brain does on 20 watts what AI needs a nuclear reactor to attempt. Last week a team figured out how to print something that actually speaks to living brain cells.

Amazon bought a 960 megawatt nuclear reactor for AI servers. Microsoft restarted Three Mile Island. Stargate is spending 500 billion dollars on data centres. All of this to do, badly, what your brain does for free on the power of a dim light bulb. The reason is that silicon processes information nothing like the brain does. Rigid chips with identical transistors trying to mimic something soft, three dimensional, constantly rewiring itself, with billions of different neurons each doing something slightly different. Northwestern University just published research showing they printed artificial neurons from MoS2 and graphene ink that produced biologically realistic electrical spikes. They tested on living mouse brain cells. The brain responded as if the signal came from one of its own cells. The breakthrough was accidental. Every other lab had been burning away the polymer residue left in the ink after printing. This team kept it. That residue created the switching behaviour that made the spikes biologically realistic. The neuromorphic computing implications here seem significant. If you can print devices that process information the way neurons do at scale, the energy math changes completely. submitted by /u/filmguy_1987 [link] [留言]

2026-05-29 原文 →
AI 资讯

I'm trying to transform a simple storyline into a 3D character

I'm creating a story for my cousin. I think it will be very interesting if this story’s main character can be a 3D character.My project is still in planning stage. I’m writing character descriptions, collecting references from Pinterest and testing some complex shapes using Tripo AI. I plan to continuously improve all the content over time. After I get a version that I like I will put it into Blender for editing and final touches.There is no final version yet but I just want to share this process with the community! I find it is so interesting to watch a story’s concept gradually become concrete lol!! submitted by /u/Final_Floor_789 [link] [留言]

2026-05-29 原文 →
AI 资讯

Step 3.7 Flash open weights dropped TODAY and the agent reliability numbers are actually interesting

Read this release today. Some crazy numbers. The tau2-bench number is 98% across all difficulty levels. That is the one that got me because usually these releases post a strong easy score and then quietly die at hard difficulty. This one... claims it holds. For multi-step agent work that actually matters more than most benchmarks. A model that drifts on step 4 of a 6 step chain is a debugging nightmare regardless of what its SWE score looks like. Raw capability is mid, Toolathlon at 49.5, GDPval at 45.8. So this is clearly a reliability play, not a frontier capability play. Depending on your use case that is either fine or a dealbreaker. 198B sparse MoE 11B activ 400 TPS 256K context Apache 2.0 runs locally on M4 Max and DGX Spark. Has anyone actually put this through agent evals or am I just reading the release card. submitted by /u/Skid_gates_99 [link] [留言]

2026-05-29 原文 →
AI 资讯

Do you really think AI can replace us?

IDK I might be wrong but.....I don't think it's happening anytime soon. ChatGPT, Claude, Gemini.....they are good....but they are too lazy. Gave them a task to create a Masterdata for all smartphone models being sold by a particular brand. Gave explicit instructions for all models. Explicitly asked for a list 1st and then asked it to create MasterData. Lazy ahh model just put in like 21 popular ones out of the hundreds of the available models and variants. Is this how it will overtake us and replace all the labor intensive work? submitted by /u/naamnhiptahai [link] [留言]

2026-05-29 原文 →
AI 资讯

Live sports might end up being one of the only truly AI-proof industries.

As GenAI starts flooding every platform, I’m beginning to wonder if live sports are one of the last truly AI-resistant industries. You still can’t prompt a model to recreate the real tension of a 14–14 tie-break in a volleyball final and maybe you never will. I read an interesting piece from NJF Holdings about this. Frankly speaking, I barely know who Nicole Junkermann is but she seems to be focused on AI infrastructure and sports rights in AI era. I agree with her, that the more polished and “perfect” AI-generated content becomes, the more valuable becomes true human unpredictability and even mistakes. The basic idea is that sports become more valuable precisely because they can’t be generated. Does that idea hold up, or do you think AI entertainment eventually becomes “good enough” to compete with the real thing? submitted by /u/AssistantStraight983 [link] [留言]

2026-05-29 原文 →
AI 资讯

SOC analysts pasting incident data into AI tools for triage and the data handling implications were never in the policy

Found this during a routine review. Analysts discovered that pasting alert context into an AI tool cut triage time significantly and started doing it because it worked, which is a reasonable thing to do when you are under pressure to move faster. The problem is that alert context includes internal hostnames, IP ranges, user identities and sometimes partial log data, none of which was supposed to leave the environment. No policy covered it because the productivity gain was not something that had been thought through when the AI use policy was written. Now trying to figure out how to give them a sanctioned version of the same capability without the data handling risk, which is harder than it sounds because the whole point is that the external tool is faster than what we have internally. submitted by /u/Only_Helicopter_8127 [link] [留言]

2026-05-29 原文 →
AI 资讯

How to investigate suspicious SSH logins without giving AI a shell

A lot of Linux incident response starts with a login question, not a malware sample. Someone sees a spike of failed SSH attempts. A root login appears in the wrong time window. A service account logs in from an address nobody recognizes. A helpdesk ticket says "the server looks weird" and the only concrete clue is a username or IP address. At that point, the useful question is not "is this host compromised?" It is more boring and more important: Did anyone actually authenticate? Which account was involved? Was it password, key, sudo, su, or a scheduled task? Was the same IP seen in web logs, current sockets, process context, or command history? Did persistence, services, packages, or recent files change near the same time? Can another responder review exactly what evidence was collected? That last point matters. If you let an AI assistant freely run shell commands during the first pass, you can get speed, but you also create a new risk: the model may over-collect, mutate the host, or produce a confident answer that nobody can audit later. For a login anomaly, I prefer a read-only evidence loop. A practical first pass Start with the narrow clue if you have one. If the alert names a user: oi login --user root -s 7d If the alert names an IP address: oi login --ip 203.0.113.44 -s 7d If the alert is vague, start wider: oi login -s 7d oi scan -s 7d The goal of the first pass is not to prove every detail. The goal is to build a timeline that a human responder can challenge. For a suspicious SSH login, I want the initial report to answer five things. 1. Authentication pattern Look for the difference between noise and access. A server can receive thousands of failed SSH attempts from the internet. That is useful background, but it is not the same as a successful session. The first split should be: failed attempts only successful login after many failures accepted key from an unusual source login by an account that normally should not be interactive root login where root SSH

2026-05-29 原文 →
AI 资讯

Presentation: Building Evals for AI Adoption: From Principles to Practice

Mallika Rao discusses the hidden risk of evaluation debt in production AI systems, drawing on her experience at Twitter, Walmart, and Netflix. She explains why traditional metrics fail modern architectures, breaks down a five-layer evaluation stack spanning infrastructure and UX, and shares a diagnostic maturity model to help engineering leaders eliminate silent semantic failures. By Mallika Rao

2026-05-29 原文 →
AI 资讯

We built an app that runs AI completely offline on your phone (Local LLMs). Perfect for flights, camping, or dead zones.

Hey everyone, A while ago, we realized a major annoyance: whenever you actually need an AI to summarize a document, write some quick code, or just brainstorm, you're usually on a flight, on the subway, or dealing with terrible cell reception. And bam, ChatGPT won't connect. Plus, there's the growing privacy concern of feeding all your personal data to cloud servers. So, my team and I started tinkering with a question: "What if we just run the AI directly on the phone's hardware?" We've been spending our evenings and weekends for months trying to make this work smoothly, and the result is Cortex AI. The logic is super simple: You download a highly optimized, small-scale local model (from our library) straight to your device. Put your phone in airplane mode, go off the grid—the AI replies entirely locally. Zero data leaves your phone. 100% private. Some real-world use cases we built this for: Coding help or summarizing offline docs while on a long flight. Getting quick answers while traveling abroad without an expensive data roaming plan. Brainstorming private ideas you just don't want OpenAI or Google to scrape. Note: We do have an optional "Online Mode" if you want to connect to massive models like GPT-4 or Claude, but the local offline models are completely free, and that's what we really want to test right now. We're currently trying to gather real user experiences on the local execution side. I'm not here to just spam a link and grab cash; we genuinely want to improve the offline mobile AI space. If anyone frequently travels, camps, or just loves local LLMs, we'd be super grateful if you could test it out. Brutally honest feedback like "runs too slow on my device," "needs X feature," or "this part of the UI makes no sense" is exactly what we need right now :) submitted by /u/Virtual_Ad_6024 [link] [留言]

2026-05-29 原文 →