AI 资讯

This article was originally published on aicoderscope.com On April 28, 2026, Warp open-sourced its terminal client under AGPL-3.0, picked up 60,000 GitHub stars, and declared itself an "agentic development environment." OpenAI signed on as founding sponsor. The announcement looked like a triumph of developer-first idealism. Read the fine print and a different picture emerges: the terminal is free; the product that matters — Oz, Warp's cloud agent orchestration platform — remains fully proprietary. Warp is not becoming an open-source project. It is becoming an enterprise SaaS company with an open-source frontend. None of that is inherently bad. But it is what this review is actually about: does the $20/month Build plan deliver enough AI value to justify adding Warp to a stack that probably already includes Cursor or Claude Code? What Warp is in May 2026 Warp's product now has three layers: Warp Terminal — the terminal client, open-source AGPL-3.0. Rust-based, GPU-accelerated, available on Mac, Linux, and Windows. The core terminal features (blocks, Warp Drive, session sharing, settings file) are free and remain free. Warp Agent — an AI coding agent embedded in the terminal. Runs locally for interactive work. Handles natural language command generation, code review, debugging assistance, codebase Q&A, and voice input. Consumes credits from your plan. Oz — Warp's proprietary cloud orchestration platform. Runs agents in the background, coordinates multi-agent workflows, triggers on events from Slack, Linear, or GitHub Actions, and orchestrates third-party CLI agents including Claude Code and Codex. Oz is where the enterprise pitch lives. Around 1 million developers use Warp as their primary terminal. The pivot to agentic tooling is a bet that those developers will pay to automate their workflows beyond what a local agent session can handle. Pricing breakdown Warp simplified its pricing in December 2025, replacing the old Pro/Turbo/Lightspeed tiers with two paid plans. P

