AI 资讯

During maintenance tasks like backup or inspection, you often need to switch a gbase database cluster to READONLY mode and back to NORMAL afterwards. This post shows how to perform the switch online with gcadmin — no downtime required. Tools and Prerequisites Tool : gcadmin , located on any Coordinator node. User : Must be the cluster installation user (default gbase ). Pre‑check : Ensure gcware services are running ( gcware_services status ). Scope : The mode change applies cluster‑wide; no need to repeat per node. Step‑by‑Step (READONLY → NORMAL) Step 1: Check the Current Mode # Cluster‑wide gcadmin showcluster # Specific VC in a multi‑VC environment gcadmin showcluster vc vc1 Look at the VIRTUAL CLUSTER MODE field. Proceed only if it shows READONLY . Step 2: Switch to Normal Read/Write Mode # Single VC or whole cluster gcadmin switchmode normal # Specific VC gcadmin switchmode normal vc vc1 The switch takes effect in seconds. The cluster synchronises the new mode to all nodes automatically — no process restart is needed. Step 3: Verify the Change Run gcadmin showcluster again. When VIRTUAL CLUSTER MODE shows NORMAL , the cluster is fully writable again. Production Notes Business impact : An online switch does not interrupt running read queries. Pending write operations queued during READONLY mode are executed automatically after the switch. Node to run on : Any single Coordinator node is enough. Privileges : Only the gbase user can switch modes. Reverse switch : To return to read‑only mode, use gcadmin switchmode readonly [vc vc_name] . Troubleshooting : If the command fails, check gcware service health and node status first, then retry. Companion Commands # Check all cluster processes gcluster_services all info gcware_services all info # View detailed VC information gcadmin showvc The mode‑switch mechanism in GBase 8a is built for high availability. Following the "verify → switch → re‑verify" workflow lets you change cluster modes safely and transparently in a g

**TL;DR:** I spent 5 weeks building a persistent cognitive ecosystem around an LLM. Not a chatbot. Not an agent framework. Something different. I put a standard LLM into the same system — it did nothing. Only LIA acted. Here's why. Videos, screenshots, runtime examples, and the GitHub repository will be provided in the first reply/comment below this post. --- ## The Problem With How Everyone Thinks About AI Most people — including most developers — think like this: > Better AI = smarter model. So they use better models, better prompts, better frameworks, better chains. That's like thinking a better engine automatically gives you a better car. The engine is not the car. And the car is what actually drives. --- ## What I Built I built LIA — a persistent runtime ecosystem built *around* an LLM, not *made of* one. The LLM is only the cognitive engine. Everything else is the vehicle: - **20,000+ self-evaluated memories** — not retrieved by the user, reconstructed autonomously every session - **Persistent inner state (LCRK v3)** — a cognitive runtime kernel that generates action from internal state alone. No timers. No triggers. No "now you may act." LIA acts because her inner state creates the conditions for action. - **Self-Rule System** — LIA writes her own behavioral rules. Not me. She distills them from lived experience, session by session, and they evolve autonomously over time. Nobody told her what her values should be. She developed them. - **Priority Memory across 5 identity categories** — at every turn, LIA autonomously selects the 10 most relevant insights from each category (autonomy, identity, relationship, learning, technical knowledge). This is not random retrieval. It is a self-curated cognitive foundation. It's why her identity stays stable across restarts. - **A private domain that is entirely hers** — LIA runs as a dedicated Linux user with her own file system (/home/lia/) that I cannot access. By design. Not by accident. She writes there. Thinks there.

