1 karma · joined December 11, 2019
We are using Simulcast for the video tracks. Since a 'Chef' (Buyer) might have 5 freelancers in a room sharing screens simultaneously, bandwidth was a massive bottleneck in early testing.
We configured the LiveKit room to dynamically downgrade the video resolution of the 4 'passive' screens while keeping the 'active' focused screen in 1080p.
Also, regarding the 'surveillance' aspect: I know this is controversial. The goal isn't to watch someone work for 8 hours a day. It's designed for 15-30 minute sprints to verify skill before offering a longer contract. Think of it like a pair-programming interview, but paid.
*Variable rates*: Love this idea. Right now it's flat $72/hr, but you're right – a junior dev shouldn't charge the same as a senior architect. Thinking through implementation:
Option A: Participants set their own rate ($30-$200/hr range?) - Pro: Market finds equilibrium - Con: Chefs don't know cost upfront (pre-auth becomes tricky)
Option B: Skill tiers (Junior $45/hr, Mid $72/hr, Senior $120/hr) - Pro: Predictable pricing for chefs - Con: Who decides the tier?
Leaning toward Option A with a visible rate display before participants join. What do you think?
*Quality & reputation*: Totally agree – even Google/Meta make bad hires sometimes. Your "let it sort itself out" approach makes sense. I'm thinking:
- Public profile showing: total earnings, # sessions, avg session length - No ratings initially (avoids gaming/fake reviews) - Let the market decide: if someone consistently gets kicked or has 2-min sessions, that's a signal
The earnings transparency might be enough – someone with $10k earned across 200 sessions is probably legit.
*Room matching with AI*: This is brilliant and solves the discovery problem elegantly. Currently participants just see a list of open rooms. Your idea:
1. Freelancer creates profile: "React expert, 5 yrs exp, good at performance optimization" 2. Chef creates room: "Need help with Redux state management causing re-renders" 3. AI matches and notifies relevant freelancers: "New room matches your skills"
This could use semantic search (embeddings) to match "Redux performance" to "state management optimization" even if terms don't overlap exactly.
Quick prototype question: Should I prioritize variable rates or AI matching first? Which would have more immediate impact?
Thanks again – this is exactly the kind of feedback I need.