This question already has answers here:
Limitations for Firebase Notification Topics
(2 answers)
Closed 9 months ago.
is there limitation in sending messages with topic? For instance, let's assume there are 100000 users subscribing topic, "weather". And I want to send messages to the topic "weather". is it possible to send 100000 messages to the subscribers(100000 users) at once without any rejection?
There is no documented limit to the number of subscribers that can be added to an FCM topic. While there is probably a physical limit somewhere in the system, I haven't heard of what that would be, and there are definitely projects with well over 100K subscribers to a topic.
Also see:
Limitations for Firebase Notification Topics (which your question is actually a duplicate of, so I'll close it shortly)
What is the maximum limit of users for single topic subscription in Firebase?
Related
I subscribed 1.5 million users to topic TEST. I sent a message to TEST with a reach rate of only 10% to 20%. If I send it alone to 1.5 million users, the arrival rate will reach 40% to 60%. We think 40% ~ 60% are reasonable. Does FCM have any restrictions on the amount of delivery for topic messages?
Thanks
There is no limit on the number of devices that can subscribe to a topic. tThe only difference between using a topic and directly sending to the device IDs should be that topic delivery takes slightly longer due to the fan-out process.
As long as the devices have subscribed to the topics with their latest tokens/instance IDs, the delivery rates should be the same.
If this is not the case, it would be great if you can give clear steps to reproduce in the question. But I get that this may not be possible if the problem only happens at >1M registrations. In that case I recommend reaching out to Firebase support for personalized help in troubleshooting.
I want to send OTP , first to Telegram with usual SMS fallback.
Therefore i have to detect read callback of OTP message from user only with telegram cli API, unfortunately(Telegram bots doesn't provide read ack. feature).
There is no any concrete info in Telegram.
Is there any limit related to telegram bot (and telegram cli) subscribers(contacts) count? Except report spam.
Also what is the limit with native telegram api sendMessage? Which density i have to keep to not banned? Also do i need more numbers or accounts for this?
I searched everywhere and can't find relevant numbers although there are some users with plenty number of accounts.
Thanks for help!
UPDATE
Limitations on bot like 30q/sec and etc. is explicit in FAQ. i have to know all other limitations, especially on CLI(max contacts, requests frequency limit). For example, i have to know is this number registered in telegram - This is possible only with cli.Therefore i don't want to abuse platform restrictions, cause of commercial cause. Glad to hear more official ways.
You can check out Bot FAQ:
If you're sending bulk notifications to multiple users, the API will
not allow more than 30 messages per second or so. Consider spreading
out notifications over large intervals of 8—12 hours for best results.
Also note that your bot will not be able to send more than 20 messages
per minute to the same group.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I am trying to create a website which implements webrtc functionality.But in all the samples and reference documents , I was unable to find how to select for a specific user to chat with. Do i need to have some server kind of setup to list all available users or anything like that. Any sort of ideas will be helpful.
For eg:
In all the samples which i refered, the user was joining a particular room or a session and the other recipient also joins the same room for chat.But what i need is something similar to skype or hangout which shows the callee status before call, and want to get rid of this chat room concept.
There are three core areas of any real time communication service:
Presence - identifying who's online and who's available to speak for a call. (e.g showing a contact list and identifying who's online)
Signaling - initiating the call, exchanging IP addresses, negotiating capabilities, hanging up. In a lot of cases, Signaling and Presence can be combined into a single service.
Media connectivity and streaming - actually getting "connected" to the other endpoint and streaming audio/video. It typically requires some assistance from the signaling service to get the initial set of local, stun, and turn addresses exchanged in order to establish a connection with the other node. It also includes the codec technology, streaming code, and rendering.
Unless something has changed, WebRTC, to the best of my understanding, is just about #3 - media connectivity and streaming. It still requires the website to provide signaling (exchanging the SDP messages).
There are some companies and open source projects that indicate they provide the complete solution, but I've never used any.
With the introduction of topics in android gcm I was evaluating this option to easen the work that should be done to mantain in sync our server with some subscriptions.
However I have read in the documentation that the use of topics is limited to 1 million subscriptions. Does this mean that you can't have more than one million users (with one or more topics) or that you can only have 1 million topics subscribed (for example 100.000 users subscribed to 10 topics each) ?
It's a limit on subscriptions in your app in total, across all topics created within your app.
You will get a TOO_MANY_SUBSCRIBERS error when the number of subscriptions per app exceeds the 1 million limit.
I think the limit has now been scrapped:
GCM topic messaging allows your app server to send a message to
multiple devices that have opted in to a particular topic. Based on
the publish/subscribe model, topic messaging supports unlimited
subscriptions per app.
https://developers.google.com/cloud-messaging/topic-messaging
You could try to work around this limit by using multiple SENDER_IDs when registering devices.
Since the 1 million subscriptions limit is enforced application-wide, I'm pretty sure that Google's way of tracking that is via the SENDER_ID.
And then, on the server-side, you'd have to issue multiple publish requests to GCM (each time with a different Server API Key, to support more than 1 million devices).
I'm going to test this theory out and let you know what I find. The worst-case scenario is that it is enforced via the application's package name (com.example.package), and then there is no elegant workaround.
Update: The limit has now been removed!
We’re now happy to announce that we’re allowing unlimited free topics for your app. This means app developers can place an unlimited number of devices within each topic and create an unlimited number of topics.
http://googledevelopers.blogspot.co.il/2015/12/google-cloud-messaging-weve-come-long.html?utm_source=Android+Weekly&utm_campaign=1cb848077c-Android_Weekly_184&utm_medium=email&utm_term=0_4eb677ad19-1cb848077c-337844217
GCM now removed the limit, check this: https://developers.google.com/cloud-messaging/topic-messaging
Also Firebase Cloud Messaging (FCM) the same. https://firebase.google.com/docs/cloud-messaging/android/topic-messaging
GCM topic messaging allows your app server to send a message to
multiple devices that have opted in to a particular topic. Based on
the publish/subscribe model, topic messaging supports unlimited
subscriptions per app. The app server sends messages with payloads up
to 2KB to the topic, and GCM handles the message routing and delivers
the message reliably to the right devices. For example, users of a
weather forecasting app could opt in to a "severe weather alerts"
topic and receive notifications of storms threatening specified areas.
Topic messaging supports unlimited topics and subscriptions for each app.
Check This
[FCM Notifications][1]https://firebase.google.com/docs/cloud-messaging/android/topic-messaging
This question already has answers here:
Windows Azure Storage Certificate Expired
(4 answers)
Closed 9 years ago.
I'm having trouble with a number of role instances refusing to leave the "waiting for status" state. It's the same problem that a user had here.
My Azure subscription comes from BizSpark and therefore I don't have the ability to submit a support ticket to get this problem fixed (assuming it is the same problem of a bad node).
Presumably, although my subscription comes from BizSpark, I'm still entitled to a functional service. Could anybody help me come up with a self remedy or a way of contacting support please?
Thanks!
Several Azure services are having problems at the moment, check here first:
http://www.windowsazure.com/en-us/support/service-dashboard/
I don't think that having a Bizspark-based subscription excludes you from buying support. The support plans should have something that fits your needs. The cheapest plan that will allow you to submit a support ticket (via the web) is $29 per month. I suggest that Bizspark or not, that you spring for at least the $29, so that you can get attention to your issues.