Show HN：我搭建了一个公开征求同意的喜剧吐槽平台
1 分•作者: RoastFeast•6 个月前
嗨，HN，
我作为一名独立开发者创建了Roast Feast，旨在解决一种文化痛点：我喜欢吐槽大会的喜剧效果，但讨厌线上“嘲讽”的恶意和缺乏同意。这是一个让愿意参与的人们重拾吐槽乐趣的平台。
核心是双方同意的、有结构的幽默：
```
验证同意：要主持吐槽，你需要上传一张手持“Feast!”标语的照片。没有意外。
私密 & 安全：创建仅限邀请的、未公开的活动，供朋友、同事或社区使用。平台会分配昵称（形容词+名词），以防止冒充。
技术栈：Nuxt 3 (SSR), Supabase (Auth/DB/Realtime), Vuetify。我甚至编写了一个自定义的PostgreSQL函数，以在数据库级别强制执行昵称格式。
```
我将通过成为第一个被吐槽的对象来启动（我的“Feast!”标语已经上传）。
我很乐意收到你们的反馈，特别是关于：
```
同意验证流程——感觉清晰还是带来了不必要的阻力？
平台界面
```
还有一个更广泛的问题：你认为像这样的、有结构的、双方同意的幽默平台有未来吗？还是混乱的嘲讽将成为线上的永久规范？
来试试吐槽或创建你自己的吐槽：[https://roastfeast.com](https://roastfeast.com)
查看原文
Hi HN,<p>I built Roast Feast as a solo dev project to solve a cultural itch: I love the comedy of roasts but hate how online "dunks" are mean-spirited and lack consent. This is a space to bring back the fun of roasting among willing participants.<p>The core is consensual, structured humor:<p><pre><code> Verified Consent: To host a roast, you upload a photo holding a "Feast!" sign. No surprises.
Private & Safe: Create unlisted, invite-only events for friends, coworkers, or communities. Nicknames are platform-assigned (Adjective+Noun) to prevent impersonation.
Tech Stack: Nuxt 3 (SSR), Supabase (Auth/DB/Realtime), Vuetify. I even wrote a custom PostgreSQL function to enforce the nickname format at the database level.
</code></pre>
I'm launching by being the first roast target (my "Feast!" sign is already up).<p>I'd love your feedback, especially on:<p><pre><code> The consent verification flow – does it feel clear or like unnecessary friction?
The platform interface
</code></pre>
And a broader question: Do you think structured, consensual humor platforms like this have a future, or is the chaotic dunk the permanent norm online?<p>Try a roast or start your own: <a href="https://roastfeast.com" rel="nofollow">https://roastfeast.com</a>