If I try to install it (from the project folder), I get about 5 deprecated warnings and then the same error about Acorn. If I try to run server.js from the project folder, it tells me it can't find the html-proxy module. Any time I try to run NPM install or NPM update, I get "permission denied" related to symlink './acorn/bin/acorn'. I am able to NPM init from the folder and create a JSON file. I transfer the downloaded CORS folder to the tablet via desktop PC and data cable. I have run termux-setup-storage so Termux should have access to the SDCard. I have it running successfully on an old Galaxy Tab A but I set that one up ages ago and must have forgot something in the process with this one! I am following these instructions. Oooph, that was a long one! Hope though, it fully explains geoplugin - we are here for you and any minor or major request, if serious and can benefit “not just you”, will always be taken on board and implemented if possible.I am trying to get this CORS server running with Termux on a Galaxy Tab A7. So by “forcing” users to pay a very small yearly charge for SSL (because they could opt for non-SSL via PHP for example), it takes the burden off us, off the free service and makes the end user (our “clients”) think about whether they need it. But by adding it as a “free” option, people will use it by default - unnecessary strain on a free service. Hmmm, see the backlog happening? Of course, all our requests don’t need SSL as they’re server-server calls. Why? I hear you ask as it costs “us” nothing - believe it or not, that SSL handshake adds 2ms to each lookup, which when you’re handling 4kreq/sec adds an 8 second latency to all the requests handles in each second. Yes, we charge a small 12€/yr fee for SSL. This cannot be far from the truth for geoplugin - we were the first to start a free API (so the others are copies) and we maintain the best free deal there is today (120 req/min). I’m mentioning all this because I read in a few places things like “free geolocation API disappear as quickly as they appear” When things like that happen, we know immediately because our support email is lit up like Times Square! They immediately removed the block after explanation. We handle so much traffic and are such a small fish, that entire networks (like Level3) have null-routed us in the past thinking we were a DDoS source. So geoplugin handles a 1/10th of that - ok, we don’t have complicated search algorithms to process, but we don’t own datacentres either! Yet we handle that traffic efficiently and reliably. To put 3.5-4k requests into perspective, Google handles globally around 40k requests a second on average (source: ) We’ve had around 20 minutes downtime in the last 2 years (the largest just outside of that timeframe was around 4hrs when we moved our entire infrastructure to a new DC and all clients were informed well in advance of the impending downtime - it was done in the early hours of Sun morning to avoid maximal impact). Today, we handle between 3.5 and 4k requests a second. We still make very very little profit, with most everything going into the infrastructure. Around 2010, a limit of 120 lookups per minute was introduced and anything over that required paid service (15€/mo, 120€ per yr etc) - those price points haven’t changed - and this allowed us to go expand our infrastructure to meet demand so that reliability became our calling card amongst all the other free services that popped up. Over time, like all things free, it got abused and service uptime suffered. At it’s base it has always been a geolocation plugin for this type of community and as such we will always try to take on board comments to facilitate things for developers.Īfter browsing around a few threads, particularly for geolocation, I feel there needs to be a minor “sales pitch” if you want to see it that way to explain geoplugin! Here goes:Įstablished in 2006 (yeah 12 darn years!!), geoplugin was the first free geolocation API. Please, noone, don’t take this as a sales pitch as it isn’t meant to be one, but simply explain the raison d’être behind geoplugin. Thanks Paul for bringing my attention to wappler! I’d like to take this one-off slot to explain geoplugin.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |