• Here’s a brief overview of our App.
Kapsuli is an App that allows users to schedule rich tweets at key moments of their Twitch stream.
We believe Twitter is an awesome place to drive traffic when you’re live and we try to make it easy for live performers to communicate while they’re streaming (with the Kapsuli App you can schedule tweets when your stream starts but also when your stream reaches a certain amount of viewers, when you change games, after a certain amount of time, etc).
For the time being we are synced with Twitch but we can’t wait to be able to plug our tool with the Periscope API.
Imagine you plan to livestream an important social demonstration in the afternoon, you’d be able to prepare the best tweets related to the topic all along your Periscope, to drive traffic in real-time.
Here’s a quick video of our App onboarding here.
We are on the verge of going in public beta and at this very moment we have 100s of active users who give very positive feedback about the app.
• Yet, as our API access has been suspended two times in a row in the last 7 days, we decided to suspend our app as long as we don’t implement every measure needed to comply with 100% of the Twitter Rules.
This post sincerely aims with no animosity to move the Twitter-Kapsuli relationships from “police” vs “spammers” to co-creation
• We’ve been flagged by the system because of “large numbers of duplicate replies or mentions and large numbers of unsolicited replies or mentions”, considered as spam.
It’s actually a common thing in the eSport to @-mention your partners, friends or sponsors when you go live, that’s why some of the tweets from the App might have contained to many @-mentions.
But even if this behaviour can be explained, we have to restrict it to comply with the rules.
I can guess some the leading scheduling tools on the market like Buffer, Hootsuite and so on have faced the same challenge so I hope the community will share feedback about this.
Here are the 3 big measures we plan to implement in the next few days
Make it impossible to have more than 2 @-mentions in each tweet.
Have a rate-limit regarding tweet frequency: max. 1 tweet / 10 minutes.
Block a tweet to be sent out if it’s exactly the same as one who has been sent in the last 30 minutes.
What do you think about these preventive measures?
Has anyone in there already solved this regulation issue?
PS: dear Andy Piper, we already share a funny story together (or, at least, a shameful one on my end).
2 years ago our Kapsuli Twitter Card was broken and as we had no news from you, I asked our early users to use a Click-To-Tweet to support us. But I accidentally forgot to remove the “andypiper” mention in this and it resulted in hundreds of notifications for you - many apologies again - forcing you to even block our tweets!
“Errare humanum est”, and we’ve been learning. I genuinely hope this conversation will enable us to start again with a clean sheet and make all of this a funny entrepreneurial anecdote.
Thanks everyone for your help and feedback about these important issues.
PS’: @Valentin will be able to chat about every technical related feedback.