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] [留言]

If you've spent any time building React Native apps, you've already bumped into the question. You're setting up a new project, you need to move users between screens, and suddenly you're 40 minutes deep in a documentation rabbit hole wondering whether to go with the familiar React Navigation setup or take the leap to Expo Router. This article is going to break it all down, no hype, no fanboy energy, just an honest look at both options so you can make the call that actually fits your project. First, What Does "Routing" Even Mean in a Mobile App? On the web, routing is pretty intuitive. You type a URL, the browser goes to a page. Simple. In mobile apps, there's no URL bar, no browser history button, nothing like that. But users still need to move between screens, go back to where they came from, open modals, tab between sections, and all of that has to feel smooth and natural. So in mobile development, routing is basically the system you use to manage how screens stack on top of each other, how state is preserved when you go back, how deep links work, and how the app knows which screen to show based on where the user is in the flow. Think of it like this: routing is "moving between screens while keeping your app's memory intact." When someone logs in, fills out a form, gets distracted and opens a modal, then comes back, the app should remember all of that. Routing is the machinery underneath that makes it happen. In React Native, this doesn't come out of the box. The framework gives you the building blocks, but you have to wire up the navigation yourself. That's where libraries come in. Why Navigation Is Such a Big Deal in React Native React Native apps are essentially single-page applications. Everything runs in one JavaScript thread, rendered to native views. There's no browser doing the heavy lifting of managing history or transitions. You're responsible for it all. Bad navigation kills good apps. A janky transition, a broken back button, a modal that doesn't dismi

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.

Atari's buying the maker of the Crossy Road games.

Malaysia's under-16 social media ban has taken effect.

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 […]