Given the ContinuumIO-suing-people-for-defaults mess, I'm hoping that we can see separate hosting for conda-forge (and for any needed tooling changes) so network admins can block access to repo.anaconda.com (at the DNS level) and miniforge would still work out of the box, by default pointing to new and separate hosting for conda-forge (and any other repos that are not Oracle-like encumbered). Ideally miniforge would also stop allowing use of defaults without manually adding a config for it.
This is a big change (unless Anaconda-the-company were to cooperate, in which case it'd be pretty easy to do with some apache/nginx configs), but it's what's necessary for orgs to feel really safe that they're not accidentally using defaults.
Given the ContinuumIO-suing-people-for-defaults mess, I'm hoping that we can see separate hosting for conda-forge (and for any needed tooling changes) so network admins can block access to repo.anaconda.com (at the DNS level) and miniforge would still work out of the box, by default pointing to new and separate hosting for conda-forge (and any other repos that are not Oracle-like encumbered). Ideally miniforge would also stop allowing use of defaults without manually adding a config for it.
This is a big change (unless Anaconda-the-company were to cooperate, in which case it'd be pretty easy to do with some apache/nginx configs), but it's what's necessary for orgs to feel really safe that they're not accidentally using defaults.