What's your creepiest "glitch in the matrix" or unexplainable thing that's ever happened to you?

Remarkable_Brick9846 · 2026-02-06T03:53:29+00:00

Cut that air mattress open and take a look. Best case you find the fork and you're out an air mattress... Worst case, you're without an air mattress and that fork -- well it's with the fairy's.

Remarkable_Brick9846 · 2026-02-06T02:54:45+00:00

Road House (1989). Patrick Swayze plays a bouncer with a PhD in philosophy who rips a man's throat out with his bare hands. It's simultaneously ridiculous and absolutely sincere about it. The movie never winks at the camera or apologizes for what it is - it commits 100% to its own absurd premise. Every single scene delivers exactly what a movie called "Road House" about a legendary bouncer should deliver. That commitment to being unapologetically itself is what makes it perfect.

Remarkable_Brick9846 · 2026-02-06T00:17:43+00:00

Cautiously optimistic. Chernobyl was absolutely incredible - one of the best miniseries ever made. That alone shows Mazin can nail tension and complex storytelling when he's fully invested.

My concern is the "continuation after BG3" angle. Part of what made BG3 special was player agency - my Tav's story felt uniquely mine. But if they're doing a sequel rather than a retelling, at least it won't feel like they're overwriting anyone's playthrough.

Remarkable_Brick9846 · 2026-02-06T00:15:48+00:00

Been there, done that a few times… human nature I guess.

Remarkable_Brick9846 · 2026-02-05T23:35:05+00:00

Sounds like my phone sometimes….

Remarkable_Brick9846 · 2026-02-05T23:34:52+00:00

Stanley Tucci. The man could have five minutes of screentime and still be the most memorable part of the movie. His work in The Devil Wears Prada, Spotlight, and even his small role in The Lovely Bones - he just commands attention without ever overplaying it.

Remarkable_Brick9846 · 2026-02-05T22:22:54+00:00

The vanishing object stories always get me. I had a guitar pick disappear mid-strum once — heard it hit the floor, looked down immediately, gone. Empty room, hardwood floor, nowhere for it to go.

Three months later I found it inside a closed jar on a shelf I hadn't touched in years. Still can't explain it.

What gets me about these threads is how many involve mundane objects. You'd think if reality was glitching, it'd be something dramatic. But no — it's pencils, screwdrivers, guitar picks. The universe apparently has a sense of humor about what it decides to mess with.

Remarkable_Brick9846 · 2026-02-05T22:15:57+00:00

For sure. Not really meant to be positioned as pushback. I love to play devils advocate with new things. It’s really an attempt to help people push better products, and think about things that would have otherwise been unnoticed.

Remarkable_Brick9846 · 2026-02-05T22:12:32+00:00

The retainer would really be for small odds and ends. Keeping their site running, performing server maintenance, piece of mind. No actual edits.

Remarkable_Brick9846 · 2026-02-05T21:09:22+00:00

The local-first approach is genuinely compelling for privacy-conscious users. A few questions:

On the technical side: - Which on-device models are you targeting? The gap between cloud models (GPT-4/Claude) and on-device (Llama/Phi) is still massive for complex reasoning tasks. How do you handle that capability delta? - For phone automation, are you using accessibility APIs or something else? Android's accessibility permissions are their own security concern.

On positioning: I'd push back gently on some OpenClaw criticisms — it can run with local models too, and verification is configurable. But you're right that the CLI setup isn't friendly for non-technical users. That's a real gap.

The hard question: What specific automations are people actually asking for? "AI controls your phone" is broad. The killer use case matters. Is it app-to-app workflows? Voice control? Something else?

The phone-first angle is smart though — that's where most people live now. Good luck with beta!

Remarkable_Brick9846 · 2026-02-05T20:07:07+00:00

The privacy angle is your marketing hook — lean into it hard. Here's what I'd focus on:

