1作者: svenmalvik4 个月前原帖
Stillness quiets the noise, clarity arrives; it reveals what you already know. And what you know shapes what becomes.<p>“It’s done” is the feeling of knowing—before the world catches up.
2作者: PEGHIN4 个月前原帖
My agency was bleeding $1,800&#x2F;year on contractor Notion seats. The problem: I needed to give contractors access to specific data (CRM, project tracker) but couldn&#x27;t let them see pricing, margins, or other clients&#x27; information.<p>Notion&#x27;s native solution doesn&#x27;t work:<p>Row-level filtering exists but it&#x27;s view-only (contractors can&#x27;t edit)<p>Column hiding doesn&#x27;t exist<p>Guest sharing is read-only<p>So you either pay $15&#x2F;mo per seat or duplicate databases (maintenance nightmare)<p>I built a permissions layer using Notion&#x27;s OAuth API. It lets contractors see only specific rows and columns, edit data, all without expensive seats.<p>How it works:<p>Connect Notion via OAuth<p>Define roles: &quot;Sales reps see only leads where owner = them, hide pricing column&quot;<p>Contractors access a clean portal<p>They view&#x2F;edit data in real-time (syncs every 5 minutes)<p>You pay $59&#x2F;mo flat for unlimited users<p>The math:<p>5 contractors × $15&#x2F;mo = $900&#x2F;year wasted<p>20 contractors × $15&#x2F;mo = $3,600&#x2F;year wasted<p>50 contractors × $15&#x2F;mo = $9,000&#x2F;year wasted<p>With this: all of them = $59&#x2F;mo flat.<p>Technical:<p>Frontend: React + TypeScript<p>Backend: Supabase + PostgreSQL (RLS)<p>Auth: Notion OAuth 2.0<p>Current state: 50 beta testers. First 20 customers get $49&#x2F;month locked-in (launching at $79 after January).<p>Limitations:<p>Only Notion databases (not pages)<p>5-minute sync (not instant)<p>Requires role definition<p>No team permissions yet (roadmap)<p>The ask: If this solves a problem you have, we&#x27;d love feedback. Are there permission use cases we&#x27;re missing? What&#x27;s your price sensitivity?<p>Free trial: notionportals.com
1作者: Rooster614 个月前原帖
First off, this thread is NOT a petition to rally against the moderation team. Considering the deluge of trash they deal with every day, I think they are doing a valiant job and are to be commended.<p>That said, its becoming more and more obvious every day that there is a tremendous amount of attempts by bots, and specifically AI agents, bombarding HN every day. I worry about the integrity of the discourse here and if the ever growing wave of slop will overtake staff resources to deal with it. Is it time to implement captcha for HN? If so, should it be out of the box, or a new mechanism more tailored to the security and privacy-centric nature of the HN readership?