If I made a mistake, please say so. You can contact me at [email protected]Note: I AM NOT STAFF
That may be the case, but if you choose to register an account here, we're happy to stripe it with moderator permissions for the cryptofree subforum so that you can extend your purview into some much-needed (as you point out) upgrading, updating, pruning, and general spring cleaning.
Cryptofree does end up being a bit of an also ran from the core team, in terms of promotion and spit-polishing (not in terms of security maintenance - there, it's looped into exactly the same procedures and operational oversight as the rest of the network and is indistinguishable in that category). We never actually announced it, as far as I know... I think someone volunteered to write a press release (who..?), and there was a reason we were waiting for a bit to do so. That was 2014, so apparently the waiting part we did really
Even by our sucky-marketing standards, we've sucked at letting folks know about cryptofree. It's not that we've held back, intentionally - it's simply that ooooh look - shiny pretty new!
This is the nature of many folks on the team, here, present company included.
Anyway, we'd love to see cfree spread wings and become more integrated into the community - it's a resource that has so much potential. We're more than happy to keep adding cfree nodes as fast as they're needed; the business case works (so far), in terms of folks "graduating" from cryptofree to full-bore access via token purchases. And it's easy to do the backend loadbalancing and cluster administration, compared to the multi-tier HAF provisioning steps required for geographically-limned cluster resources.
I suspect someone from the team may have already emailed you about this - but rather than burn effort hunting that fact down, it seems better to simply parallel task & hope we get things moving via that method, meanwhile.