API key limits on IP addressesSolved

So I've read the blog about "Enforcing the rule: limiting API keys to a single IP address". What is the current status of this? It says "in the near future" an API key can be used from a few different IP addresses. We have a test server and a production server so only two addresses. I noticed the production server stopped working when you started enforcing the limit, but saw the blog and since we weren't doing much with the test server then I thought it would be ok to wait for the "few addresses". Today I ran the test server and it was working so I thought that was all sorted, but now our production server is not working, so it seems the limit is still one, but is there some sort of timeout? The blog mentioned a 3 day limit, does that mean between each use from a different address?

Full blog post for people wanting context: https://wyday.com/blog/2019/when-in-conflict-security-supersedes-usability/

>> " What is the current status of this? It says "in the near future" an API key can be used from a few different IP addresses. "

Not done yet. No hard date. It'll be out when it's out. It's very low priority right now.

The solution: 1 IP per API key. If you made a mistake you can reset the last-used IP address manually on your settings page when you log into LimeLM.

Ok great, I hadn't spotted the reset option. Looks like I need to go the correct route and create a second API key next time we need some testing. Thx.