Most AI products today are wrappers. Different interfaces. Different branding. Different marketing. But underneath many of them is the same pattern: centralized models, rented intelligence, recurring dependence, and cloud-first control. The user doesn’t own the intelligence. They lease access to it. I think that creates a dangerous future. AI Is Quietly Becoming Infrastructure We’re moving toward a world where AI won’t just help write emails or generate images. It will: operate businesses, manage workflows, coordinate logistics, assist with infrastructure, analyze systems, monitor environments, and increasingly act as operational infrastructure. That changes the stakes dramatically. If AI becomes operational infrastructure, then ownership matters. Control matters. Resilience matters. And right now, most users have very little of any of those things. The Problem With Generalized Intelligence One of the biggest issues I see in modern GenAI is overgeneralization. We’re trying to build one giant intelligence that does everything: coding, marketing, legal reasoning, architecture, writing, support, psychology, operations, and research. The results can be impressive. But also unreliable. Hallucinations happen because the systems are stretched across too many domains simultaneously. The broader the intelligence becomes, the harder consistency becomes. That’s why I’ve become increasingly interested in specialized AI systems. AI Should Work Like A Workforce Instead of one giant model pretending to know everything, I believe AI should operate more like a coordinated workforce. Specialized agents. Focused responsibilities. Defined operational boundaries. For example: a development agent, an infrastructure agent, a security agent, a documentation agent, a research agent, a support agent, a creative writing agent. Each one optimized for a specific domain. Each one independently updateable. Independently replaceable. Independently trainable. Not one brain. Many experts. Local-Firs

While designing the database and Product Requirements Document (PRD) for an online school project, I ran into a problem I was not expecting. The school had multiple subscription plans. For simplicity, imagine: Live Class Plan:₦50,000 per term Video On Demand Plan: ₦30,000 per term Hybrid Plan (Live Classes + Video On Demand):₦70,000 per term. Initially this looked simple. Students subscribe. System charges them. Done. Then I asked: What happens if somebody changes plans halfway through the term? Suppose: A student already paid: Live Class Plan ₦50,000 Two months later: They decide: Upgrade to Hybrid Plan Do we charge: ₦70,000 again? That would be unfair. Do we charge: ₦20,000 difference? Maybe. But what if they already used most of their subscription period? This question led me to something called: Proration What Is Proration? Proration simply means: Charging customers only for the portion they actually use. Instead of pretending subscriptions always begin and end perfectly. Proration tries to answer: "How much value remains in the current subscription?" and "How much should the customer pay for the new one?" Simple Example Assume: Term Length: 100 Days Student buys: Live Plan ₦50,000 After: 40 Days they upgrade. This means: Used: 40 Days Remaining: 60 Days Value remaining: Remaining Value = Remaining Days / Total Days = 60 / 100 = 60% Remaining credit: 60% × ₦50,000 = ₦30,000 Hybrid costs: ₦70,000 Therefore: Amount to bill = New Plan Price − Remaining Credit = ₦70,000 − ₦30,000 = ₦40,000 Student pays: ₦40,000 instead of: ₦70,000 This feels fairer. Downgrades Are More Complicated What if: Hybrid user: ₦70,000 moves to: ₦30,000 plan Should the system: Refund money? Create account credits? Apply discount later? Ignore downgrades until renewal? This is where: Proration Rules become important. What Are Proration Rules? Proration calculations are useless without rules. The business must decide: Rule 1: How Is Remaining Value Calculated? Options: Daily basis Weekly basis

Last time I posted this game the UI looked totally different and the UX was honestly pretty rough. I'm happy with where it's at now, but the colors keep bugging me and I can't tell if it's just me staring at it too long. Quick context on what you're seeing: it's a roguelike where you pick a few technologies and use them to answer quizzes. Combos, multipliers, mods, the usual. The cards in the middle are Strikes, basically quiz minigames, and each one is tied to a tech like React, Next or Postgres. The card's color is how you tell which tech it is, so the palette is doing actual work, not just decoration. The bar at the bottom is the Mods Bar. Mods are one off modifiers you pick up during a run, like the cards in a deckbuilder. So: does it read as too much, or is the color earning its place? Roast it. submitted by /u/mister_pizza22 [link] [留言]

Forms are everywhere in mobile apps - authentication flows, data entry, support requests, onboarding... If your app has a login screen, a form is likely the first thing a new user interacts with. That makes accessibility here not just a nice-to-have, but a first impression. The problem is that forms are consistently one of the most broken areas for assistive technology users. Missing labels, keyboard traps, silent validation errors, focus going nowhere after submission - these are issues that make an app unusable for a significant portion of your users. This guide is a complete reference for building forms that work for everyone in React Native, whether users are navigating with their fingers, an external keyboard, a screen reader or voice input. Code examples throughout show both what to do and why . A fully working demo repo is available to fork and test on a real device - check it out at rn-accessible-form-demo . Labels Every form field needs a label, whether a text input, checkbox or radio/submit buttons. No exceptions. Don't rely on placeholders Placeholder text disappears the moment a user starts typing. Screen readers will read it initially, but once it's gone, there's no way for them to recall what the field was for without clearing their input. Placeholders are useful as hints, not as labels. Use a visual label + accessibilityLabel To avoid screen readers announcing the same information twice (once for the visual label, once for the input), hide the visual label from assistive technology and put the full label on the input itself. < Text importantForAccessibility = "no" accessibilityElementsHidden > Email address* </ Text > < TextInput accessibilityLabel = "Email address, required" /> importantForAccessibility="no" handles Android, and accessibilityElementsHidden handles iOS. Together they tell assistive technology to skip the visual label entirely - the accessibilityLabel on the TextInput is the single source of truth for screen readers. Required fields De

