Private key limit too low for keeping mirror updated?

[moritz]

Hey,

I know that you recommend setting up a mirror once using the JSON-dump of the database and then using the public key to have users update their data.

However, I was thinking to run my own mirror and keep it updated, while having users contact my own API. This would also reduce the load on your server.
So basically:
Lots of requests: My users -> My server
Only once or twice a day: my server -> your server

But when doing this, the private key will reach its limit within the first year of doing updates if I update daily. Is there any way around that or should I have users contact your API directly instead of mine?

[edirol]

Hello.

Private key, JSON and SQL dumps were made to create initial mirror while public key was made to keep mirror updated. Public key has limit per IP (remaining_monthly_allowance). This limit resets each month (allowance_refresh_timer).

[moritz]

Ah, got it. So after initial mirror, I should just use the Public key on my server. It has a fixed IP, but because it gets refreshed every month, that will be enough.

Thanks for the quick clarification!