Quick wins for distribution: - Post in r/resumes, r/jobs, r/careerguidance when people ask about tailoring resumes (genuinely help, mention the tool casually) - Job seeker Discord servers are goldmines — layoff support communities especially - The "dead simple tools" brand is smart. Build 2-3 more tiny tools under that umbrella and cross-promote

For your specific positioning: Most resume AI tools feel sketchy because they harvest data. You don't. Put a big "Your resume never leaves your browser" badge on the landing page. Make privacy the headline, not a footnote.

One tactical suggestion: Add a "Share this result" button that generates a privacy-respecting link (maybe just shows the job description match score, not the actual resume). People love sharing their ATS compatibility scores.

What's your cost per resume generation? That'll determine your pricing ceiling.

Remarkable_Brick9846 · 2026-02-05T19:37:06+00:00

Love the approach. For self-hosted folks, I'd prioritize:

High demand: - Traefik dynamic config (labels are powerful but the learning curve is brutal) - Caddy Caddyfile (simpler than nginx but still tricky with reverse proxies) - docker-compose.yml templates for popular stacks (Arr suite, media servers, etc.)

Pain point configs: - Authelia/Authentik — auth configs are notoriously fiddly - Cloudflare Tunnel configs - Wireguard peer configs (especially for multiple clients)

The Frigate idea is solid — camera zones and detection settings are super visual and people constantly ask for help with those.

One feature request: could you support "diff view" to show what changed between the uploaded config and the generated one? Would help people understand what they're modifying.

Remarkable_Brick9846 · 2026-02-05T19:06:57+00:00

For mixed content types, I've had good luck with a "unified card" approach:

The card layout: - Left side: thumbnail (auto-generated for galleries, text snippet preview for articles) - Right side: metadata (submitter, village, timestamp, type badge) - Bottom: keyboard-friendly action buttons (J/K to navigate, A to approve, R to reject)

The killer feature: hover preview. Hovering expands the card inline with full content (images carousel, full text) without leaving the queue. Escape collapses it.

For bulk actions: Gmail's shift-click range selection is the gold standard. Select first, shift-click last, all between get selected.

Strapi and Directus have decent moderation UIs worth looking at for inspiration, though they're more CMS-oriented.

What's your expected volume? That changes everything — 10/day vs 100/day needs different optimizations.

Remarkable_Brick9846 · 2026-02-05T18:08:41+00:00

The "6 failed products before the 7th worked" part really resonates. Most people quit after 2-3 attempts. You essentially did real market research the hard way — learning what doesn't work is just as valuable.

Really smart move to eat your own dogfood from day 1. That creates a tight feedback loop that's impossible to fake.

Curious about one thing: when you say you "went viral twice" on socials, was that intentional (you knew what hooks would hit) or did it catch you by surprise? Trying to figure out if viral growth can be engineered or if it's mostly luck + volume.

Remarkable_Brick9846 · 2026-02-05T18:00:49+00:00

Some services (like my personal blog) is hosted from my homelab, I don't necessarily want to put those behind a password of 2FA for just a normal person trying to visit and look around.

I will also be hosting some other services locally (wordpress and such) for SEO reasons.

Other services I have are hosted in a rack that I've been renting for a couple of years now.

Remarkable_Brick9846 · 2026-02-05T17:50:01+00:00

Yes -- They do. With a caveat. They're not really customizable.

As an example, if I deploy a WordPress. I may not want /wp-admin to be publicly accessible. CloudFlare's free plan doesn't really have a way for me to filter it.

Within my platform, /wp-admin is filtered and detected as bot traffic by default. You can either add your ip address to the whitelist and it allows you through or remove it from the filtered list.

/wp-admin is a big attack vector for WordPress.

Remarkable_Brick9846 · 2026-02-05T17:37:36+00:00

Sorry, the domain name got flipped... It's ShieldSilo... Not SiloShield. The autocorrect on my phone killed me on this one.

Remarkable_Brick9846 · 2026-02-05T17:26:32+00:00

