AI 资讯

ok this is gonna sound dumb but bear with me I write a lot for work, marketing/copy stuff mostly, and over the last ~14 months ive slid from "use AI to clean up my draft" to "use AI to make the draft" to honestly not really writing anything on my own anymore. like i hadnt put a complete thought on paper without a model in the loop for months. didnt even notice it happening tbh. last weekend i tried to write a journal entry. just for me, no audience. nothing fancy. sat there for like 20 minutes trying to remember how to start a sentence that didnt have a thesis at the front of it. i kept wanting to write "Today I noticed three things about my mood." and then realising — wait, no, thats a chatgpt sentence. nobody writes that. but i couldnt remember the person-version. eventually wrote some half-garbage about being tired and what i ate and a weird thing my sister said about her landlord. it read like a 12 year olds diary which, fine, i guess thats what a journal is supposed to be but the embarassing part. i had to physically stop my hand from opening the chat app to "help with the wording". my brain was treating writing like a thing AI does, not a thing i do. felt like reaching for a phantom limb. idk man. anyone else fine until they try to write something with no audience? like the second the audience disappears the chatgpt brain pattern is whats left underneath? not really asking for advice or anything. just wanted to say it out loud somewhere submitted by /u/Napster3301 [link] [留言]

Like, no matter which topic I'm researching, whether it's sports or nutrition or technical stuff, it's hallucinating all the fucking time. Then, in vscode, when using pro 3.5 via API, it constantly ignores coding instructions, it constantly isn't able to fix the simplest mistakes in the code, it repeats the same mistakes over and over and fucking over again and then apologizes ("oh sorry, you were right"). Like what the fuck? This is extremely bad quality, how the hell is this even still viable? submitted by /u/eternal_sunshineeeee [link] [留言]

The AI productivity paradox states that AI scales whatever abstraction it is built on. If that abstraction is structurally brittle, it scales structural brittleness. This article shows how, to build a future of reliable, AI-driven test automation, we must stop scaling DOM-centric abstractions and build a new testing paradigm grounded in perception and intent. By Amanul Chowdhury, Vinay Gummadavelli

Dozens of people have complained to the Federal Trade Commission about Norse Atlantic Airways’ tech-first customer service operation. Some said they lost thousands of dollars.

I tried to explain OpenAI’s solution more clearly than OpenAI did.

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

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

Solo dev here. Building an AI companion that lives entirely on your device — no cloud, no account, no data ever leaving your phone. Coming soon to Google Play. Would love honest feedback. I genuinely just want opinions. It is not even available yet. I have been working on this for over a year. I am still building it. I started this project because a regular family budget like mine cannot just go out and purchase an AI companion robot. So I started with a cheap robot kit from Amazon — something my 9 year old son and I could build together. Then I thought... "What if I could give it a real brain?" I had an old Samsung Galaxy collecting dust and went to work. Scout is a calm AI companion that transforms an old phone into a friend. He listens, remembers, learns, and provides a warm family-safe presence — designed to feel less like an assistant and more like someone who is simply glad you are there. Everything runs offline. No account. No subscription. No data leaving your phone. Ever. I will need beta testers later — but right now I am just curious: What would make you look at something like this and think "that is actually kind of nice"? Edit: It will what support your own free Gemini key for online conversations if you want them. I call this "more Intelligent conversations" submitted by /u/CapeManCoral [link] [留言]

The Seoul-based rocket startup is developing its own launch vehicles and engines.

OpenAI frontier models and Codex are now generally available on AWS, giving enterprises a new path to build with OpenAI through the AWS environments, controls, and procurement workflows they already use. Customers can get started with OpenAI on AWS and move faster from evaluation to production.

There might finally be a way forward for long Covid treatment—if only you were allowed to talk about it.

A security researcher found that adding a trailing slash to AWS HTTP API paths bypassed Lambda authorizer authentication entirely, enabling unauthenticated wire transfers at a fintech. The root cause is a path normalization mismatch between HTTP API's greedy route matching and its authorization layer. The same vulnerability class appeared in gRPC-Go via CVE-2026-33186. By Steef-Jan Wiggers

