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.
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?
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.
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.
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?