Most web scraping projects are not unique snowflakes. Track competitor prices. Enrich a list of leads. Audit a site for SEO. Pull training data for a model. It is the same handful of recipes, over and over. A web scraping template is one of those recipes, pre-wired: a ready-to-use JSON config that chains the right tools in the right order, so you copy it, point it at your targets, and run. CrawlForge ships 24 of them in the templates gallery . This guide is about using them well — not just copy-paste, but read, adapt, and cost them out before you scale. TL;DR: A CrawlForge template is a copy-paste JSON config that chains multiple MCP tools into one workflow (price monitoring, lead enrichment, SEO audits, market research, AI training data). There are 24 across 9 categories, each costing 3–19 credits per run. Run them from Claude/Cursor, the crawlforge CLI, or the REST API. Free tier = 1,000 credits, no credit card. Table of Contents What Is a Web Scraping Template? Templates Gallery vs the scrape_template Tool How to Use a Template the Right Way 8 Templates Worth Copying First The Other 16 Templates Customizing or Building Your Own FAQ What Is a Web Scraping Template? A template is a saved configuration that orchestrates two or three CrawlForge tools into one workflow with a business outcome attached. Instead of wiring search_web then scrape_structured then analyze_content yourself — and guessing every parameter — you copy a config that already does it. Each template in the gallery carries: A category — E-commerce, Research, Data Collection, Monitoring, AI & LLM, Sales, SEO, Content, or Advanced Scraping (nine in total). A difficulty — beginner, intermediate, or advanced. The tool chain it runs and a fixed credit cost per run (3–19 credits). A copy-paste JSON config with sensible default parameters. You run that config from any MCP client (Claude, Cursor, Windsurf), the crawlforge CLI, or the REST API. Same config, same shape of result. Templates Gallery vs the scrap

This is a submission for the June Solstice Game Jam What I Built Solstice Cipher: Enigma of the Longest Day is a browser-based puzzle game built around the Caesar cipher — the same substitution cipher technique used in ancient cryptography. On the theme of the June Solstice, I tied the longest day of the year to an Enigma Machine-inspired challenge: decode encrypted messages before time runs out, with the difficulty scaling as the sun climbs higher. The game features a real-time animated sky that shifts through dawn, noon, and dusk to reflect the solstice theme. Players are given a cipher shift key and must decode encrypted phrases by working through the Caesar cipher manually or by reasoning out the pattern — no brute-force tools allowed in-game. This connects to the June Solstice theme because the game is literally set on the longest day: the puzzles grow harder as the day progresses, and the sky animation mirrors real solstice light from sunrise to sunset. Video Demo Play it here: gtxpoffic-developer.github.io Code GTXPOFFIC-developer / Solstice-Chiper-Enigma-of-the-Longest-Day This is a Enigma based June Solstice game feel free to include your own code or tinker this project just mention the orignal developers name pls Solstice Cipher — Enigma of the Longest Day A browser-based Enigma machine puzzle game set on the June solstice. Decode (or encode) encrypted transmissions before the daylight runs out. Built By Sudipto — Original developer Feel free to fork, tinker, and include this in your own projects. Just mention the original developer's name. How to Play Objective Configure the Enigma machine correctly to decode each level's ciphertext (or encode the plaintext) before the sun sets. Each wrong guess costs 45 minutes of daylight; correct guesses pause the timer for 30 seconds. Controls Control What it does Rotor dropdowns Select which 3 rotors (I–V) are used ▲ / ▼ buttons Adjust each rotor's starting position Plugboard Drag from one letter to another to connec

A proposed $2 billion data center has become a political flashpoint in the small city of Shelbyville, Indiana. And the controversy has only grown more intense after the mayor, Scott Furgeson, was caught on camera saying of the "No Data Center" signs going up that, "I've seen a lot of these all over town, but […]

Benn Jordan may have initially gained notoriety for his music as Flashbulb and later, reviewing synths and effects pedals on YouTube under Benn and Gear. But about five years ago, Benn decided to take his YouTube channel in a different direction. He didn't stop covering music gear overnight, but as time progressed, his channel became […]

These newer social apps offer alternatives to Big Tech’s feeds, focusing on interests, creativity, and community.

I wanted to do something entirely different than my normal, meet overwatch.earth Explore the world through a fully interactive 3D globe with real-time feeds from over 150,000 sources. Track live events as they happen—from earthquakes and satellite movements to live webcams, global transportation networks, and digital infrastructure. submitted by /u/tuxxin [link] [留言]

82-0 marries the stat nerd fun of fantasy basketball with instant gratification and a bit of dumb luck. The goal is to draft a team of players that could (theoretically) have a perfect 82-0 season. Obviously, if you just had free rein to pick whoever you wanted from throughout history, there would be little challenge. […]

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