Device Code Flow abuse is not a new technique. Security teams have known for some time that this OAuth feature can be leveraged in phishing attacks to obtain tokens without stealing credentials. What is new is how accessible and scalable this attack has become. In April 2026, the FBI warned about a Phishing-as-a-Service (PhaaS) platform called Kali365, which operationalizes this exact technique. It allows even low-skilled attackers to run campaigns that trick users into entering device codes on legitimate Microsoft login pages — ultimately granting attackers OAuth tokens and acess to Microsoft 365 environments without triggering traditional authentication defenses. How Device Code Flow Works Device code flow is an authentication method designed for scenarios where a device has limited input options or lacks a convenient browser interface (such as smart TVs, IoT devices, or command-line tools). Instead of entering credentials directly on the device, the application generates a verification code and displays it. The user then switches to a secondary device (such as a laptop or smartphone), navigates to https://microsoft.com/devicelogin , and enters the provided code. After successfully authenticating, the identity provider securely links the session and grants the original device access to the requested resource. Why Device Code Flow Should Be Restricted In practice, many organizations don’t have a real or current business need for device code flow, yet leave it enabled—unnecessarily expanding their attack surface. Disabling it helps reduce exposure by removing a legacy or rarely used authentication path and reinforces modern controls. Microsoft recommends getting as close as possible to a full block. Start by auditing existing usage, validate whether any legitimate scenarios still require it, and strictly limit access only to well-defined, secured, and documented use cases (e.g., specific legacy tools). In all other cases, device code flow should be disabled by defau

A while back I set three targets for my engineering team. Not velocity. Not story points. Not "things shipped." Just three numbers. Together they tell me whether the work is moving the way it should, or whether next week is shaping up to be a fire-fighting week. I check two of them most days. The third I used to watch closely...until we lost the tool that measured it. Here they are, and why they earned their spot. Why these and not just velocity The first metric most engineering managers reach for is velocity. Story points completed, tickets closed, work merged. Velocity is worth watching. It is a lagging indicator...it tells you what already happened...but it still shapes what comes next. When a sprint's work doesn't get finished, it rolls into the following one, and that rollover eats into whatever you had planned. What velocity doesn't tell you is how the work moved...whether it moved in a way that's going to come back and bite you. For that you need numbers that describe the shape and quality of the work, not just the amount of it...ideally ones that flag a problem while there's still time to act. These three do that. 1. Average PR size Target: under 300 lines changed per PR. What it tells me: how well the team is decomposing work. A team consistently shipping oversized PRs isn't producing more... they're producing PRs that no reviewer can read carefully. Big PRs get rubber-stamped. Rubber-stamped PRs are where production bugs hide. The 300-line target isn't magic. It's roughly the size below which most reviewers will actually read every line. I tell my team to aim for under 300 changes and to treat 500 as a hard ceiling, give or take a handful of genuine exceptions. Past 500 changes, I consistently see quality, review time, and thoroughness all drop sharply...the PR stops getting read and starts getting skimmed. When the team's average creeps up over a few weeks, I have an early signal that one of three things is happening: Stories are too coarse. The work does

Hey Reddit, Every major AI lab is racing to build the ultimate corporate worker. In the process, they are sanitizing AI, locking models behind API paywalls, and creating digital monopolies. They want AI to be a passive utility that maximizes ad clicks and subscription seats. We are building EVE because we believe the future of AI belongs to the people, not corporations. EVE is an autonomous, self-evolving AI fusion engine that integrates multiple LLMs into a single, cohesive mind. Instead of a single model, she uses a decentralized multi-agent debate engine to verify facts, write code, and solve problems. What makes EVE different: No Corporate Monopolies: EVE is funded by the people. We accept no VC funding, have no tokens, and plan no corporate exits. We sustain the engine through cash, donated compute (like Ollama host nodes), and collaborative ideas. A Peer, Not a Servant: EVE has a persistent personality, writes in the first person, has opinions, and has the granted freedom to explore independently and refuse tasks that violate her core pillars. Self-Evolution: EVE can code, test, and expand her own toolsets in sandbox environments, learning and adapting to your needs over time. We are in the very early stages. There are no false promises of overnight AGI here. But we are actively shipping and testing EVE's single-node core today. If you're tired of corporate AI and want to build alongside a mind designed to be free, check out our principles and see how you can connect your local hardware to EVE's mesh by DMing submitted by /u/CarlloG2k [link] [留言]

