Postingan

Show HN: Crawlee Cloud Self-hosted platform for running Crawlee and Apify actor https://ift.tt/XOejHfb

Show HN: Crawlee Cloud Self-hosted platform for running Crawlee and Apify actor Hey HN, I built Crawlee Cloud, an open-source, self-hosted platform that lets you run Crawlee and Apify Actors on your own infrastructure. The problem: The Apify ecosystem (Crawlee, SDK, Actors) is fantastic for web scraping, but it's tied to their cloud. If you want to keep your data on-prem, run on your own servers, or save on costs at scale, you're stuck. The solution: Crawlee Cloud implements Apify's REST API so your existing Actors work without code changes. Just point APIFY_API_BASE_URL to your own server. What's included: SDK compatible: Datasets, Key-Value Stores, Request Queues all work Docker-based: Each Actor runs in an isolated container Dashboard: Monitor runs, explore datasets, manage Actors CLI: Push, run, and manage Actors from your terminal Stack: Node.js, Fastify, PostgreSQL, Redis, S3/MinIO, Next.js GitHub: https://ift.tt/JRtKbHo Happy to answer questions! https://crawlee....

Show HN: Buoy – A persistent, status-bar web server for local utilities https://ift.tt/fcNRh6g

Show HN: Buoy – A persistent, status-bar web server for local utilities I’m constantly building small web-based tools for my own use. Usually, my workflow ends with a dilemma: do I keep a terminal tab open forever running `npx http-server -p 8080`, or do I spend time configuring a Caddyfile for a 50-line HTML tool? Nothing felt right. I wanted something that felt like a native, always-on, utility that was easily accessible but invisible. I built Buoy. It’s a minimal server that: Lives in the status bar: I can see that it's running at a glance without hunting through ps aux. Is persistent by default: It starts with macOS and keeps my utilities alive in the background. Zero-config: It points at a XDG‑Standard www folder so I can create a symlink and be done. Small: I wanted to avoid the modern bloat. Buoy is a single, self-contained binary that's under 10MB. It’s a minimal tool that lets me build many small things and move on to the next. https://ift.tt/Bq8OpSL December 25, 2025 ...

Show HN: nunchux – A handy tmux launcher buddy thing https://ift.tt/Ey2tmbv

Show HN: nunchux – A handy tmux launcher buddy thing Had some fun over the christmas holidays and nunchux is the output. A fun menu for tmux to reduce the number of apps I need to remember the name for. Also a nice quick way to browse hacker news via hackernews_tui :-) https://ift.tt/JT7IO2f December 26, 2025 at 12:18AM

Show HN: I treated my brain like a buggy server and wrote a patch (Shi-Mo Model) https://ift.tt/uADgRtJ

Show HN: I treated my brain like a buggy server and wrote a patch (Shi-Mo Model) https://ift.tt/wRCTacd December 25, 2025 at 11:55PM

Show HN: Why many AI-generated websites don't show up on Google https://ift.tt/sVpwj96

Show HN: Why many AI-generated websites don't show up on Google We’ve been experimenting quite a bit with AI website builders and kept seeing the same pattern: Sites often look finished to users — modern UI, fast loads, everything appears “done” — but when search engines crawl them, much of the main content isn’t actually present yet. In many cases the issue isn’t SEO basics, keywords, or content quality. It’s simply when the HTML is generated and what Google receives on first visit. We wrote up a calm, non-marketing explanation of what’s going on, how to spot it yourself (even if you’re not very technical), and why this keeps happening with many modern AI builders. We’re also building a tool (Pagesmith) around this problem, but the article stands on its own and should be useful even if you never use our product. Happy to answer questions or be challenged on any of the claims. https://ift.tt/CQYNHT8 December 25, 2025 at 11:39PM

Show HN: Epstein Files and images (4000 .png files) https://ift.tt/jrugEIY

Show HN: Epstein Files and images (4000 .png files) credit to @RhysSullivan on github for creating this https://epstein-files-browser.vercel.app December 25, 2025 at 12:28AM

Show HN: No more writing shitty regexes to police usernames https://ift.tt/5AcseTd

Show HN: No more writing shitty regexes to police usernames Every product that allows usernames eventually ships the same broken solution. Someone adds a blacklist. Then a regex. Then another regex copied from StackOverflow. It works just long enough to ship, and then `admin`, `support`, city names, brand impersonation, and obvious slurs start leaking through anyway. Everyone knows it’s fragile, but it gets ignored because "it’s just usernames". I’ve had to rebuild this logic across multiple products, and I got tired of pretending it’s a solved problem. So I built *username.dev*, an API that answers a more useful question than "is this taken?" — it tells you what a username actually represents. Instead of returning a boolean, the API classifies usernames into real categories like brands, public figures, places, system-reserved terms, dictionary words, premium handles, and offensive content, and returns structured metadata you can actually make decisions with. That m...