121–130 of 197 posts
Earlier quoted context omitted.
Hello @thejbf, I am not able to get your email from Hacker News, please send a test email to me at anurag.ait@gmail.com. Thanks for helping out
Try googling for the Hacker News usernames of these people who're trying to help you. Very likely you'll find them on Twitter, LinkedIn etc. E: If you haven't already done this, of course.
Earlier quoted context omitted.
That can be done but it will affect user experience right ? Better will be if I stop further registrations for the app.
An alternative: For non-premium users sync every 5 minutes. For premium users sync every minute. Use Indian payment gateways if possible, though Paypal works fine too.
We developed a product specifically for Google Drive using their JavaScript client. We were hoping to make it commercial but had to abandon those plans due to 3 bugs that have been present since around the beginning of 2013. Also, there's no open bug tracker. The developer relations people are very friendly, but when I ask where to report bugs I'm told "just tell me". So every 2 months I've reported the same 3 bugs i…
The instability/unreliability of the Drive API can't be understated. I used to have almost my entire app rely heavily on gdocs, but the api is far too shaky. Even wrapping every API call in a try_5_times function (which would often take 2-3 requests before getting a non-500), server errors would get through. Critical components of the API would go down for hours -- once, the entire day -- sometimes without even a bli…
If you build something on someone else's API, you can get fucked in a million ways. They might shut down the API (Google Reader), take away the functionality you relied on (Google Calendar), limit it (Twitter) or deprecate the version you're using, forcing you to do development work to keep working at the worst possible time for you (IOS). They might also decide that your product is very good and build a version of i…
> They might also decide that your product is very good and build a version of it themselves, using functions not available to you via the public API so that you cannot compete with it (Apple). Can you give an example of that?
If you build something on someone else's API, you can get fucked in a million ways. They might shut down the API (Google Reader), take away the functionality you relied on (Google Calendar), limit it (Twitter) or deprecate the version you're using, forcing you to do development work to keep working at the worst possible time for you (IOS). They might also decide that your product is very good and build a version of i…
Your argument is exactly why I don't use Google AppEngine. I know there are open-source stacks now that you can use if you want to take your AppEngine code in-house, but trying to build up an AppEngine infrastructure at probably the worst possible time ("we're getting billed @ $10k/month, but only making $8k! getting more popular will cause us to lose more money! quick, switch to custom servers!") when you can build up a solid infrastructure using technology that you can replicate on any VPS or managed box or colocated hardware that you buy seems the easiest way to scale.
If you build something on someone else's API, you can get fucked in a million ways. They might shut down the API (Google Reader), take away the functionality you relied on (Google Calendar), limit it (Twitter) or deprecate the version you're using, forcing you to do development work to keep working at the worst possible time for you (IOS). They might also decide that your product is very good and build a version of i…
- Be careful with companies that don't sell the API or SDK as a product (Twitter, Google, Faceboook, etc.)
- Watch out for companies that don't like to publish roadmaps and makes APIs and SDKs deprecated or obsolete with little warning (Apple, and more recently Microsoft)
1.) You are clearly young and do not know: if there is something on the internet you do not like, go make it yourself. What obligation does Google have to do something for you? None! They are providing mostly free services, but if you don't like it (or the support), go make your own and quit bothering people (and Google).
2.) You have no relation to the GMail Web Application, yet you specify: "Founder GmailSharedTasks" Remove the Gmail from your description and build out your solution without trying to get a free ride.
3.) Your Google Groups post can be summed up: "Cry! I'm not getting any attention for my pet project!" Instead of crying, create your own solution that does not leave you at the mercy of a company or individual who sees you only as "1 of billions". Get over yourself.
4.) You know how to code, you know how to integrate with FREE APIs, now learn what it takes to run a business.
The problems with Google start at the very basics of communication, with their policy of providing just one email adress (and nothing else) where you may or may not get an answer, effectively handling incoming requests more like petitions than providing real communication. This is in constrast to many other big companies where you get at least some reply (although it's often canned and not very helpful, but still mor…
One missing piece if the puzzle that is really going to make this idea if a shared platform across companies is moving to encrypted data oriented networking instead of server based networking. Not only does that model make vastly more sense in terms of the real topology of internet use now with data being propagated to leaf nodes, but there are also very strong reasons to move to distributed encrypted computing for privacy and economic reasons. A server based internet means server based web apps which is going to continue to result in due facto platforms created by individual companies.