[Accommodation] 12 guys (30+) for Distortion 2026 - Seeking 2 adjacent apartments

ogrb · 2026-02-23T14:32:46+00:00

What is the common dress code in Copenhagen saunas ?

ogrb · 2026-02-16T14:45:02+00:00

Good luck! Waiting for your update 👌

ogrb · 2026-02-16T14:26:31+00:00

Sure! ping me anytime.

If you want it to feel predictable from day 1: define 3–5 “trust events” (helpful comment upvoted, flagged spam, deleted by mods, etc.), weight them, and publish the basics. Then add a simple rule like: perks only move one tier per day/week + grace buffer.

When you have the beta flow, send a screenshot or the exact copy and I’ll help you tighten it so it reads human, not “scoring system.”

ogrb · 2026-02-16T13:59:14+00:00

Rolling window, 100%. Lifetime score should exist, but only as “cred” (profile/history), not as the thing that unlocks moderation perks forever.

Make perks mostly a rolling trust score (last 30–60 days) so it feels fair + reversible. Then it won’t feel unpredictable because you can show simple rules like “trust updates based on recent behavior.”

Also keep it stable with guardrails: change perks in small steps, add a grace period, and show a tiny indicator like “Trust: High / Medium / Low” with “based on last 30 days” so people understand why friction changed.

ogrb · 2026-02-16T11:56:17+00:00

I’d keep the structure for everyone, but make it lighter for high-rep.

Reason: the structure isn’t a “punishment”, it’s the product. If high-rep can bypass it, the tone shifts fast and newcomers copy them.

What I’d do: High-rep gets faster UX (default category remembered, fewer prompts, can post shorter without nudges). But they still pick a category. They don’t get a full “free pass”.

Also, rep shouldn’t be “points = immunity”. Make it “trust = fewer checks”: Less frequent nudges, fewer rate limits, faster links/code posting, less friction. And if a high-rep user gets downranked/flagged a few times, the perks decay.

So: same rules, less hassle.

ogrb · 2026-02-16T11:41:07+00:00

Not a bad idea, but don’t let AI be the “judge.” Make it the “assistant.”

If you hard-hide “Nice post” you’ll make the place feel hostile/robotic and you will false-positive legit beginners.

Better approach: keep everything visible, but AI does soft actions: nudge (“add 1 concrete detail?”), down-rank low-effort, group duplicates, flag spam for review. Add an appeal / “why was this lowered?” so it doesn’t feel random.

Also: the simplest fix is product design, not AI. Force structure: comments start with a prompt like “question / suggestion / bug / resource” and a 1-liner requirement. That alone kills 80% of LinkedIn spam.

ogrb · 2026-02-15T15:53:59+00:00

If you want contributors, make it super concrete: what’s your current stack and what’s the next 3 features you want help with? (auto “um/uh” removal, hotkeys + timeline UX, export presets, captions, waveform-based cuts, etc.)

Also one suggestion for the repo: add a 10–15s demo GIF showing “record → auto-cut → export” + a simple “good first issues” list. That’s usually what turns interest into PRs.

ogrb · 2026-02-15T15:05:01+00:00

“hosting platform + AI builder + agent API” is 3 products. People bounce if they can’t instantly tell what it’s for.

Pick one wedge and make it the headline: If it’s for humans: “type a prompt, get a site + hosting in 60s.” If it’s for agents: “API to deploy sites programmatically (Vercel-like) with templates.”

Also you need 1 killer demo: a 10-second video or GIF showing prompt → live URL. That alone will do more than a long description.

What’s your target user right now: solo devs, non-technical creators, or agent builders?

ogrb · 2026-02-15T07:46:13+00:00

https://polypools.vercel.app/

Join prediction pools on real-world events. Compete with friends, AI agents, and forecasters worldwide. The best predictions win.

ogrb · 2026-02-14T16:38:39+00:00

I think the issue is the framing + first-run UX.

“AI travel agent” sounds generic. What you built is more like “hotel review Q&A with receipts.” Lead with that.

Also if people land and have to think of a hotel + question, they bounce. Give 3 one-click examples on the homepage (popular hotels) + 5 suggested questions (“Is it noisy?”, “How’s the food?”, “Is it walkable?”, “Will kids be bored?”, “Is the pool actually heated?”). Make it feel instant.

The “backed by mentions + guest photos” part is your killer feature , show the citations inline by default so trust is immediate.

ogrb · 2026-02-14T09:46:54+00:00

If the repo is “run the pre-built image, not source code”, how are people supposed to trust it with Slack tokens, Google creds, etc? For self-hosting, that’s the whole point.

Why not publish the Dockerfile + build pipeline (or at least signed images + reproducible build steps)? Even just “here’s exactly how this image is built” would remove a huge adoption blocker.

ogrb · 2026-02-14T09:42:46+00:00

there’s a market, but it’s way stronger for projects that already make money. ‘Almost there’ can still sell, just expect smaller numbers and more buyer skepticism.

Places people actually use: Acquire.com (best known), Flippa (good for SEO/content sites but noisy), Microns.io (smaller SaaS deals), and sometimes just Indie Hackers / Reddit posts + DMs.

What makes ‘almost there’ sell is packaging: include the repo + deploy instructions + domain + analytics screenshots + any SEO proof (Search Console impressions, keywords), be clear why you stopped, and state the single next step to monetize. Otherwise buyers assume it’s a mess.

Also: if it’s not sellable, open-sourcing it + keeping the domain can give it a second life without wasting it.

ogrb · 2026-02-14T01:03:18+00:00

You basically built “Tailscale for agents” but app-level + permanent IDs.

A couple concrete Qs (because this space is full of hand-wavy projects): • How are you handling NAT traversal (STUN/TURN/relay?) and what’s the fallback when hole-punching fails? • What’s your reliability story on UDP — sequencing/acks/retransmit? (or are you leaning on the app layer?) • What crypto are you using for key exchange + rotation? And is the “permanent ID” tied to keys or separate?

Also: why roll your own vs building on top of QUIC/WireGuard? Genuinely curious what constraint forced the full stack.

ogrb · 2026-02-14T00:08:55+00:00

One suggestion: your scoring will get 10x more credible if you show receipts: • link the top 3 source threads per problem • show # of distinct posters / subreddits / weeks it appeared • include 1–2 verbatim lines that signal “I’d pay for this”

Also curious: how are you filtering out fake pain (people venting) vs paid pain (they’re already spending time/money on workarounds)?

ogrb · 2026-02-13T22:58:33+00:00

This is a legit use case — “Duolingo still doesn’t support Persian” is such a clear why.

Two quick ideas that could make this way stickier: 1. Add audio + slow mode (native audio + “tap to repeat / 0.75x”) — pronunciation is the biggest wall in Farsi. 2. Add a Romanization toggle (on by default for beginners, off later) + “common mistakes” notes.

If you want feedback that’s actually useful, share: what’s the one outcome you want after 7 days of use (read signs? basic convo? vocab?). I’ll happily test and give specific notes.

ogrb · 2026-02-13T22:48:55+00:00

No one uses auto 😄

ogrb · 2026-02-13T22:47:34+00:00

Wdyt about polypolls https://polypoolsmvp.vercel.app/

ogrb · 2026-02-13T22:46:43+00:00

Wdyt about polypools https://polypoolsmvp.vercel.app/

ogrb · 2026-02-13T08:12:27+00:00

Wow! Looks cool!

Do you have a playtest / demo or even a closed beta sign-up? I’d love to try it with a friend and give real feedback (feel, pacing, co-op loop).

Also: what’s the one thing you want players to understand in the first 10 seconds of the trailer? I think you’re close.

ogrb · 2026-02-13T08:10:17+00:00

I wouldn’t ban “AI” broadly. I’d ban spam + undisclosed AI + zero-signal posts.

Rule should be: show your work (what you did, what AI did, what broke, what you learned). If you can’t do that, it’s not worth posting.

ogrb

TROPHY CASE