Comment by garygao
2 hours ago
We're not encouraging spam with this. We're mainly focused on existing conversational use cases that's currently done over SMS/RCS. They can be more human and expressive when done over iMessage.
2 hours ago
We're not encouraging spam with this. We're mainly focused on existing conversational use cases that's currently done over SMS/RCS. They can be more human and expressive when done over iMessage.
>We're not encouraging spam with this.
what you encourage and what actually happens are two different things, though. gmail does not actively encourage spam, yet most spam emails i receive are from gmail addresses.
you have to actively fight against malicious uses, like spam. "not encouraging" is nowhere near enough.
what systems/processes/safeguards do you have in place to prevent abuse?
I agree. We're not completely self-serve right now, so we get to talk with each potential customer and learn about their use case before onboarding them onto the platform. This way, we can prevent use cases that involve spam or abuse.
>We're not completely self-serve right now,
"right now", which implies that you plan to move to self-serve. and obviously manually checking in on each and every customer is not sustainable if you scale.
do you do periodic checkups now? hoping nobody lies during onboarding is risky, in an already-risky endeavor. have you thought about anti-abuse systems for when you go self-serve?
The last thing I want is an AI “thumbs up” or reaction over iMessage
For iPhone only users, so right off the bat your product is targeting 50% ish of a companies customer base. And the non iMessage people get a worse experience?
We have SMS/RCS fallback for non-iMessage devices. Also, in the verticals that we're targeting, the iMessage usage rate is a lot higher than 50%