gordalina
Joined 14 years ago
Karma
11
Submissions
24
Member since
May 28
Recent submissions
Comment · 1 year ago
Comment · 3 years ago
Hello, I'm an aspiring entrepreneur looking to validate my idea focused on privately syncing your personal events to your work calendar so that your teammates do not schedule meetings when you have personal events booked already.
The initial solution would involve a website where you can connect your personal and work calendars (Google/Outlook) and then setup syncs between different calendars. Then it would synchronize all events from a calendar to another while making those events private. It also would synchronize new events as they come up and delete events that were deleted from the original calendar.
I'm currently trying to guage how much of a problem this is in people's lives, as such I'd greatly appreciate your input on a brief survey. Thank you for your time and valuable feedback!
Comment · 3 years ago
Hello, I'm an aspiring entrepreneur looking to validate my idea focused on privately syncing your personal events to your work calendar so that your teammates do not schedule meetings when you have personal events booked already.
The initial solution would involve a website where you can connect your personal and work calendars (Google/Outlook) and then setup syncs between different calendars. Then it would synchronize all events from a calendar to another while making those events private. It also would synchronize new events as they come up and delete events that were deleted from the original calendar.
I'm currently trying to guage how much of a problem this is in people's lives, as such I'd greatly appreciate your input on a brief survey. Thank you for your time and valuable feedback!
Comment · 3 years ago
> $5 buys you a decent mobile subscription in Hungary (for this use-case). Setting up Automate is just graph editing. It is not much easier to add apps to Slack itself.
That's a good point! I was thinking about US-centric solutions.
Thank you for contributing to the conversation!
Comment · 3 years ago
Currently there is no way to share authenticator-based 2FA codes, happy to discuss further if this is an issue you'd like to be solved.
There is definitely a shift in the industry to move away from SMS for 2FA, but unfortunately people still use SMS and not all services support authenticator codes, which is still a problem.
Comment · 3 years ago
That's great!
SMS to Slack makes it easy for less technical folks to have a similar setup. Also cheaper than a monthly mobile service subscription.
Comment · 3 years ago
Yes, this is a solution for gmail login challenges.
In the slack app you create a phone number, then you register that phone number with your google account. From now on any login challenge you receive on that phone number will be sent to slack.
If you have a team of multiple people, they would all be able too see and use that code if they triggered it.
This is much better than having to ask the person who's phone number is associated with the gmail account. As they may not answer in time.
Comment · 3 years ago
SMS to Slack is not solving the providence problem of who triggered the 2FA flow (hasn't been an issue with customers), and it solves a problem for money - correct.
Comment · 3 years ago
This is compatible with many services, e.g.: Amazon, Google, Sendgrid. The one service that I know of that's not supported is TikTok.
I am working on adding support for a real phone number to solve for this shortcoming.
Comment · 3 years ago
If you think in terms of how much your time is worth:
- How much of would it cost you to forward a 2FA message to a team mate?
- Maybe two messages, if the first one expired by the time they saw it?
There's the ancillary cost of the frustration if something goes wrong, as well as dropping whatever you were doing to do this menial task.
This has been fully automated and managed with SMS to Slack.
Comment · 3 years ago
It's different for two reasons:
- As @detaro mentioned, it's a fully managed solution where you don't have to set it up, or more importantly, maintain it - it's all done for you.
- Twilio numbers do not receive SMS messages from short code numbers, which are usually the ones sending 2FA messages.
I had an annoying use case where when trying to login to a shared work account, the 2FA code was being sent to a colleague's phone number. Now being able to receive that code in Slack solved the problem.
Customers now use it for their own customer support. End users really like SMS as a messaging platform, nobody wants to send an email or talk to a chatbot.
It uses Elixir, Fly, GCP, Stripe, and a couple carriers.
https://smstoslack.com