Great to see Odysseus blow up this past day, local AI getting this much attention is genuinely good for everyone building in this space. Figured this is the right crowd to share what we're launching tomorrow (June 1st), since we're playing a pretty different game. A quick framing: Odysseus is a self-hosted workspace that points at engines (Ollama, llama.cpp, vLLM, cloud APIs) and runs through Docker. Conifer is the engine itself, with our own runtime, running natively on Mac, Linux, and Windows. So we're the layer underneath, not a competitor to the workspace. What's actually in it tomorrow: A native inference runtime across Mac, Linux, and Windows, with our own Metal engine for Apple Silicon already matching or beating llama.cpp on a few models on the M3 Max (full benchmarks, including where we're still behind, are at conifer.build/benchmarks) A real coding IDE on top (CodeMirror, integrated terminal, file viewers), so you can code locally with models that never leave your machine Typhoon, a local agent that can read and edit a folder you point it at, kernel-sandboxed rather than just a shell with a warning Install is a signed app you double-click, no Docker, no localhost ports Fully free and open source The honest reason we exist: PewDiePie's wave defined "local AI" in millions of people's heads as Linux + Docker + an NVIDIA rig. If you weren't on that exact setup, the conversation probably felt like it skipped you. Conifer is what local AI should feel like when it's actually native to your machine, whatever your machine is. Launches tomorrow, free and open source like PewDiePie! You can sign up for our waitlist here: conifer.build I'll be around in the comments all day tomorrow, please bring the hard questions. submitted by /u/No_Elephant_7530 [link] [留言]

The biggest headache im having is learning how to separate elements on the page correctly. I can center things and all, but dont know when to create a new section or just keep using the same since most things i can center or adjust using some propertie. Is there anywhere I can learn about something like this? i was trying to learn about the structure of websites trough the inspect in the browser(just to know what what are some best practices to adopt) and it just feels confusing. Im new to webdev, and was doing it to learn how to separate the divs on the page, then i asked claude to generate some random site just to read through the code, and simply everything is divs, like everything, no h1, title, nothing. From what i understand divs are the favorites because they dont have any set properties, and there's the thing about being able to arrive at the same result in different ways. But is it really the optimal way? Thank you in advance. submitted by /u/SkullDriv3rr [link] [留言]

Ok, so I had days long conversation with AI, but half of it disappeared, and now it's giving me different answers than it was before. submitted by /u/Melora1976 [link] [留言]

NVIDIA claims the new RTX Spark chip for PCs will offer 1 petaflop of AI computing power.

Without revealing too much information, what were the circumstances? submitted by /u/XTXinverseXTY [link] [留言]

Once upon a time, Microsoft had to write off $900 million betting an Arm-based Nvidia chip could power its first flagship Windows portable, the original Microsoft Surface. But today, it's trying again. Microsoft and Nvidia have just announced the Surface Laptop Ultra, a computer with a new Arm-based Nvidia chip at its core. There's a […]

With all the talk about AI companions and autonomous agents, I’ve been experimenting with building a more personal, always-on assistant that runs locally or on your own hardware. The goal wasn’t just another chatbot — it was something that could handle voice conversations, manage ongoing tasks across different platforms (chat apps, scheduled triggers, etc.), remember context over long periods, and delegate work without constant babysitting. What stood out in practice • One consistent “brain” across everything — Whether you’re talking to it via voice, Telegram, a web interface, or it wakes up on a schedule, the core reasoning, memory, and tool use stay the same. This eliminated a lot of the fragmentation you see in many current agent setups. • Modular extensions — Different capabilities (voice, different chat networks, external tools, long-term memory consolidation) plug in cleanly. This made it easier to add or swap things without rebuilding the whole system. • Persistent and proactive — It can maintain memory across days/weeks, run background tasks, and even hot-reload its configuration when you change settings. The result is something that starts feeling more like a digital collaborator than a question-answering box. A quick feel for the voice interaction style is here: https://youtube.com/shorts/NGIi8sliooU I open-sourced the harness (called Maven) under an MIT license for anyone interested in running or extending their own version: https://ageneral.ai/maven I’m curious how others are thinking about personal agent setups in 2026. • Do you prefer fully local models, cloud APIs, or a mix? • What capabilities feel most missing from today’s consumer AI assistants? • How important is “owning” your agent data and runtime vs. using polished third-party services? Would love to hear experiences or concerns from both technical and non-technical users. submitted by /u/qasimsoomro [link] [留言]

The row looked perfect. rating: 7 . Valid JSON, right type, no nulls, no missing keys. My schema check waved it through. The page had returned HTTP 200. The selectors hadn't moved. Everything green. A rating of 7 on a 5-star site is impossible. The model invented it, formatted it correctly, and handed it to me with total confidence. That's the failure I want to talk about. Not the scraper that breaks loudly. The one that hands you a clean-looking row that is quietly, plausibly false — and sails past every check you have, because your checks are all looking at the shape of the data, and the lie is in the value . TL;DR HTTP 200, intact selectors, and valid JSON tell you the form is fine. They say nothing about whether the value is true. When an LLM extracts from messy free-text, structured-output mode guarantees you get valid JSON. It does not guarantee the content is real. The model fills uncertain fields rather than leaving them empty — because the schema demands a complete row. A ~60-line value-level sanity gate (ranges, dates, cross-field, reference, language) catches the obvious lies before they hit your database. Real code and real output below. The honest catch: this gate catches rule violations , not plausible lies inside the allowed range . A rating: 4 where the truth is 2 slides right through. I'll be specific about where the gate stops. Two different ways a scraper lies to you I wrote about source drift last week — the case where the page changes underneath you and a 30-line schema check catches the structure shifting. That's an input problem. The source mutated; your agreement with the page broke; you detect it by watching the shape. This is the other end of the pipe. The source is fine. The page is intact, the selectors are correct, the structure is exactly what you expected. The thing that lied to you is the model , on the extraction step, when you asked it to pull structured fields out of a paragraph of human prose. Those two failures feel similar and t

I spent way too long staring at this error. If you're here, you probably are too. Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.3 but your php version (8.2.30) does not satisfy that requirement. My Laravel 13 app needed PHP 8.3. My Hostinger server was running 8.2. composer install refused to budge. Here's exactly what happened and the one-liner that fixed it. The Setup I was deploying a Laravel 13 + Inertia + React app to Hostinger shared hosting. Laravel 13 requires PHP 8.3 minimum — and so do its locked Symfony 8.x and PHPUnit 12.x dependencies. My composer.lock had been generated on a local machine with PHP 8.3, but Hostinger's CLI was defaulting to 8.2. The hPanel showed PHP 8.3 selected under PHP Configuration . The website itself was running fine on 8.3. But SSH? Still on 8.2. $ php -v PHP 8.2.30 ( cli ) That disconnect — hPanel vs. CLI — is the trap. What I Tried First composer update My first instinct was to just let Composer resolve newer compatible versions: composer update No luck. The root composer.json itself declared "php": "^8.3" , so Composer refused before even touching the lock file. The PHP constraint wasn't just in dependencies — it was in my own project requirements. composer install --ignore-platform-reqs This flag skips platform checks and forces the install anyway. It works , but it's a lie — you end up with packages that may behave incorrectly or fail at runtime because they genuinely require PHP 8.3 features. Not a real fix. Changing PHP in hPanel Hostinger's control panel has a PHP version switcher under Hosting → Manage → PHP Configuration . I had already set this to 8.3. This controls the web server / FPM version — what runs your .php files in the browser. It does not change what php points to in your SSH terminal. That's the key distinction most tutorials miss. What Actually Fixed It Hostinger installs multiple PHP versions in parallel. They live in /opt/alt/ph

Based on real system architecture decisions. About a $660K AI platform, three AI agents that kept the dashboard green, and a P0 incident that cost $3.15M over one weekend. Act 1 · The All-Hands Meeting Wang Lei, VP of Product, stood in front of the big screen, a smile on his face. Behind him, a dashboard rolled data from the "Axon AI Client Engineering Platform — Q1 Performance Report." Numbers cascaded across the wall: Metric Axon Platform Human Team (Last Q1) Improvement Avg daily tickets processed 847 312 +171% Avg first response time 12s 4h 17m ↓ 99.92% Customer satisfaction 4.8/5 4.1/5 +17% Monthly operating cost $52K $133K −61% Twelve department heads sat in the room. Dead silence. Wang Lei planted both hands on the table and scanned the room. His eyes landed on me. "Alex. Your team processed 312 tickets last Q1. Axon processed more than that in a single day last month." He smiled. Not a friendly smile. A sentencing smile. "And Axon costs less than a third of your team's operating expense." "We invested $660K in the whole platform. At current operating costs, it pays for itself in eighteen months." "After management review — the Client Engineering technical liaison function is being fully transitioned to the Axon platform." He clicked to the next slide. "Employees in replaced roles will complete exit interviews within the week." Someone inhaled sharply. I didn't. I opened my notebook to page 37. "Wang, what dimensions are these numbers from?" "What do you mean, 'what dimensions'?" His smile tightened. "Of those 847 daily tickets — how many are auto-tagging and routing, and how many are actual technical resolutions?" The room went quiet for about five seconds. Wang Lei looked at me. "Axon's ticket closure rate is ninety-three percent." "What's the reopen rate?" He paused. "What?" "After Axon replies — how many customers reopen the same ticket within twenty-four hours?" "We're still collecting that —" "Let me save you the trouble." I turned my notebook toward th

[Paper Notes] JEPA: Self-Supervised Learning from Images with a Joint-Embedding Predictive Architecture 🔗 TL;DR: JEPA learns a a generalized semantic representation with less data pairs by predicting missing information in the embedding space , which helps it disregard unnecessary noisy from input(pixel)-level details and learns at a higher abstraction level with good semantic generalization. 1. Innovation & Significance The Bottleneck: Image-text data pair labels are hard to find Pixel level pre-training paired & data augmentation are strongly biased towards trained data distribution, hard to determine proper generalization and level of abstraction. JEA's (Joint Embedding Architecture) collapse probelm: encoder & decoder attempts to cheat by always landing on trivial constant when predicting itself (reconstruction) and gets away with an easy Error=0. The Solution: > Chain-of-thought ⭕ Mask pre-training to reduce data & generalize↓❌ Bad/lower semantic representation without semantic target, could be learning noisy local pixel correlation↓⭕ Learn at the embedding level to omit pixel input and generalize⭕ Adds context encoder & positional encoding to inject context and force model to pick up image inherent structure from reconstructing multiple masked patches with one target.↓❌ JEAs wants to cheat: if I always map all pixels to a constant for both the predictor and end target encoder then the reconstruction error is always collapsed to zero! Hehe~ ↓ ⭕ EMA (Exponential moving avg.): Update target encoder parameters from the EMA of context encoders. This 'delays' the target encoder to prevent collapsing (a trick from the BYOL paper[2020], proven essential to training JEAs with ViT). 2. Model & High-Level Intuitions 2.1 Model Architecture Input: randomly samples block masks from original image within certain aspect ratio changes, and apply mask for context image 2.1.2 Context Context Encoder: ViT encodes context image to embedding SxS_x S x ​ Mask Token : an [1,D] random

I know the most popular are Claude, chat got and Gemini but idk which one to use submitted by /u/Ok_Durian3627 [link] [留言]

Last year I needed to ask for a raise. I knew my number, I'd read the guides, I had bullet points in my notes app. Then my manager said "let's chat about your goals for next quarter" and I said "sounds great, looking forward to it" and hung up. Never brought up money. Same thing kept happening elsewhere. Coworker taking credit for my work, I said nothing. Relationship that should've ended months earlier, I kept postponing. I always knew what to say. I just couldn't say it with someone actually looking at me. So I started building a thing to practice on. That thing became cosskill . What it actually is You pick a persona, tell it the situation in a sentence, and start talking. The persona doesn't help you. It holds position and pushes back. You practice not folding. Think of it as a flight simulator for hard conversations. You rehearse until your opener comes out steady, then go do the real thing. 20 personas across five categories: Operators (Musk, Jobs): first-principles thinking, harsh product feedback Strategists (Trump, Buffett): treat everything as a deal or a bet Relationship (Ex, Coworker): breakups, workplace friction, family money Philosophy (Socrates, Aurelius, Confucius, Sun Tzu, four more): each tradition frames problems differently Psychology (Rogers, Rosenberg, Ellis, Frankl, Kahneman, Jung): therapeutic frameworks on real situations These aren't celebrity impressions. The Buffett persona won't hype your startup idea. It'll ask "what's the downside?" and keep asking until you have something concrete. Tech stack Next.js 16 on Cloudflare Workers. DeepSeek for inference. Cloudflare D1 (SQLite at edge) for the bits that need to persist. No user accounts, chat history lives in localStorage. Monthly cost stays low enough that the free tier (10 messages/day) doesn't worry me. Why I made these choices DeepSeek instead of GPT-4/Claude. Each conversation is 10-30 messages. At GPT-4 pricing a free product bleeds money. DeepSeek gives maybe 90% of the quality for

Frontend request code often involves repetitive state management. This article compares Axios and alova through a paginated list example, analyzing how request strategization reduces boilerplate and when it's a good fit. The Pattern: Paginated List in Two Ways A common requirement: fetch a user list with pagination. Approach 1: Axios const [ data , setData ] = useState ([]); const [ page , setPage ] = useState ( 1 ); const [ total , setTotal ] = useState ( 0 ); const [ loading , setLoading ] = useState ( false ); const [ error , setError ] = useState ( null ); const fetchUsers = async ( currentPage ) => { setLoading ( true ); setError ( null ); try { const res = await axios . get ( ' /api/users ' , { params : { page : currentPage , pageSize : 10 }, }); setData ( res . data . list ); setTotal ( res . data . total ); } catch ( e ) { setError ( e . message ); } finally { setLoading ( false ); } }; useEffect (() => { fetchUsers ( page ); }, [ page ]); This pattern appears in nearly every data-fetching component. The actual business logic — GET /api/users — occupies a single line. The rest is infrastructure: state declarations, loading toggles, error handling, and effect management. Approach 2: alova with usePagination const { data , total , loading , error , page , pageSize , nextPage , prevPage , } = usePagination ( ( page , pageSize ) => alovaInstance . Get ( ' /api/users ' , { params : { page , pageSize }, }), { page : 1 , pageSize : 10 } ); Both implementations are functionally identical. The key difference is where the state management logic lives: in the component (Axios) vs. inside the hook (alova). What Changed Component of Axios version Handled by alova loading state + toggling Managed internally by usePagination error state + try/catch Managed internally by usePagination data state + assignment Returned as reactive value page state + change handler Built-in nextPage / prevPage total state extraction Extracted from response automatically useEffect dependency tr

ive been scrolling on tiktok and instagram reels, found out that the subjects in these specific ai skit videos generated by chinese people tend to have a really bad negative canthal tilt and same face syndrome. after a while, i noticed some ai advertisements are getting the same negative canthal tilt issue, the ethnicity, age, gender dont matter in this case, they all have a same eyes i can only attach one image, but i have 2 other examples i came across. submitted by /u/Deanphoque [link] [留言]

Introduction to AWS certifications First things first, lets understand what the AWS Security Specialty certification is and where it fits in the AWS certification ecosystem. AWS certifications are divided into levels, each one targeting a different stage of your journey: Practitioner Associate Professional Specialty The practitioner level is where most people start. It focuses on foundational cloud concepts and basic AWS knowledge. As of today, there are two certifications at this level: AWS Cloud Practitioner AWS AI Practitioner The Cloud Practitioner covers core concepts like IAM, security, availability, pricing, and general cloud architecture. The AI Practitioner follows a similar structure, but focused on AI concepts and AWS AI services. The associate level is where things start to get more practical. At this level, you are expected to understand how to design and build solutions using AWS services. Some well-known certifications here are: Solutions Architect Associate Developer Associate SysOps Administrator The professional level goes much deeper. Here, you are expected to design complex architectures, handle trade offs, and make decisions based on real world constraints. The main certifications are: Solutions Architect Professional DevOps Engineer Professional Finally, we have the specialty certifications. These are focused on specific domains and require deep knowledge in a particular area. Examples include: Security Specialty Machine Learning Specialty (Retired) Advanced Networking Specialty And this is exactly where things start to get serious. At this level, AWS is no longer testing if you understand the services. It's testing if you can actually apply them in complex, real world scenarios. What it is and who this certification is for The AWS Security Specialty is one of the most difficult certifications in your AWS journey. This exam expects that you already know the basics and are comfortable with complex and long detailed scenarios that you often come