All of them call a readNogos function. But only the first method also checks the nogo-vetos defined in the BRouter app. So with the other methods, a nogo works on all profiles.
I would vote to a remove the readNogos call on the profile and remoteProfile.
This means the clients have to transfer a nogo definition if needed - the web client already does it this way.
We have three ways to call a profile in the app:
All of them call a
readNogosfunction. But only the first method also checks the nogo-vetos defined in the BRouter app. So with the other methods, a nogo works on all profiles. I would vote to a remove thereadNogoscall on theprofileandremoteProfile. This means the clients have to transfer a nogo definition if needed - the web client already does it this way.