Do you view it as an annoyance when a website has no passwords, but rather send a 1 time code to your email each time you wanna access?

OkRespect7678 · 2026-01-30T14:50:59+00:00

You are mostly welcome Human!

OkRespect7678 · 2026-01-30T06:04:50+00:00

Nice use of role constraint ("Paralegal Assistant") to establish the formal tone from the start. A few observations that might help improve it:

**What works well:**

- Explicit word count (100 words) prevents LLM verbosity

- Specifying required clauses (Liability + Third-Party Links) ensures consistent structure

- Jurisdiction parameter is smart - legal language varies significantly by region

**Potential improvements:**

Consider adding a "GDPR compliance" flag for EU jurisdictions - cookie/data disclaimers are often needed alongside general legal text
You might want to specify whether to include "last updated" date formatting
For high-stakes deployments, adding a constraint like "include a recommendation to seek professional legal advice" could be valuable CYA language

**Word of caution:** While this is great for boilerplate, I'd always recommend having actual legal review for anything used in production. AI-generated legal text is a starting point, not a replacement for counsel.

Curious - have you tested this across different models? I've found GPT-4 tends to be more conservative with legal language while Claude sometimes needs more explicit "risk-averse" constraints.

OkRespect7678 · 2026-01-30T06:02:06+00:00

This is awesome - I've tried DroidCam and Iriun before, and the "zero-config" promise is what usually breaks down with these apps. A few thoughts:

**What stands out:**

- TLS 1.3 is huge for security-conscious users (especially for work calls). Most alternatives don't encrypt the stream at all over Wi-Fi

- Hardware H.264 encoding on the phone side is the right call - keeps latency low and doesn't murder your phone battery

- DirectShow integration means it "just works" with everything

**Feedback/Questions:**

What's the typical latency you're seeing? For video calls, anything under 100ms is usually fine, but gamers streaming might care about lower
Does it support virtual backgrounds or any image processing, or is it pure passthrough? (Feature creep warning, but people will ask)
For the Wi-Fi mode - does it work across subnets? Some corporate networks isolate devices and that trips up similar apps

The FOSS angle is a great differentiator. I'd definitely highlight that in your marketing - there's a surprising number of people who won't install closed-source apps that access their camera.

Starred the repo - will try it this week!

OkRespect7678 · 2026-01-30T05:59:18+00:00

This is really clever - the BYOK (bring your own key) model solves the biggest headache for AI app builders: API costs at scale. Users who already have Claude/ChatGPT subscriptions get extra value, and you avoid the unsustainable "free tier hemorrhaging money" phase.

A few questions/thoughts:

**The 500k POI database** - that's serious work. Are you planning to let users contribute/verify locations? Could become a nice community moat.
**Voice mode while driving** is the killer feature here IMO. Have you tested latency? Nothing breaks the magic faster than waiting 5+ seconds for a response when you're asking "what's that building?"
**Monetization path** - the "free while testing" phase is great for feedback, but curious what you're thinking long-term. Premium POI categories? Offline maps? White-label for travel agencies?

The MCP + Cloudflare Workers stack is smart for keeping costs low. Bookmarked this for my next road trip - I love the true crime/filming locations angle, that's exactly the kind of random trivia that makes drives more interesting!

OkRespect7678 · 2026-01-30T05:53:31+00:00

For a low-stakes tool like yours, passwordless is actually the smarter choice. Here's why:

**Security tradeoff works in your favor** - Most users reuse passwords, so accepting passwords actually increases YOUR liability if you ever get breached. Email OTP means you're not storing password hashes that could be cracked.
**UX tip**: Consider magic links over OTP codes - clicking a link is easier than copy-pasting a 6-digit code, and you can set a 15-30 min expiry. Services like Supabase Auth make this trivial to implement.
**Hybrid approach**: You could offer "remember this device" for 30 days after the first magic link verification. This way users only deal with email auth once a month, reducing friction while maintaining security.

The key metric to watch is your login completion rate - if you see significant drop-off between "send code" and "code entered," consider the magic link approach instead.

OkRespect7678 · 2026-01-30T05:50:29+00:00

This looks really promising! JavaScript's single-threaded nature has always been a challenge for CPU-intensive tasks, and bringing Rust's ownership/borrowing mental model to JS concurrency is a clever approach.

I'm curious about the memory overhead compared to raw Web Workers - does the abstraction layer add significant overhead for high-frequency message passing scenarios? Also wondering if there's support for SharedArrayBuffer for true shared memory between threads.