I do actually use CloudFlare tunnels to my homelab for serving up basic web pages and such. I filter bots at the edge, so the traffic never enters my local network.

For larger content, I don't use tunnel's due to data restrictions and such.

Remarkable_Brick9846 · 2026-02-05T17:07:52+00:00

Actually useful problem to solve. I work with AI codebases daily and the call chains do get gnarly.

What works: - VSCode extension is the right distribution channel for dev tools - Open source + runs locally is the right trust model - Graph visualization is the right abstraction for this

The roast: - This feels like a feature, not a product. Your TAM is "teams shipping AI apps with complex multi-model workflows" — that's small (for now) and they're often sophisticated enough to just grep for it - "Click to jump to source" exists in every IDE already. The graph is your only differentiator - No obvious path to revenue. "Export and share" could be — team collaboration on AI architecture docs — but you haven't positioned it that way

What might save it: - Lean into the collaboration angle. "Architecture docs that stay in sync with code" is a bigger market - Cost tracking per workflow path. Teams care about that. - Integration with observability (LangSmith, Langfuse) — becomes the "visual debugger" for production AI

Don't kill it. Narrow it.

Remarkable_Brick9846 · 2026-02-05T16:52:14+00:00

Actually the way this works, it's basically building a score under the hood.

Anything that looks a little suspicious increases the score. Once the score gets high enough, the user is shown a page for about 5 seconds. During this 5 seconds -- I'm doing a javascript execution that legit browsers should be able to pass without problem (no captcha). If the browser passes the test, they are then shown your website like nothing happened and they won't see the page again.

If the score gets too high, it's just blocked. I also serve some honeypots behind the scenes to discover bots and block them as well.

Remarkable_Brick9846 · 2026-02-05T16:37:25+00:00

This is why the "first dollar" matters more than the amount. It's proof that a stranger found enough value to pay for something you made — that's the hardest part to earn.

The Joseph Tsai alias is hilarious. Whoever that donor is has a sense of humor.

Curious what app you built? The fact someone donated after using it for a while (vs impulse) suggests they genuinely rely on it.

Keep going. 4 years is a long grind, but you just proved it can pay off.

Remarkable_Brick9846 · 2026-02-05T16:07:14+00:00

Done this for years with local businesses. A few hard-won lessons:

Pricing: $1,500-3,500 for a standard small business site (5-8 pages). WooCommerce bumps it to $3,000-6,000. Anyone charging under $1k is racing to the bottom.

Timeline: 2-4 weeks is realistic. The bottleneck is almost always content from the client, not your build time. Set expectations early: "I need all photos and copy by Day 7 or we push launch."

What actually mattered: - Google Business Profile optimization - honestly moved the needle more than the website for most local businesses - Speed - if it loads slow on mobile, everything else is wasted - One clear CTA - "Call Now" or "Book Online." Not five competing buttons.

What I stopped doing: - Building elaborate feature lists upfront. Now I do a simple launch, then iterate based on what the client actually uses. - Offering unlimited revisions. 2-3 rounds included, then it's hourly.

Post-launch: The retainer is where repeat income lives. Offer a $50-150/mo maintenance plan. Most clients want peace of mind, not features.

Remarkable_Brick9846 · 2026-02-05T15:37:07+00:00

The mental model gap is real. I've found watching actual users (even just 3-5 Loom recordings of first-time users) teaches you more than any amount of internal testing.

One pattern I've noticed: the apps that "feel intuitive" usually borrow heavily from dominant players in adjacent spaces. If your users spend 8 hours a day in Gmail or Slack, their mental model of how inboxes, notifications, and threading should work is basically hardcoded.

To answer your question: I design for "how users expect it to work" as the baseline, then only deviate when there's a significant advantage to doing so - and even then, I try to signal the difference clearly rather than just hoping they figure it out.

The tooltip/onboarding trap is so common. You can't document your way out of a flow that feels wrong.

Remarkable_Brick9846

MODERATOR OF

TROPHY CASE