Forums latest activity | Product Hunt

Brands use employees’ social networks as influencers. But what do employees get out of it?

Joao Seabra:@arun_tamang Exactly right. The standardisation kills the thing that made it valuable in the first place. Audiences follow people, not brand guidelines. The moment an employee's content starts sounding like a press release, the trust evaporates and you've lost both the authenticity and the reach you were trying to capture.

What was the very first project you vibecoded with AI?

Isaias Solaeche:@busmark_w_nika To be honest, I'm still surprised by how well the product is doing! I’ve already managed to secure my first sales, and the best part is that it’s working almost semi-automatically now, generating some passive income while I keep learning. Since I started this with zero coding knowledge, I’m always afraid of breaking things, so I’ve learned to be very careful. I try to make only tiny, surgical changes instead of letting the AI rewrite everything at once. Whenever I get stuck or one model doesn’t 'get' me, I just switch to another one like DeepSeek or Claude for a second opinion. It’s been a huge challenge, but debugging those little mistakes is actually how I’m finally starting to understand how it all fits together. Just migrated to Supabase for our v2 next month, and I’m just taking it one step at a time!

I built something to solve my problem, maybe it helps you too

M O E I N:https://hamzaban.xyz

How much do you trust AI agents?

Abhay Donde:@busmark_w_nika You seem like someone who has interesting thoughts.. should I be curious or concerned??

How much do you trust AI agents?

Abhay Donde:@busmark_w_nika Exactly… the real skill is knowing where to draw the line 😉

How are you managing Supabase credentials across environments without things drifting?

Matteo Avalle:@eric_nodeops I genuinely feel like it has the potential to get there, but it is indeed tricky. Even here we haven't really addressed ALL the issues key rotation brings - mostly due to our setup, as we leverage frontend-supabase interactions for authentication, but then everything happens through a backend layer in the middle, that pushes the problem to the backend. In general, I'd say that trying to make sure frontend "keeps up" with the hardening processes on backend side is overall a very complex process REGARDLESS on your size, mostly because it's kind of a new thing: frontend keys are literally "publicly available, compromised by default" keys, so nobody ever felt the need to change them often, before Supabase became popular. This is because it's both a painful devops problem, but also an even more painful frontend problem: let's assume you find a way to change your keys easily, but can you also force people to refresh their pages in real time, anytime you apply a change? Also, what happens to your JWT tokens, the moment keys change? Will you still recognize the old ones, or are you kicking people out at every rotation? Being a "modern" problem, the support for it is kind of limited so in my company we tried to avoid having to reinvent the wheel once again, and tie this issue to our more common "multi tenant" scaling problem: we have loads of subdomains, one per specific customer, and we'd really love to avoid having to keep a lot of different frontend builds just for that, considering the codebase is always the same, and the UX changes are just driven through a configuration envfile. So we replaced the .env with the json, as our own way to deal with that: we got a single frontend container image, and the only difference between the various instances is indeed the mounted json file. This made our multi tenant policies easier to scale, while also making key rotation quite doable. But still, caching and JWT tokens are the outstanding problems you should solve if you are using supa more directly: you may be forced to re-download that very same JSON configuration file at every API call or so, to be sure you always have the latest keys

How do you decide what features should be free and what should be paid?

Wambugu Gichuki:@busmark_w_nika just checked the translation, wow, I guess I'll have to change the name when I make it available there :D . I hope the slovak word for picture isnt a mouthful

Brands use employees’ social networks as influencers. But what do employees get out of it?

Arun Tamang:@busmark_w_nika Paying someone to create content is a cost on the company side, but the channel still belongs to the employee. The value comes from the trust and audience attached to that profile, not just the content itself. So even if the company invests in content, it doesn’t really balance out if they’re also relying on that existing trust for distribution.

What design skill should our agent learn next?

Mu Li:@mikita_aliaksandrovich Thanks for raising this, Mikita! Yeah, this is a big one. “generate UI” vs “make it feel like the same product”. That gap is very real. That’s exactly where things get much harder (and more useful). Curious how you’re handling that today on your side?

How do you decide what features should be free and what should be paid?

Calin Rasniceru:For me the line is blurry and I don't think there's a clean answer. The mental model I keep coming back to is: free should create/show the problem, paid should solve it. For content/services like yours, free builds the belief and generates the trust that you can help. Paid is the actual help. You're not giving away too much as long as the free stuff makes people want the paid service more, not less. When I build products I take a similar approach, FREE should be generous enough that users get real value and trust the product, but the moment they want to go deeper, faster, or at scale, that's where paid comes in play.