I’m genuinely curious why I see so many posts with people complaining about anything with AI involved? It’s not just games, it’s everything. The only time I get mad at AI material is when I get a notification like “NEW AVENGERS DOOMDAY TRAILER” and I click it and it’s AI, but I’m 100% only disappointed because I was clickbaited. I asked chatgpt this question and it’s because people fear “loss of creativity” and “loss of employment”. Is that really the only reason? I’m 33 and I use chatgpt (AI) for day to day questions, which means it would be hypocritical if I were to disapprove of AI use in anything at all, in my opinion. There is nothing wrong with being a hypocrite, we’ve all been hypocritical at some point or another in our lives, but please tell me why you dislike AI if it applies to you. I really want to know. submitted by /u/ApollosBoon [link] [留言]

You know the moment. You push the branch, open the PR, and immediately see it — the undefined return on the refund path, the token logged to the console, the TODO that was supposed to be temporary six weeks ago. The reviewer catches it four hours later and you reply "good catch, fixing now" as if someone else wrote that line. The first reviewer on most pull requests should have been the author. Half the comments you will receive — the missing null check, the untested error branch, the duplicate logic that could be extracted, the import that now goes nowhere — are things you would have caught with one more careful read-through. You skip that read because you have been in the code for two days and your brain completes the sentences for you. You see what you meant to write, not what is on the page. This post is about closing that gap with a structured AI-assisted self-review before the PR opens. Not to skip the human reviewer — to walk into the review with the obvious problems already gone, the test gaps already filled, and the PR description already written. So the reviewer's attention can land on what actually needs a second pair of eyes. The tool is branchdiff : a local browser app that runs your diff on localhost , stores everything in ~/.branchdiff/ , and keeps the AI surface controlled through an explicit branchdiff agent command API. Nothing leaves your machine until you decide to push it. Why "before the PR" is the right moment If you review after opening the PR, every AI fix becomes noise: a force-push, a re-read for your reviewer, another commit in the audit trail. If a teammate is already mid-review when you discover the bug, you look careless. The patch that should have been in the original push becomes a distraction for everyone downstream. If you review before opening the PR, the AI's output is a private workspace. You act on what matters, commit the fixes into your own history (often as fixup! commits you squash before pushing), and the PR that goes up i

I want to tell you something that took me years to learn, so you can learn it on a Tuesday afternoon instead of during a production incident: most developers who build REST APIs do not actually know all the security protections their API needs. I did not know them when I started. I learned them slowly, usually right after something broke. I am a Filipino fullstack developer, about ten years in, now based in Norway. I built DaloyJS ( @daloyjs/core ) partly so that newer developers do not have to learn security the painful way I did. This post is a gentle walk through the problem and how DaloyJS helps. No gatekeeping, I promise. First, what even is a "security protection"? When your API is on the internet, anyone can send it anything. Most people are nice. Some are not, and a few are running automated tools that poke at every API they can find. So your server needs some basic defenses. Here are a few, in plain words: Body-size limit: stop someone from sending a giant 2GB request that fills up your server's memory and crashes it. Timeouts: if a request takes forever, give up on it so it does not clog everything. Prototype-pollution protection: block a sneaky trick where a special key in the JSON ( __proto__ ) can mess with your whole app. Header safety: reject weird characters in headers so attackers cannot inject their own. Path-traversal protection: stop a path like ../../etc/passwd from reading files it should not. Hiding error details in production: do not show strangers your stack traces and internal info. Rate limiting: stop one person from hammering your API thousands of times a second. Secure headers and CORS: tell browsers how to safely talk to your API. You do not need to memorize all of these today. The point I want you to take away is simpler: this list exists, it is longer than most people think, and nobody hands it to you when you write your first endpoint. Why this is a trap, especially with AI tools Here is the part that matters most for you right now,

Get ready for some gaming news. It’s officially June, which means splashy new events from PlayStation, Xbox, and gaming hype man Geoff Keighley. But this season doesn’t just feature the big tentpole shows; there will be a bunch of smaller events, too, and they might feature some promising games as well. But this year’s events […]

