@dajbelshaw @bonfire @Supernova @Thursday @ivan I would indeed merge them together. Otherwise you can easily end up with an AWS IAM system oder endless mix-and-match options like the NTFS file system exposes.
@dajbelshaw @bonfire @Supernova @Thursday @Dragan_Espenschied

here an attempt of an improved UI for boundaries, the main outcomes are:

  • Reduce the permissions list toshow only the relevant ones for each activity type (eg. see / read / like / boost / mention / reply / edit (future one) / delete (future one) ...)
  • Default the permissions to be the same for all the users/circles involved
  • Let the user expand each verb to customise the permissions for the users involved (fig.3)
  • replace the 3 icons that shows the permission states (can / undefined / cannot) with a more standard 3-toggle state