Hard-coded provider ip problems

Since switching the riseup provider to lilypad, and new infrastructure, some users began to report problems connecting to the api endpoint. Eventually, we discovered it was only desktop clients who had this problem, and the problem was because we had changed the IP of the API endpoint, and it appears that bitmask hard-codes the ip of the provider api endpoint. I think there may be a rationale behind this (such as guarding against DNS problems), but it is a very hidden, tightly coupled, and different mechanism than android uses.

I think this should be revisited, because provider agility around IP addresses is important. Right now riseup has two different ips that resolve for api.black.riseup.net and those should be able to change (by either adding more, or removing ips) depending on the needs of the provider and not require a code change, release, and roll-out to users of new versions.