The web interface won't mark an activity as restricted if it's restricted but the user has permission to sign up for it; however, this isn't true for the API. I believe this is because of some magic getter for the restricted attribute, whereas the API just gives the actual restricted value as displayed in the database.
The web interface won't mark an activity as restricted if it's restricted but the user has permission to sign up for it; however, this isn't true for the API. I believe this is because of some magic getter for the restricted attribute, whereas the API just gives the actual restricted value as displayed in the database.
I have no idea how to mark upstream bugs.