Hello,
I understand security reasons. I fully agree too. But :

1. Wide team (Berkeley) are 10 years ago, disabled by Berkeley it self, because spam. With reasons. It was also a very big cleaning of "wide team" who abused the function "send to team". I really think all around the world, there are perhaps still a few hundreds "wide team", with responsible founder and admin.
I have read today on a other thread, that "wide team" are fully restricted.

2. The export of credits to BoincStats are random ! As team founder, I see my members. Some returns WU each day (not much of course because running time). But the latest synchro between BoincStats and team was two weeks ago. Once again, "wide team"

3. Member joining : the same : a new user of CPDN, (but very old user on Boinc) can not join my team ! Because security enforcment. Please, not answer me to check if "accept new members" is checked. After about 20 years BOINC, i know.

4. Very long running time : with risk to computations errors and no credits. Developper, why not to make more little, with less credits ? So you will escape never ending WU.

So please Admin, developper, consider all and restore.
You are interresed by results for project.
The cruncher are interrested by project but ALSO credits and world racing and ranking.
Example :
I will not block one WU on one core for one day for 1000 credit, if I can run ten WU on 8 cores in one day for 10 points each. It is pure figurative example.

So Admin, please unblock restriction on wide team.

Best regards

---

1. People who want to join your team at cpdn have to come here to cpdn and join it.

2. cpdn doesn't use the BOINC credit system, it has it's own system.
Credits here are calculated once a week, with the scripts running on Saturday, UK time. And there's often problems lately. The last failure was caused by a dos attack.

4. Of course the run times are long. This is about calculating the climate.

And the project is getting ready to use even larger models, with resolutions that are similar to what is achieved by the UK Met Office on their super computers.
Who are the people who create, maintain and own the programs that we use.

This project isn't suitable for everyone, and it seems that includes you.

Very long running time : with risk to computations errors and no credits. Developper, why not to make more little, with less credits ? So you will escape never ending WU.

Some of these models do have very long running times. That is why credits are given by trickles returned, so if the model fails half way through, you get about half the credits of a completed model.