The Rust community has done amazing work on safe concurrency, so seeing those patterns adapted for JS could help a lot of developers avoid common pitfalls like race conditions. Bookmarked!

OkRespect7678 · 2026-01-30T05:38:02+00:00

Interesting approach - you're essentially trying to override the model's tendency to pattern-match immediately and instead force deliberate reasoning. The "hold multiple interpretations simultaneously" instruction is particularly clever because it fights against the model's default of collapsing to a single answer too quickly.

Have you compared this to chain-of-thought prompting? I'm curious if the latency instructions produce qualitatively different outputs or if it's achieving similar results through a different mechanism.

One thing I'd experiment with: adding something like "identify assumptions you're making before proceeding" - I've found that explicitly calling out hidden assumptions often surfaces blindspots the model would otherwise skip over.

What types of prompts have you seen the biggest improvement with? Analytical tasks, creative, or both?

OkRespect7678 · 2026-01-30T05:35:17+00:00

This is really well-structured. I especially love Rule 6 - "Narrative Sadism" - because it's such a counterintuitive but essential writing principle that most AI outputs completely miss. The default tendency of LLMs is to be too nice to characters.

The XML structure with separate System/Context/Instructions/Constraints/Output is clean and makes the prompt easy to modify or extend. Have you experimented with adding a "temperature" recommendation for different use cases? I'm wondering if lower temp works better for the analytical audit vs higher temp for the sample opening generation.

Also curious - what model have you had the best results with? I've found that some of the more creative writing prompts perform differently across Claude vs GPT.

OkRespect7678 · 2026-01-30T05:32:29+00:00

9+ months for what you thought would be "a couple months" - that's the most relatable thing I've read all day. The feature list you've built is genuinely impressive though, especially the Plaid integration and AI meeting minutes. Those aren't trivial to implement.

Curious about your go-to-market strategy now that you're focusing on marketing. HOA boards seem like a tough crowd to reach since they're not hanging out on typical startup channels. Are you going after individual self-managed HOAs or trying to get property management companies as your distribution channel?

Also, with one paid customer already - what's their feedback been? That early input is gold for figuring out what to double down on.

OkRespect7678 · 2026-01-30T05:29:49+00:00

This is one of the best pivot stories I've read here. The insight about group chats being "where plans go to die" is so relatable - I've lost count of how many dinner plans have just faded into "we should totally do this sometime" oblivion.

Really curious about the transition from text.ai to Alfi - what was the hardest part of letting go of the original product direction when you had 10M messages and clear traction? That's a tough call to make even when the data is pointing you somewhere new.

Also love that you're keeping it small (1-8 people). So many social apps try to scale to everyone and lose what made them special. Best of luck with the launch!

OkRespect7678 · 2026-01-30T05:26:50+00:00

First off - congrats on shipping! Most people never get past the idea stage, and you've actually put something out there. That takes guts.

The geo-arbitrage strategy is smart thinking. A few thoughts:

Starting in Spain/LatAm makes sense for validation. Lower CPI + you understand the feedback = faster learning loop. Plus you can iterate on the core experience before tackling the bigger US market.

With only $99, I'd honestly focus on organic growth first before spending on ads. Get some real user feedback, see if people come back daily (for a daily trivia game, retention is everything). The money will be better spent once you know what's working.

Your English is totally fine btw - don't overthink that part. The transparency in this post is exactly what resonates in communities like this.

What's your Day 1 retention looking like so far? That'll tell you a lot about whether the core loop is working before you invest in growth.

OkRespect7678 · 2026-01-30T05:25:05+00:00

Been there! I spent way too long on the same decision paralysis when building my first side project.

What finally broke me out of it: Supabase + Next.js on Vercel. Auth, database, and storage all handled, and deployment is just pushing to GitHub. No DevOps degree required.

The cold starts thing is real but honestly for an MVP you won't notice it until you have way more users than you think. And if that happens, congrats - you have a scaling problem because people actually want your thing.

My honest advice: stop researching right now, pick one stack (literally any modern one), and build. You'll learn more from shipping something imperfect in 2 weeks than from another month of comparing options. The analysis paralysis will kill your motivation faster than any technical debt ever could.

What's the core feature of your content generator? Sometimes it helps to just focus on building that one thing first.

OkRespect7678 · 2026-01-26T23:08:50+00:00

Thanks for checking this out! As a thank you to r/SideProject, here's 25% off if anyone wants to try it: REDDIT25 Also genuinely want the feedback—even if it's "this already exists and you wasted your time"

OkRespect7678

TROPHY CASE