Animations can make an application feel faster, smoother, and more polished. However, many developers think animations are only useful for things like: page transitions modals enter/leave effects But Vue provides another powerful pattern - State-driven animations. Instead of animating when elements are added or removed from the DOM, you animate changes in reactive state. This allows you to create rich interactive experiences while keeping your code declarative and easy to maintain. In this article, we'll explore: What state-driven animations are How they differ from regular Vue transitions What problems they solve How to implement them in Vue Best practices for creating smooth UI interactions Let's dive in. 🤔 What Are State-Driven Animations? Most Vue developers are familiar with the <Transition> component. Example: <Transition> <Modal v-if= "isOpen" /> </Transition> This animates an element when it enters or leaves the DOM. But what if the element already exists and only its state changes? For example: a progress bar grows a card expands a chart updates a panel changes size a value changes position This is where state-driven animations shine. Instead of animating DOM insertion or removal, you animate changes caused by reactive state. 🟢 What Problem Do State-Driven Animations Solve? Without animations, state changes can feel abrupt. Example: <div :style= "{ width: progress + '%' }" ></div> When progress changes: progress . value = 80 The width instantly jumps. This works technically... but it doesn't feel great. 🟢 A Simple Example Let's create an animated progress bar. < script setup lang= "ts" > const progress = ref ( 20 ) function increase () { progress . value += 20 } </ script > < template > <button @ click= "increase" > Increase Progress </button> <div class= "progress-container" > <div class= "progress-bar" :style= " { width: `${progress}%` }" /> </div> </ template > CSS: .progress-container { width : 100% ; height : 12px ; background : #eee ; } .progress-bar

Hello Dev Community! 👋 It is officially Day 8 of my journey to master the MERN stack! After spending the first week structuring with HTML and styling with CSS, today I finally started learning the core language of web logic: JavaScript . Moving from static designs to actual programming logic feels like unlocking a whole new level of web development. 🧠 Key Learnings From Day 8 Today was all about setting up the foundation in JavaScript and understanding how code runs in the browser. Here is what I covered: 1. The Browser Console & Execution I learned that every browser has a built-in environment to run JavaScript. Writing my very first console.log("Hello World"); and seeing it print in the developer tools console was the perfect start. 2. Variables: Storing Data Safely I learned how to store information using variables and the crucial differences between modern variable declarations: let : For values that can change later in the program (mutable). const : For values that must remain constant and cannot be reassigned (immutable). Note: I also read about var , but learned why modern JavaScript avoids it due to scoping issues. 3. Data Types Fundamentals Data needs a type so the computer knows how to handle it. Today I practiced with: Strings: Plain text enclosed in quotes (e.g., "MERN Stack" ). Numbers: Integers and decimals without quotes (e.g., 2026 ). Booleans: Simple true or false states (e.g., isLearning = true ). 🛠️ What I Actually Code / Experimented With Since I am just starting with core logic, I didn't write code directly into my HTML webpage layout today. Instead, I created a script.js file, linked it to my project, and built a basic script in the console that: Stores a user's name and learning status in variables. Dynamically calculates values (like years left until a milestone). Outputs formatted statements into the browser console. It is simple, but understanding how data moves in the background is incredibly exciting. 🎯 My Goal for Tomorrow (Day 9) Tomorr

If you run a website that serves European users — or if you’re based in the EU yourself — hosting location is no longer just a technical detail. It has become a strategic and legal consideration. In 2026, questions around data residency, GDPR compliance, and digital sovereignty are front and center for businesses of all sizes. Choosing where your website and its data live can affect everything from legal risk to user trust and even search engine performance. The core issue: Where does your data actually live? When you choose a hosting provider or CMS, your content, user data, images, and analytics often get stored on servers in a specific country or region. This matters because different jurisdictions have different laws regarding data access, privacy, and government requests. Key concerns include: GDPR compliance : The EU’s strict data protection regulation requires that personal data of EU citizens be handled with strong safeguards. Transferring data outside the EU/EEA can trigger additional legal requirements (such as Standard Contractual Clauses). Schrems II and data transfers : Following court rulings, simply relying on old mechanisms for transferring data to the US became more complicated. Many organizations now prefer to keep data within the EU to reduce legal complexity. Data sovereignty : Some companies and public sector organizations want (or are required) to ensure their data is stored and processed under EU jurisdiction. Performance and latency : Hosting closer to your users generally means faster load times — which also helps SEO and user experience. For many European businesses, especially those handling any form of personal data (even something as simple as contact forms or newsletter signups), EU-based hosting has become the safer, simpler default. Why traditional hosting often falls short Many popular CMS platforms and hosting providers are headquartered outside Europe. While they may offer data centers in the EU, the company’s legal jurisdiction, d

Modern search engines do more than match keywords. When you search for "cozy mystery set in Paris" and get results for "atmospheric detective novel in France" that's vector search at work: documents and queries are converted into lists of numbers, called embeddings, and the search engine finds the documents whose numbers are closest to the query's. Manticore Search supports this natively. Under the hood, it uses a data structure called HNSW: a graph that connects nearby vectors, so it can find nearest neighbors quickly without scanning every document. That makes vector search fast enough to run on millions of documents in milliseconds. But HNSW has an inefficiency. Early in the traversal, almost every distance computation finds a better candidate than the ones already in the result set. As the search goes on, those improvements become rarer, but the algorithm keeps traversing the graph until it exhausts its exploration budget. By that point, the result set has often already converged, and the remaining work does little or nothing to improve it. Early termination fixes this by detecting that point and stopping early. The effect becomes more noticeable as k grows, where k is the number of nearest neighbors the query asks Manticore to return. Returning more neighbors requires more graph exploration, and much of that extra work happens after the result set has already stabilized. That also makes early termination more valuable, because it has more unnecessary work to cut. This gets more pronounced with vector quantization . Quantization compresses stored vectors to save memory, which slightly lowers search precision. To recover it, Manticore uses oversampling : it fetches 3x more candidates than requested, then rescores them using the original full-precision vectors. With the default 3x oversampling, HNSW explores many more candidates per query. Large k values often come from this kind of candidate expansion: an application may ask the vector index for hundreds or thous

As the web has evolved, so have the strategies for rendering content in browsers. Two of the most widely used approaches today are Server-Side Rendering (SSR) and Client-Side Rendering (CSR). Each has its strengths and trade-offs, and understanding when to use one over the other is key to building fast, scalable, and user-friendly applications. This article explores the key differences, benefits, and common use cases of SSR and CSR, with practical examples. What is Client-Side Rendering (CSR)? Client-Side Rendering means that the browser downloads a minimal HTML shell and renders the content using JavaScript. Most of the work, fetching data, templating, and updating the DOM, happens in the user's browser after the page loads. Benefits Rich interactivity: Ideal for dynamic single-page applications (SPAs). Fast navigation after initial load: Once loaded, switching between views is instantaneous. Great for app-like experiences: Think dashboards, SaaS tools, or email clients. Drawbacks Slower initial page load: The user sees a blank screen until JavaScript loads and executes. SEO challenges: Search engines may struggle to index dynamic content, unless SSR or prerendering is used. Poor performance on slow devices: All rendering logic happens in the browser. What is Server-Side Rendering (SSR)? Server-Side Rendering generates the full HTML on the server for each request. When a user visits a page, the server fetches the data, compiles the HTML, and sends it to the browser, which then hydrates the app into an interactive component. Benefits of SSR: Fast time-to-first-byte (TTFB): HTML is ready and shows up immediately. Better SEO: Search engines receive fully rendered pages. Good for public-facing content: Blogs, marketing sites, e-commerce pages. Drawbacks Increased server load: Every page request triggers rendering logic. Longer time to interactivity: HTML loads quickly, but hydration takes extra time. Requires server infrastructure: Cannot be purely deployed as static f

Not every old business web app needs a full Internet Explorer environment. That sounds obvious, but it is easy to miss when a legacy intranet, ERP, OA, or ASP.NET WebForms page fails in Chrome or Microsoft Edge. The first instinct is often to put the whole system into IE mode. Sometimes that is absolutely correct. Other times, the page mostly works in Chromium and only breaks on older JavaScript or DOM assumptions. The useful first step is to separate those two cases. Case 1: the page needs a real IE engine Use Microsoft Edge IE mode, a Windows virtual machine, remote desktop, or another managed legacy-browser path if the page depends on: ActiveX controls COM integration VBScript Trident or MSHTML rendering behavior Browser Helper Objects Java applets strict IE7 or IE8 document modes A Chrome extension or JavaScript compatibility layer should not be presented as a replacement for those requirements. If the workflow depends on the IE engine, the browser engine is part of the application runtime. Case 2: the page mostly works, but old browser assumptions fail There is another common category. The page loads in Chrome or Edge, authentication works, and the main UI appears, but a small set of old behaviors fails. Examples include: empty frameset entry pages loading pages that do not finish redirecting attachEvent window.event event.srcElement showModalDialog -style picker flows document.frames older WebForms date fields that call a calendar function on focus For maintained source code, the best answer is still to fix the application. Replace old event APIs, remove synchronous dialog assumptions, and modernize generated WebForms scripts where possible. But in many real organizations, the legacy page is owned by a vendor, frozen department system, or migration backlog. In that situation, a scoped compatibility layer can be worth testing before moving the whole workflow into IE mode. A low-risk triage sequence I use this sequence: Pick one legacy hostname. Pick one failing