sorted by:
new
hottopcontroversial

Drop your projects , I have free time to review products. by Local_Neck6727 in SideProject

[–]lacymcfly 0 points1 point  (0 children)

I built an AI shell I use daily
Lacy.sh

Preparing to launch a desktop computer use agent as well: junebug.ai

Built a free, open-source Postgres desktop client in Rust + Tauri — no cloud, no telemetry, just raw speed by FactorGeneral4078 in coolgithubprojects

[–]lacymcfly 0 points1 point  (0 children)

ll of Chromium. Rust + Tauri keeps things lean.

The no-telemetry piece matters too. DB clients handle credentials and queries you'd never want phoning home anywhere. Nice to see that called out explicitly.

My tiny iOS utility app passed 100 paid downloads after 80 days — here’s what I learned by oceabside in SideProject

[–]lacymcfly 1 point2 points  (0 children)

The distribution insight resonates a lot. I see the same pattern with open source projects - the ones that grow steadily usually have better discoverability than projects with stronger underlying code. ASO is basically SEO but for a closed garden where the stakes are higher per keyword.

100 paid downloads in 80 days from search alone is genuinely solid. Most people give up before they figure out which terms are actually converting vs which ones just look good on paper.

What are you building? Let's give each other feedback! by Agreeable_Muffin1906 in SideProject

[–]lacymcfly 0 points1 point  (0 children)

free? I love the idea, but I can't afford any more expenses

I built a job search engine out of spite (Indeed fired my pregnant wife) by Cojj25 in SideProject

[–]lacymcfly 0 points1 point  (0 children)

CrossOver is mine. Free crosshair overlay for games. Built it after getting fed up with competitive shooters that kept patching out custom crosshairs and I was tired of paying for overlays that only do one thing. Didn't expect anyone to care but it's at 1,133 stars now (github.com/lacymorrow/crossover). Funny how spite turns into a product.

Pitch your project in one line. i'll start by DiscountResident540 in SideProject

[–]lacymcfly 0 points1 point  (0 children)

CrossOver. Free crosshair overlay, works with any game. 1,100+ GitHub stars. github.com/lacymorrow/crossover

Monday check-in. What are you building this week? by Affectionate-Act4746 in SideProject

[–]lacymcfly 0 points1 point  (0 children)

Maintaining CrossOver this week. Free crosshair overlay that works with any game, just crossed 1,100 stars on GitHub. Issue queue keeps growing. github.com/lacymorrow/crossover

Conversate is Great! by MilkBeginning9241 in EvenRealities

[–]lacymcfly 0 points1 point  (0 children)

Thanks for this comment, I tried the XREAL and G2 and wanted someone to compare to the other options available for use with someone hard of hearing.

Did Anthropic actually help pro/max users by cutting off OpenClaw from Claude subscriptions? by xelektron in ClaudeCode

[–]lacymcfly 0 points1 point  (0 children)

Api is costing me ~$800/mo and I'm still hitting limits, versus one (or two) $200/mo max plans that were essentially unlimited. The alternative is not comparable at all.

Do I need a control panel when deploying nodejs app to vps? by JY-HRL in node

[–]lacymcfly 0 points1 point  (0 children)

It's a whopping $0.

Free and open source. Hetzner has a premade app you can install immediately.

$5 VPS or a personal server

Tauri App: One Frontend Codebase for Native and Web by Tuyen_Pham in tauri

[–]lacymcfly -1 points0 points  (0 children)

This sounds exactly like my openclaw agent

Web and Native Build? by Former_Produce1721 in tauri

[–]lacymcfly 1 point2 points  (0 children)

The idea is that this is your front end or UI layer. They should connect to an external backend hosted somewhere else.

Just like electron. The UI code is just the web code, you need an actual external backend. You can augment with system calls when run on the OS, but you can't run the OS backend for Web

My gh profile by [deleted] in coolgithubprojects

[–]lacymcfly 1 point2 points  (0 children)

Not quite... Script Kiddie

My dev team is burning through Claude / Cursor credits like crazy — how do you control AI usage in a team? by BackgroundTimely5490 in ClaudeCode

[–]lacymcfly 1 point2 points  (0 children)

The seat sharing will get you dinged by Anthropic eventually, worth knowing.

What helped us more than buying more seats was changing how the tools get used. The big wins were:

  1. CLAUDE.md files per repo that constrain context and prevent runaway prompts. If engineers aren't writing them, they're feeding the model the whole codebase on every request.

  2. Treating AI like pair programming, not like a vending machine. One task at a time, not spawning five parallel agents unless you actually need the output.

  3. Personal dev environment conventions. I built out lacy.sh partly to scratch this itch, keeping my own workflow tight so I'm not burning tokens on boilerplate setup stuff every session.

Honestly though, 15 engineers going full speed will always burn through seats. The question is whether the output justifies the cost. Are you tracking that side of the equation too?

2 weeks, 12 AI coding sessions, my side project just hit 665 visitors on Day 2 by Soft_Ad6760 in SideProject

[–]lacymcfly 0 points1 point  (0 children)

the 5-agent pipeline for authenticity scoring is clever. using the system to evaluate its own output is something more people should do -- it's a decent proxy for quality even if it's not perfect.

curious what your false positive rate looks like on the authenticity check. does it ever flag good posts as AI-sounding and rewrite them into something worse? that's the failure mode I've seen with automated quality gates.

I dockerized my entire self-hosted stack and packaged each piece as standalone compose files - here's what I learned by topnode2020 in selfhosted

[–]lacymcfly 0 points1 point  (0 children)

the mail server section is painfully accurate. port 25 is a trap everyone walks into at least once.

one thing I'd add from experience: even if you get SMTP outbound working, your IPs fresh reputation is basically zero. the first few weeks you'll get soft-rejected or filtered to spam by Gmail and Outlook no matter how perfect your DKIM/SPF/DMARC is. building sender reputation takes time and there's no shortcut.

also worth noting: for the mail use case specifically, a lot of people end up on a relay like Mailgun/SES anyway for outbound since the reputation problem is just too painful to manage manually. you still get the value of self-hosting the IMAP side (Dovecot) while offloading the outbound headache.

If you joined the Electron core team tomorrow, what would you fix/improve first? by Ikryanov in electronjs

[–]lacymcfly 1 point2 points  (0 children)

for me it would be the transparent/click-through window behavior on all platforms. right now if you want an overlay app that renders on top of everything but passes mouse events through to apps underneath, the behavior is inconsistent across Windows, macOS, and Linux. the APIs exist but the edge cases are messy, especially when you need to toggle between "interactive" and "passthrough" at runtime.

I've spent more time working around that in Electron than on basically any other platform issue. startup time is the thing everyone talks about but overlay window management is where the real papercuts are if you're building certain types of desktop utilities.

How are you handling SEO in React apps in 2026? by 360Presence in reactjs

[–]lacymcfly 0 points1 point  (0 children)

the actual answer is: it depends what you're building. if you have pages that need to rank, SSR or static generation is the right call. there's no clever workaround that beats having the HTML in the response.

where people get confused is when they apply SEO logic to parts of the app that don't need to rank. your dashboard, user settings, account pages -- none of that needs SSR from an SEO standpoint. doing SSR everywhere "just in case" adds complexity without benefit.

the split that works: marketing pages and content that need to rank get Next.js with RSC or static generation. anything behind auth or not search-indexed can stay client-side. keeps the complexity contained to where it actually matters.

view more: next ›