简体   繁体   English

应用程序管理多个Twitter帐户

[英]Application to manage multiple twitter accounts

I need some insights on making an application to manage multiple twitter accounts from a single web app. 我需要一些有关开发应用程序以从单个Web应用程序管理多个Twitter帐户的见解。 I have stored oauth token and secrets for these apps on a database and would like to have realtime displays of these account on different panes. 我已将这些应用程序的oauth令牌和密码存储在数据库中,并希望在不同的窗格中实时显示这些帐户。 Basically, I don't need help with code, I am just looking for ideas how I can proceed. 基本上,我不需要代码方面的帮助,我只是在寻找可以继续进行的想法。

Basically, I like to create application like the hootsuite. 基本上,我喜欢创建像hootsuite这样的应用程序。 I would like to know how it manage to realtime update twitter timelines. 我想知道它如何实时更新Twitter时间轴。 The thing I can imagine is having a relay script that will make api requests to the twitter on the backend and send back json replies and then I update my views. 我可以想象的是,有一个中继脚本,该脚本将向后端的Twitter发出api请求,并发送回json答复,然后更新我的视图。 But I would have to hit the api in intervals. 但是我必须间隔一定时间才能到达api。 I have learned about siteStream api for twitter, but I am not sure it is out of beta. 我已经了解了适用于Twitter的siteStream api,但是我不确定它是否超出测试版。

So basically, any suggestions how I can implement an application that manages around 20-30 twitter applications with realtime updates of feeds, would be best. 因此,从根本上讲,关于如何实现可实时管理Feed的20-30个Twitter应用程序的应用程序的任何建议都是最好的。

So far I have made an application that would hit twitter api to fetch new tweets. 到目前为止,我已经制作了一个可以通过twitter api获取新tweet的应用程序。 But for this I think I will soon run out of rate limits. 但是为此,我认为我很快就会超出速率限制。 Is there any positive approach in this regard? 在这方面有什么积极的方法吗?

I apologise if this question sounds vague, but I am looking for insights and not any coding help but architecture suggestion would be great. 如果这个问题听起来模棱两可,我深表歉意,但我想寻求的是见识,而不是提供任何编码帮助,但体系结构建议会很棒。

What you describe looks like a good use case for the user streams API . 您所描述的内容看起来像是用户流API的一个很好的用例。

It is stable, and using it will be more convenient to you rather than polling the REST API at regular interval. 它是稳定的,比起定期轮询REST API,使用起来更方便。 This way, you should not run into problems with rate limits. 这样,您就不会遇到速率限制问题。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM