Hi, thanks for your feedback. You’re right. There is no exception handling yet. I also plan to add some kind of state handling, so that jobs can be paused/resumed. What do you mean by making lookups?
Hi,
thanks for your comment and the link to your Geocoder. I think it's exactly the use case that I faced several times in the past.
I just saw that the Geocoder API is free with certain limitations. If I find some free time, I would like to create an enricher for it. Maybe it can help your clients (and other people of course) to save some time :)
Thanks for the feedback! It means that a single unit of the currency you are looking at must reach 2,054.37$ to obtain the same market cap as your selected base currency.
Korean exchanges are excluded. I currently use only the Top 100 to calculate the market cap. However, I would still say that you are right because one definitely can't liquidate the whole supply for the current market price.
Thank you for the feedback.
You're right, if the images are not yet cached it takes a while. First I pulled thoses images via Google Image Search but the results were not satisfiable but neither it's now. I'll take a look on better techniques.
Timer is decreasing and you got +2 seconds if you answer right.
I think it really depends on what kind of data is stored. For something like a chat it is a really nice solution in my opionion. If you have to apply complex queries and need full control over your data I would recommend a "real" backend.
For instance, we use Firebase for our community feed on http://spotpot.co but I would not use it to store user accounts there. In the end it is always a trade off but consider that for heavy real time applications a service like firebase can not only be convenient but also save you load on your infrastructure.
I dont think that it is spam, but you are right, there should be more information on the front page...how does the dairy look like...maybe show a public diary.