Backlog

Next up

In Progress

Done

Main Roadmap

Description of the bug.

**Browser:** Chrome 120
**Extension Version:** 1.0.5
**Steps to Reproduce:**
1. Step 1
2. Step 2

In Review

TEST - Bug Report via API

test

Let a real teammate (manager/peer) co-sign a specific message/thread so a recruiter can trust it at a glance.<h1>Trust model (clear, layered, realistic)</h1>A vouch can have up to three independent signals. Show them as a stack so viewers know what was proven:<ol><li>Identity Verified — endorser logged in with LinkedIn (OIDC).<ul><li>What it proves: “This is a real LinkedIn member.”</li><li>Notes: LinkedIn supports Sign-in with LinkedIn using OpenID Connect; you can get a stable user ID + profile basics after consent. Rich employment data usually needs special approval. </li></ul></li><li>Company Affiliation Verified — endorser proves they worked at <code>&lt;company&gt;</code> (now or previously).<ul><li>Primary method: work-email magic link (e.g., <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="mailto:sam@acme.com">sam@acme.com</a>) → “Company verified” check.</li><li>Alternatives for alumni: upload a redacted offer letter/pay stub (date + company name only), or a second endorser with the same domain (2-endorser rule).</li></ul></li><li>Overlap &amp; Role — endorser attests they worked with you on this (role + dates).<ul><li>You collect: relationship (Manager/Peer/Stakeholder),</li></ul></li></ol><div data-type="horizontalRule"><hr></div><h1>End-to-end flow</h1>A) Author<ol><li>Posts a claim (message) and optional assets in a channel.</li><li>Clicks Request vouch → gets a unique invite link.</li><li>Sends it to a manager/peer (email, DM, LinkedIn message).</li></ol>B) Endorser<ol><li>Opens invite → sees only the claim snippet + any attached artifacts.</li><li>Signs in with LinkedIn (OIDC). (Identity ✓) </li><li>(Optional but powerful) Clicks Verify work email → we send a magic link to <code>@company.com</code>. (Company ✓)</li><li>Selects Relationship + Dates, adds a short note, clicks Confirm. (Overlap ✓)</li></ol>C) Display<ul><li>On the message/thread, show a tiny shield: Vouched ✓✓ (hover → panel).</li><li>Hover panel shows:<ul><li>Endorser avatar, name, title, company, LinkedIn link</li><li>Checks for Identity / Company / Overlap</li><li>Their one-line note &amp; date of vouch</li></ul></li><li>Click → small card with details and a “See LinkedIn profile” link.</li></ul>D) Privacy &amp; control<ul><li>Endorser can revoke any time.</li><li>Authors can hide a vouch (e.g., if it includes sensitive info).</li><li>Viewers see “Private details hidden” when evidence is redacted.</li></ul><div data-type="horizontalRule"><hr></div><h1>UI copy (drop-in)</h1><ul><li>Badge (compact): <code>Co-signed by Sam Lee · ✓ Identity · ✓ Company · ✓ Overlap</code></li><li>Tooltip header: <code>Verified signals</code></li><li>Tooltip items:<ul><li><code>✓ Signed in with LinkedIn</code> (view profile)</li><li><code>✓ Verified @acme.com email</code></li><li><code>✓ Worked with Alex (Manager, 2023–2024)</code></li></ul></li><li>CTA button for authors: <code>Request co-sign</code></li><li>CTA for endorser: <code>Confirm &amp; co-sign</code></li><li>Revocation: <code>Withdraw co-sign</code> (You can remove this at any time.)</li></ul>

Co-sign verification

Jovanny Tovar

Pages are long-form, block-based docs you can:<ul><li>create standalone or attach to a channel or DM,</li><li>reference messages and threads (with deep-links),</li><li>publish public / private / link-only using your existing model,</li><li>auto-announce to a channel with a TL;DR post + deep-link.</li></ul>

Pages (Blog Post)

<ul><li>Promise: “Separate job search / portfolio / founder proof hubs.”<ul><li>great to A/B test portfolios</li></ul></li><li>MVP: Workspace switcher; per-workspace public link.</li></ul>

Multi-Workspaces (you mentioned this)

<ul><li>Promise: “Never lose a half-written post.”</li><li>MVP: Local + server draft; “Resume draft?” toast.</li></ul>

Autosave + Drafts

<ul><li>Promise: “Paste Loom/Figma/GDrive → tidy preview.”</li><li>MVP: Whitelist hosts; oEmbed/thumbnail fallback; no chips or reactions.</li></ul>

Link Preview (Safe Hosts)

<ul><li>Promise: “Visitors can request access; you approve with one click.” Allowing users to start collecting leads/emails</li><li>MVP: CTA → request form → owner inbox.</li></ul>

Access Requests for Private Channels

<ul><li>Promise: “Post faster with a 4-line scaffold (S/T/A/R).”</li><li>MVP: Optional placeholder lines in the composer; one-click “Insert TL;DR.”</li><li>Why users love it: Kills blank-page; matches how people already write.</li></ul>

Guided TL;DR Template

Resume to channel/messages/threads

Give users the ability to archive posts so they can be edited and refined and then published when ready.

Archive posts

Refactor to Next.js 15 and remove Hero UI usage from the app and standardize on shadcn ui with Radix primitives and compact tokens.Goals<ol><li>Replace all Hero UI components in the app with shadcn ui equivalents or headless Radix where needed.</li><li>Keep the current routes and logic intact. Only the UI layer changes.</li><li>Result must feel sleek and compact, not bulky.</li></ol>Tech guardrails • Next.js 15 with React 19 and App Router • Tailwind CSS • shadcn ui primitives: Button, Input, Card, Dialog, DropdownMenu, Label, Tabs, Tooltip, Separator, Skeleton, ScrollArea • Radix where shadcn wraps it • State: React Query for server data, Zustand for local app state • Forms: React Hook Form with ZodDesign tokens for compact feel • Container: center, max width 1100 to 1200 px • Type: h1 text 4xl md 5xl semibold tracking tight, h2 text 2xl md 3xl, body text 15px leading 7, ui meta text sm • Density: default paddings p 4, controls h 9 px 3 text sm • Radius: cards rounded 2xl, controls rounded lg • Borders: hairline border white 10 percent on dark or black 10 percent on light • Motion: transition all duration 150 with subtle scale or translate on hoverAcceptance checklist • No imports from hero ui remain • All primitives come from ui directory that wraps shadcn • The app uses compact controls h 9 px 3 text sm and body text 15px leading 7 • Containers never exceed 1200 px and line length feels readable • Keyboard navigation and focus rings pass WCAG AA • Lighthouse on a typical app view shows performance 95 plus and accessibility 100

Redesign using other library classes

this wil act as the onboarding, and preload “Jovanny Tovar” as the originlal poster, welcoming them, introducing the product and giving some tips.

Create #welcome channel onboarding workflow

Persona-based message editor/composer.

<ul><li>Promise: “Cmd/Ctrl+F across this channel only.”</li><li>MVP: Client-side search by text/has:attachment.</li></ul>

QUICK PING

Main Roadmap