#1196 MUC: Change restrict_room_creation local to allow all c2s instead of parent host

Reporter pep.
Owner Nobody
Created
Updated
Stars ★ (1)
Tags
  • Type-Enhancement
  • Priority-Medium
  • Status-New
  1. pep. on

    Description of feature: ``` VirtualHost "foo.bar" VirtualHost "foo.baz" Component "muc.foo.bar" "muc" restrict_room_creation = "local" ``` Currently this configuration snippet only allows accounts from foo.bar to creation MUCs on muc.foo.bar. This is a request to change the meaning of "local" to allow all c2s connections, (foo.bar and foo.baz here), and maybe a "parent" value to imitate the current behaviour. Motivation: Semantically "local" seems closer to "c2s" than the current behaviour. I was surprised not to have my anon.foo.bar host allowed to create any MUC on my component. Some people might still want to have the current behaviour though, and "parent" could be added as a possible value, as Zash suggested. This is certainly going to break people's workflow. <xkcd reference>

  2. MattJ on

    Changes
    • title Change restrict_room_creation local to allow all c2s instead of parent host MUC: Change restrict_room_creation local to allow all c2s instead of parent host
  3. MattJ on

    Proposal: room_creation_policy = "open" -- Anyone may create rooms room_creation_policy = "admin" -- Only admins may create rooms room_creation_policy = "host" -- Anyone on the "parent" host may create rooms room_creation_policy = "server" -- Anyone on the same server may create rooms, regardless of host

  4. pep. on

    With `restrict_room_creation = "local"` mapping to `room_creation_policy = "host"` for backwards compatibility I assume? LGTM. What would be the recommended way to go if I wanted more detailed permissions? custom module/mod_firewall? (Note, I don't need it atm)

New comment

Not published. Used for spam prevention and optional update notifications.