Erazal

Encouraging people to meet up in everyday life and gathering them just to talk is where I’d simply start.

In that spirit I have created and deployed a vibe coded app: come have dinner.com (not the real website).

A simple website we share with my SO to our loved ones, friends, co workers and more. People can register to come have dinner at ours, with an attendance they don’t know.

The website has an admin interface with a simple password, some good jokes, email reminders and calendar invitations.

Should I open source it?

Sorry for the support query here - but I’m blocked in a bus and am HOOKED.

At the moment the prompt just loops for a second and then produces no answer :(

Quick note: it’s hard to pull down the prompt panel down, and makes for a frustrating UX (just there)

I’ve just tested it out, and purchased a subscription within 5 minutes, for an app we were seriously discussing with a friend over the last days.

Keep crushing!

also check out Meeting BaaS (meeting bots as a service), we're an open-source competitor.

We thought long and hard of creating an SDK but did not go that route for now. Our main problem is that if you have to support Windows machines you're putting the finger into something really complicated.

And then depend on the end user's specs, etc.

So I'm really curious, in your case are you planning on deploying to Apple machines (m1+)? Or also set it up on Windows machines?

Creator of MeetingBaaS here (sorry for the double ping), you actually start lower than $1 / hour, rather $0.69 / hour and that scales down quite fast

Unfortunately cloud infrastructure has a cost :/

Hey :)

Creator of MeetingBaas here

We're actually thinking of open-sourcing our bots too!

Been waiting for this day for too long! Welcome back

That’s not something I’d be putting forward either, anywhere. In my opinion, it’s just a way for them to be putting forward their “value,” which actually feels dishonorable.

hey that's pretty cool

Are you using insanely-fast-whisper?

Would be happy to contribute if it were open-source (been working in the field, with meeting bots, since 4 years)

A Grammarly-style retrofit would’ve actually been appropriate here—I made a syntax error.

If you don’t mind, I’ll be stealing and using that analogy!

We were talking about that approach today with a friend who unifies parking apps across the country. He calls his engine UMM—Ultimate Macro Machine.

I’m working in the “classic” generic browser-automation agents with a unified API for meeting bots (transcription, voice input, etc.).

I really like you retrofit analogy - not sure if you coined it or geohot has.

It seems to me that's where a ton of start-ups are currently converging - not repairing the old, which would be too complicated, but understanding and "mending" for new usages, or functionalities.