标签:#hack
找到 9388 篇相关文章
Man nearly sucked out of window mid-air on Ryanair plane
Ryanair Passenger Sucked Toward Broken Window After Midair Engine Failure
Late Bronze Age Collapse
Show HN: Microcosm Industries – Simulation toys and software microcosms
I’ve been obsessed with simulation toys (software that allows you to play with a complex miniature world) ever since I was young and playing with SimCity and cellular automata. This kind of software exists at the delightful and weird intersection of simulation, complexity science, education, and gaming. And I want more of it! I created Microcosm Industries to initially act as a clearinghouse for simulation toys that are being built, ones that allow the user to playfully grapple with complex syst
Accretive Editing
Unified Memory, Explained: Why Mini PCs Can Run 70B Models a Big GPU Can't
Good Tools Are Invisible
Java 27: What's New?
In Emacs, Everything Looks Like a Service
AI-generated videos to maximally drive a target brain region
Let's build a simple interpreter for APL – part 1
Hackers Use Fake Emergency Requests to Steal Data from Apple, Meta and Others
Paddle rejected my account. Here's the map of what actually works in 2026
Disclosure before anything else: I'm Oded, co-founder of UniPaaS, the FCA-authorised Payment Institution (No. 929994) behind paas.build, and we compete with Paddle. The title above is the sentence builders keep arriving with - right here on dev.to , in Hacker News threads , and in our inbox. This is the map I give them, including the branches where Paddle is still the right call. Why good products get rejected Paddle is a Merchant of Record. The moment it approves you, it becomes the legal seller of everything you sell. So its underwriting answers exactly one question: "do we want to legally own this business's sales?" A brand-new solo builder with no history is the riskiest possible answer to that question, regardless of how good the product is. Builders who have been through it report the same four themes: No prior processing history. The chicken-and-egg: you need a payments track record to get approved, and you need approval to build a track record. An incomplete-looking site. Missing terms, no pricing page, no live domain, no visible product. Reviewers open your site. Identity mismatches. The applying entity, the domain owner and the bank account don't line up. Category restrictions. Paddle has tightened around some generative-AI products. Very little of this is documented, which is why the rejection email feels random. It isn't. It's a business model doing exactly what it was built to do. The decision tree Two questions decide your next move. 1. Is "global tax handled for me" your top requirement? If yes, stay in the MoR category. This is Paddle's genuine strength, and it's a real one: as Merchant of Record it remits VAT/GST across 100+ jurisdictions, and that liability sits with them, not you. No PayFac gives you that. Don't switch categories - fix the application and get back in the queue: Make the site look finished. Live domain, real pricing page, terms of service, privacy policy, a working demo. Explain the business plainly. What you sell, to whom, expecte
How I Built an AI Decision Copilot to Help India Prepare for the 2026 El Niño Crisis
Building an explainable AI platform that helps district administrators allocate resources and farmers make better crop decisions using Gemini, Vertex AI, BigQuery, and Google Cloud. Climate disasters are not just weather events. They are decision problems. When forecasts predict a strong El Niño, governments do not simply need more data. They need answers to questions like: Which districts will be affected first? Where should limited water resources be sent? Which crops are likely to fail? What should farmers sow instead? Why is the AI recommending this action? Existing dashboards provide plenty of charts. Very few provide decisions. That became the motivation behind El Niño 2026 Decision Copilot , an AI-powered decision intelligence platform built during the Google Cloud Gen AI Academy APAC Hackathon . The Problem India depends heavily on the monsoon. A severe El Niño can lead to: Rainfall deficits Reservoir depletion Groundwater stress Crop failures Rising food prices Rural employment challenges The information already exists across dozens of government portals, weather services, satellite datasets, and agricultural reports. The challenge is that it is scattered. District collectors do not have time to manually combine: Weather forecasts NDVI satellite imagery Reservoir levels Mandi prices Contingency plans Drought indicators Farmers face an even bigger challenge. Most need a simple answer: Given my district, should I plant the usual crop this season? The Goal Instead of building another dashboard, I wanted to build an AI system that reasons over multiple data sources and produces explainable recommendations. The platform serves two audiences through the same intelligence engine. District Administrators They receive: District risk scores Interactive risk maps Reservoir outlook Crop stress indicators Resource allocation recommendations AI-generated explanations Instead of simply showing that a district has high risk, the system explains why . Farmers Farmers intera
Publishers Are Preparing to Opt Out of Google Search
China's public QR codes are being hijacked to redirect users to porn and scams
Counting ArXiv Delays
Happy to share I've completed the Cyber Security 101 Path on TryHackMe.
certificate link: https://tryhackme.com/certificate/THM-RLPNFMYL4M My LinkedIn: https://www.linkedin.com/in/ahmedaldiab