justinclift
commented
3 years ago Good questions. :smile:
For points 1 and 3:
We haven't imposed any limits on # of calls each day, and there isn't any cost (from us) for transfer. From our internal stats, we're not really getting anywhere near usage that would mean we have to introduce limits nor costs. If/when that starts happening, then we'll look into the best way of handling it.
In the meantime, we're upgrading the backend servers anyway to be much more powerful, so that'll push out any potential need for call limits further.
With point 2, it's currently hard coded to 512MB. Uploading a 512MB database can take an awful long time, but the option is there if people want to for some reason. On that note, if someone wants a larger database uploaded, the new servers will be able to handle it (prob up to about 10GB). The current backend servers though would struggle, so we'll leave it as 512MB for now. :wink:
For point 4. To be a contributor you're probably best off to start getting the hang of documenting stuff using the wiki (it's public access, even for writing). We haven't really put enough time and effort into documenting stuff, so it's likely a case of making an initial start, learning from that, an iterating on it.
Does that make sense? :smile:
That aside, where does your general interest in this stuff lay and what skills are you already strong on? Personally, I've found that documenting stuff works pretty well if it ties into an area of interest. Whereas trying to force myself to document stuff that's knid of boring... keeps on getting put off. :wink:
datatalking
captn3m0
I've just learned about your project and perhaps this is discussed elsewhere but after reviewing the docs I didn't see where it showed what the limits of the API are.
Questions: