Thank you for the heads-up. Link has been changed. Simon, Stuff.

Copenhagen and New York are just the very first cities we are covering. We will slowly extend over the next months. Just remember that public events can still be created outside these cities. -Simon, Stuff.

Time fields are 24hr. I don't have any issues entering 2:33pm/2:33pm in Chrome/Safari. Could you please try again and send me a screenshot on simon@stuff.li so we could have it resolved. Thank you. Simon, Stuff.

Thank you. I've spotted a few views that needs some love. Will have it fixed by Friday. Thank you for the heads-up. -Simon, Stuff.

Thanks for the feedback. We are looking into different opportunities - and weighing pros vs. cons on functionality and privacy. But one thing is sure, we will do our best to create something you will rather use than Facebook, Evite, Paperless post etc :-)

Simon, Stuff.

Hi, thanks a lot for your feedback and time. Much appreciated. We have had bunch of conversations re. call-to-actions vs. words vs. events. Initially we had loads of events on the frontpage - and everyone just thought we were a new version of Timeout without the option of creating your own private invitations.

Feel free to drop me an email on simon@stuff.li if you want to chat further or share notes.

Simon, Stuff.

Heja Sverige. My wife is Swedish. She told me you guys were ok with Danish ;-) Language switch is in the footer. Alternatively hit https://stuff.li/en directly.

Simon, Stuff.

We can mostly understand it when reading but it really is not a good idea to default to danish for a multitude of reasons.

Thanks, tried to put it in a couple of different spots over the past weeks - with pros and cons. Will give it another spin based on your feedback.

-Simon, Stuff.

Thank you so much for your feedback. Much appreciated. Will work on the copy and make it more clear. Especially on the privacy side. Also having a dashboard in pipeline showing what data is stored for how long etc.

Future business model will be based on professional organisers paying for services. We are currently looking into different directions based on the conversations we have with different venues and companies. Hope this clear things up.

-Simon, Stuff.

We are looking into Google/Linkedin Oauth. Not fans of Facebook, though... -Simon, Stuff.li

Yeah, which is why using their oauth is a great way to stick it to them! Obviously don't only use it, but giving their users a one-click way to leave their platform is hilarious!

I understand that you are not fans of Facebook. But couldn't this be a good opportunity to show Facebook users that there is an alternative out there? I'm just not sure that restricting users who primarily use Facebook oauth does any good, to me it feels like a wasted opportunity!

I think the only reason to include FB OAuth is if it allowed such users to integrate the service with FB Events (which, AFAIK, isn't possible with their current API).

I'd say it's a given that FB users also use Google, and would be just as likely to use either service's OAuth.

I think that's a safe assumption. Anecdotally though, I prefer to stick with one service and if I was offered options that didn't include my primary choice I might be reluctant to sign up. I just don't think that intentionally walling out a group of potential users is a great idea if you're trying to expand your audience.

I tried to quickly find some numbers on distribution between them. Although I didn't find anything concrete, it seems to be Facebook > Google > LinkedIn. I would actually love to know more about this. Maybe someone with more experience has some more data?

A refreshing display of values, thank you.