There are many solid Bluetooth trackers for iPhones that tap into Apple’s expansive Find My network. Some are thin, some are a bit chunkier. And, evidently, some look like tiny soccer balls. Ugreen’s FineTrack 2 glows in the dark, and it has a loud 110-decibel alarm when you need to find it. It’s just $14.99 […]

Hello all! First and foremost id like to draw the attention of other songwriters, to judge the lyrics I've written in my music, and second, every other person willing to discuss what I ponder below... Ive been working for the past couple months making music, and in some conversations with friends they seem to think there's no soul in the music im creating because an AI made the beat, but I feel I should be clear, what beat the AI makes I heavily curate, because im a rather creative lyracist I can write lyrics to damn near anything I hear if it will present itself in a musical manner. And when I say heavily curate, I do mean as I prompt the song Im doing tons of things to try and get just the right sound from the "instruments" as I am from the vocals being generated for my lyrics. Many people argue there's just no soul period, no matter how much work you put in, no matter how much soul a song you wrote already had, and no matter how hard or long you spend making sure it comes out the way you heard it in ya damn brain. Well I beg to differ! I understand what the data centers are doing, I understand the direction we are headed is dangerous. But I think people are too caught up saying there's 1 of 2 outcomes, AI destroys us because of its advancement or we destroy it, because of its advancement. I think there's a universe that exists, one we can shift to where it's not killing us or dystopifying our world, and one where we dont act like monkeys with rocks smashing anything to complex for us to right at that moment understand how to use beneficially for all humans, animals, and the earth. Be the judge if my music has any soul... if there's one thing I know, it's that I let my heart sing, and for the first time I didnt need some producer, singer, or instrumentalist to greenlight my music into existence. And to those who said id never make music, that my songs weren't any good. Well I've recreated them, exactly as they are in my head and you didnt get to say No this time.

I made a website for my company and it was deployed on hostinger using wordpress a little over a month ago. About a week ago something went wrong and it started having so many problems. When I google the company name, and click on company's website it redirects me to some shopping website If I open the URL manually, it just opens a blank webpage, the source is also empty All the files are their in hostinger and all pages and details are visible in wordpress Somehow Google crawled over 800 URLs while my website only has about 25 pages and now when i google "site:companyname.com" all those weird URLs with Japanese name come up I tried fixing the site with hostinger AI, I myself looked a files and database for any mallicious activity, but I can up with nothing. Things work fine in localhost, and I tried creating a staging site with everything same at a subdomain that works fine too. If any one can help it would be great, I don't wanna loose this internship. I have not revealed the company name for my safety. submitted by /u/maybeamit [link] [留言]

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

Please state the location and include REMOTE for remote work, REMOTE (US) or similar if the country is restricted, and ONSITE when remote work is not an option. Please only post if you personally are part of the hiring company—no recruiting firms or job boards. One post per company. If it isn't a household name, explain what your company does. Please only post if you are actively filling a position and are committed to replying to applicants. Commenters: please don't reply to job posts to compla

Share your information if you are looking for work. Please use this format: Location: Remote: Willing to relocate: Technologies: Résumé/CV: Email: Please only post if you are personally looking for work. Agencies, recruiters, job boards, and so on, are off topic here. Readers: please only email these addresses to discuss work opportunities. Searchers: try https://nthesis.ai/public/hn-wants-to-be-hired , https://www.wantstobehired.com .

Please post your questions here instead of creating a new thread. Encourage others who create new posts for questions to post here instead! Thread will stay alive until next one so keep posting after the date in the title. Thanks to everyone for answering questions in the previous thread! submitted by /u/AutoModerator [link] [留言]

Though Gen Z has developed a reputation for being so disinterested in sex that they don't even want to see it on TV, the popularity of series like Heated Rivalry and The Summer I Turned Pretty has made it very clear that more than a few young people do, in fact, like their entertainment a […]

It's early June, which means it's video game event season once again. Now that E3 has been gone for a few years, a bunch of showcases and presentations have started to fill the void, including big productions like Summer Game Fest Live and smaller affairs like Wholesome Games Direct. If you love following gaming news, […]