Page 1 of 1

Regarding Public Projects

Posted: Sat Apr 20, 2019 5:56 am
by Leo_Pride
Hi all!

As many of you may have noticed, we've changed the way we handle key issuance, to prevent excessive mirroring without artificially limiting end users. To that end, our developers are still tweaking key restrictions, but a few things should be noted.
  • First and foremost, key pairs are being issued solely to developers going forward.
  • End users should not be requesting keys on this forum, as legacy keys are no longer directly supported.
  • Keys are issued in private/public combinatons.
  • Private keys should be used once to mirror the entire dataset and should not be disclosed to the general public, as they are invalidated once they limit out.
  • Public keys need not be obfuscated at all, as requests made using those are distinguished by true IPs.
  • When in doubt - or in testing - run your codebase against an extremely limited set of data using your public key to check core functionality before mirroring with your private key. Legitimately malfunctioning code may be grounds for an adjustment, but excessive adjustments may lead to negative corrective measures. Please do your part to avoid this by resisting the urge to test on your private key.
Additionally, it's worth noting that application developers like Faith and CyberFox put a lot of heart and soul into their projects, so please respect that and let them know first when there seems to be an issue with keys, and we'll work something out with them to minimise interruptions.

Thank you for your time and consideration in this matter.