Rate Limiting Solution - facebook

I am developing a software application that uses the Facebook API to conduct searches on open posts etc.
The issue I am trying to get my head around is rate limiting imposed by the Facebook API.
All the other tools that do similar things to mine are managed services, not stand alone software applications. So I assume customers that subscribe to the service are throttled globally from within the managed service.
My issue is that my product is a stand alone software application.
So if I sell 100 software licences and all 100 people try and use it at the same time the application could grind to a halt as the Facebook API will rate limit them.
The application will use the same Application ID; as far as I know I have to.
Is there aby solution to this problem?

As you are planning to build application that you consider would just exceed the starting threshold, you may do what the Facebook Platform Policy suggest, quoting from there
If you exceed, or plan to exceed, any of the following thresholds please contact us as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day).

Related

WhatsApp rejects all templates designed for business-initiated conversation using Business API

I am testing a feature of WhatsApp Business API using a test account. I want to integrate this functionality in my personal project. So far, I have tried submitting many different templates. But none of them were approved. Not just that, most of them were rejected with seconds by some AI I guess. They haven't provided any specific reason for it.
These are the templates I have submitted till now:
This template is for test purpose only!
(Transactional) Your package has been shipped. It will be delivered in 4 business days.
(Transactional)
Dear {{1}},
Your request to change your ABCD username has been approved. You can access your account using your new username.
Contact ABCD customer support for any further assistance.
(Transactional)
Dear Customer,
Welcome to ABCD Payment Gateway!
You’re now one among 50 lakh+ businesses that use ABCD to accept payments from their customers. Start your journey by visiting ABCD developer's documentation page.
We are eager to offer you support in integrating our payment gateway with your platform and to provide the best customer experience possible.
(Marketing)
Why Awareness campaign on waste management is so important?
Waste management and disposal of waste is a serious issue that we are facing nowadays. If we are not aware of proper waste management, it leads to serious issues like air pollution, water pollution, and soil pollution. By doing small practices in our daily life we can make a huge difference. For that, we all have to practice the “3Rs” in our daily life.
The 3Rs – Reuse, Reduce, Recycle
Reduce- try to reduce the use of single-use products maximum especially plastic substances.
Reuse- always try to reuse day to life things. For example, carry kit when you are going for shopping.
Recycle- try maximum to recycle or reuse things other than disposing of.
Above all 3R’s will help us and our society for the proper disposal of waste management.
(Marketing)
Hi there!
We are excited to invite you to join us for ABCD`s Biggest Education Fair to fulfil your dream to study MS.
Many program representatives from different universities and institutions will be present at the fair to provide you with the latest information on admission requirements and scholarships, as well as answer any questions you may have.
Date: February 25, 2023
Venue: XYZ
Please register by visiting our website.
We look forward to seeing you there!
Best Wishes,
ABCD
Does anyone know what is the problem with these templates?

Google Analytics 4 (GA4) - Analytics Data API - When will this be out of Alpha, Beta?

Based on the Analytics Data API Banner ("Keep in mind that these APIs are pre-release and subject to change. Code built using these APIs should not be pushed to production. While we will try to notify you of upcoming changes, you should expect to encounter breaking changes before the APIs are publicly released."), the APIs are pre-release and subject to change.
https://developers.google.com/analytics/trusted-testing/analytics-data
When is the Analytics Data API expected to be out of Alpha?
When is it expected to be out of Beta?
Is this timeline a few months, a few quarters, or will it take a year or more to stabilize and publish?
Followup question, if this is going to take some time to move out of Alpha / Beta, do you expect to allow "App+Web" upgrades to downgrade back to "Universal Analytics"?
I have also sent an email to the address in the documentation with no response.
Thanks!
Brie,
I don't believe there is a public timeline on the API release cycle, but we hope to move on to Beta fairly soon. As for your second question, it is not possible to downgrade GA4 (formely App+Web) properties back to "Universal Analytics", as they are fundamentally different.
Thanks,
Ilya
The Google Analytics Team
I imagine most developers are waiting until the official release of the API before incorporating it into their workflows. But I would recommend that we all spend some time testing the API and provide feedback to Google. That way we can point out any issues and suggest features that will be of value.
For example, I want to pull up to 50+ dimensions and metrics but the API limits runReport requests to 9 dimensions and 10 metrics. I doubt Google will budge on those quotas so I figured I'd run multiple queries and merge them programmatically. Unfortunately, that's not a viable approach since there is no universal key/column available to effectively join data across those queries.
However, if the Google Analytics session id were a dimension it could serve as that universal column. So I made an entry under the Google Analytics Issue tracker requesting just that (feel free to star Issue#: 188980721).
So get involved, the sooner we do and vocalize our needs (especially at this stage of development) the more likely the API will meet those goals.

Need some advice to get a commercial xmpp application developed

I have a business idea which I want to materialize for sometime .. I recently shared my idea with 2 close friends who also found it very interesting, new and doable plus the cost included for the project to start is reasonable and they have planned to invest in it. Much of the success of this project app depends on the proper marketing element out of which most of the time, you have to personally meet up with clients/vendor and make them use your application.
The idea is to connect local ecommerce (retail shops, businesses, vendors, etc.) with users/customers through a messaging app mostly similar to whatsapp. I have already started to look for a xmpp/jabber developer who can accomplish our requirements. We are expecting him to develop the app and also set-up the server requirements. Our budget lies within $3000-4000 range for the project to initiate.
I want the app to have the following aspects:
a) user friendly GUI
b) highly scalable (planning to start within my city located in south asia)
c) location sharing (want users to navigate nearby shops/vendor offering their type of goods/services)
d) have a user review feedback against vendors and an additional page for vendor profile/rating system
e) only customer - vendor chats with functionalities like camera snaps, audio recording (just like whatsapp).
f) both for ios and android
Now the whole idea outlaid, after reading lots of articles, discussion and tutorials, I have some questions (I am a non-technical person btw):
1- I believe ejabberd is the best option as compared to tigase or prosody due to high scability. Is this ok to go with or should I look at other xmpp servers?
2- Currently, I am planning to launch this application within my city (rated as worldwide no.2 as per population stats of above 25m people), should I set-up a local server with high internet bandwith and a powerful machine or should I outsource it to some xmpp hosted server in the US (as their technological infrastructure has always provided quality service).
3- Should I be worried about the developer stealing the source code or is there any effective way to minimize this risk?
4- Any ideas what other things I am missing. This is dead serious for me and I am willing to do anything to get this project on the road.
(P.S.: The idea for this app is similar to the existing app called Lookup but I am planning to add some variations to it)
Thanks and sorry for being a bit lengthy ..
Regards,
Ahmed
ejabberd is indeed likely your best bet. However, be careful about the budget. To launch a quality service in an highly competitive area you have to have a significant budget, both development and marketing, if you expect your project to succeed.

Is it possible to connect my app to my QBO account using the intuit development server indefinitely?

I originally posted this question as an 'answer' to:
Can a single company really not use QB API?...Semi Rant
but am reposting, because it is a question.
The original poster and I face a similar problem wanting to use the QBO API for an application designed for a single company. What would be the disadvantage of connecting my app to my QBO account using the intuit development server indefinitely, i.e., never take my app through the production qualification process?
Thank you.
I believe that is possible but then you can use at max 10 developer connections.
As we already mentioned we do not not support custom integrations at this time.
Even we wouldn’t recommend moving you to production as it would cost us $1k per year to security review it, and we would only recover about $60 per year in connection fees.
So, the disadvantage for you will be in terms of number of connections, limited support and your app vulnerability since it has not gone through the security review process.
Please read the policy docs mentioned here:
https://developer.intuit.com/docs/0025_quickbooksapi/0005_introduction_to_quickbooksapi/z_developer_policies_and_guidelines
Edit for the question asked:
When you login into developer.intuit.com, Go to Manage My Apps, then click your app.
You will see the number of connections for that app under Test connections.
It refers to the numbers of company files your app is associated with or has been authorized to access data.

Own Backend vs BaaS [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am trying to decide between two development firms. One wants to go with Parse while the other wants to build a backend. I would like to get feedback and reasons why building a backend or using a BaaS such as Parse, Stackmob is better in terms of scalability and performance.
For example let's use SnapChat a highly used app that handles millions of users and data requests. What would happen if a newly created app were to experience a large increase in users and data request. Would the backend be able to handle this? Would I be looking to have it fixed shortly after the increase in users?
Something like Parse.com gives you a lot of value for very little capital investment. With BaaS, all of the gory details of infrastructure management are hidden. Deployment, system capacity issues, system availability, system security, database administration and a myriad of other task simply go away when using a good BaaS. Parse.com for instance, uses Amazon Web Services and elastic load balancing to dynamically add more capacity to the system as usage increases. This is the nirvana of capacity management.
Parse.com is a special kind of BaaS. Parse.com's intended purpose is to be a light-weight back-end back-end for mobile apps. I believe Parse.com is a very good mobile backend-as-a-service (MBaaS - link to a Forrester article on the subject).
That said, there are times when Parse.com is not the right solution. Estimate the number of users for the application and the number of HTTP requests and average user would send in a day. Parse.com charges by the number of transactions. The Pro Plan has these limits:
15 million HTTP requests per month
Burst limit of 40 requests per second
Many small transactions can result in a higher cost to the app owner. For example, if there are 4,500 users, each sending 125 HTTP requests to Parse.com per day, then you are already looking at 16,850,000 requests every 30 days. Parse.com also offers a higher level of service called Parse Enterprise. Details about this plan are not published.
The services provided by a BaaS/MBaaS save much time and energy on the part of the application developer, but impose some constraints. For example, the response time of Parse.com might be too slow for your needs. Unless you upgrade to their Enterprise plan, you have no control over response times. You currently have no control over where your app is hosted (Parse apps are presently run out of Amazon's data centers in Virginia, I believe).
The BaaS providers I have looked at do not provide quality-of-service metrics. Even if they did, there is no community agreement on what metrics would be meaningful. You just get what you get and hope it is good enough for your needs.
An application is a good candidate for an MBaaS if :
It is simple or the application logic can run entirely on the client (phone, tablet...)
It is impossible to estimate the number of users or the number of users could be huge.
You don't want a big upfront capital investment.
You don't want to hire infrastructure specialists to handle capacity/security/data/recovery/network engineering.
Your application does not have strict response time requirements.
Parse's best use case is the iPhone developer who wrote a game and needs to store the user's high scores, but knows nothing about servers. That said, complex application like Hipmunk are using Parse. Have a look at Parse.com's portfolio of case studies. Can you imagine your application in that portfolio or is it very different from those apps?
Even if a BaaS is not the right solution, a PaaS or IaaS might be. Look at Rackspace and AWS. In this day and age, buying hardware and running a data center is tough to justify.
BaaS providers like apiomat or parse have to handle the requests of thousands of apps. Every app can have lots of users there. The providers are forced to make the system absolutely secure and scalable because if there are any issues about one of those points it will be the end of their business... Building scalable secure backends on your own is not as easy a you would expect. Those companys mentioned above have invested some man-years in that.