—
no calls resolved yet
0 scored
single source
4
companies · 14 data points
if Twitter were to allow people again to make their own clients and to display the feed however they wanted and just have fun with it that'd probably be a good move
I think it's a pretty important collaborator. So we're a connector inside of ChatGPT. You can use us as an MCP provider inside their agent builder. ... And so, Zapier plus, you know, you know, a ChatGPT or a Claude or a Gemini is a pretty powerful combination.
I think our approach is, you know, we'd rather keep that for ourselves. But I do think there's benefit to releasing benchmarks and evals and other tools that can help you get a sense for how well these models perform against these tools. And if you make those public, you'll likely find that the foundation models will start training on those things. And that can be beneficial to you because you're getting some cooperation with everybody to improve on a certain thing that you actually are like, I
in the case of us, we're sitting on 14 years of workflow data. And as a result, like we know how to make these things reliable. And when things break, we know how to fix them. And, you know, we can use that data because very few other people have access to the corpus of information we have. And so we can use that to improve the experience.
if I was running Twitter if I was Jack you should just say anybody who makes their own client can take 30% of whatever revenue is shown in that client ... they're still getting 70% and it might make people more into basketball more interested in Twitter
if Twitter were to allow people again to make their own clients and to display the feed however they wanted and just have fun with it that'd probably be a good move
it seemed to have hurt them right they you don't see nearly as much interesting things happening with your Twitter developer pop ecosystem as you did you know four or five years ago
Twitter was worried about right with people basically replicating the Twitter feed and Twitter clients right it's like now you don't have to use Twitter calm or are officially sanctioned Twitter clients you're using some third-party client that maybe isn't pulling in ads in a way
their customer is ad buyers right and so that's who they end up serving and so the API platform has to serve the ad buyers as well and so that kind of creates an interesting friction that you don't necessarily get in b2b
whether it's slack logs or github commits or you know publications on a blog or what-have-you there is there is a digital trail of did you do this thing or not
that's what you see with like slack blowing up and why they've done so much to invest in integrations is because it makes slack sticky and you don't want to leave any more
if Google came out with a slack competitor let's say yeah which obviously they're going to at some point
so Aflac becomes the command line the operating system exactly and this can expand to any of the apps you right might use
most companies don't have time to build out native integrations between every possible permutation and combination of ways that their end customers might use it but they do have time to build an API and so whether it's us or our partners building integrations on a zapier you know hooks into this big ecosystem of 600 plus apps now and then regular people who aren't you know engineers who couldn't spell it barely spell API right are able to come in and you know set up these neat little automations
when you're looking at Salesforce to developer platform it's all about empowering the end user of salesforce.com and so the API is built to empower people to use more of Salesforce and get even more out of Salesforce they don't care if you log into Salesforce every day they care if you're getting value out of the data that's in Salesforce so if the API helps you get data into Salesforce and pull data out of Salesforce and makes Salesforce more sticky then of course Salesforce is gonna invest mor