Uploaded image for project: 'Snowstorm'
  1. Snowstorm
  2. STORM-1731

Ad-hoc confererence block failing. Residents using it to start massive multi-sim conferences, used as a griefing tool.

    XMLWordPrintableJSON

    Details

    • Type: Defect
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Active
    • Labels:
      None
    • Environment:
    • Test Plan:
      Hide

      You will need 3 avatars to perform this test: Avatar A, Avatar B, and Avatar C

      Log the 3 avatars in, each on a unique computer

      Enable voice for each avatar

      Assemble them near each other

      Using B mute A

      PART 1 – Text Test

      1)
      Using A open the people panel
      Click the Nearby tab
      Select both B and C
      Click the IM button
      Write something into the Ad-hoc Conference window: only C sees the message

      2)
      As soon as C receives the message have C click on the >> in the IM window to display a list of who is in the session: B's name is there at the bottom but shortly disappears.

      3)
      Using C write something back: A receives the message, B does not receive the message

      Using A click X to close the Ad-Hoc session
      Using C click X to close the Ad-Hoc session

      PART 2 – Voice Test

      4)
      Using A return to the Nearby tab
      Select both B and C
      Click the Call button: a voice call session is established only with C

      Show
      You will need 3 avatars to perform this test: Avatar A, Avatar B, and Avatar C Log the 3 avatars in, each on a unique computer Enable voice for each avatar Assemble them near each other Using B mute A PART 1 – Text Test 1) Using A open the people panel Click the Nearby tab Select both B and C Click the IM button Write something into the Ad-hoc Conference window: only C sees the message 2) As soon as C receives the message have C click on the >> in the IM window to display a list of who is in the session: B's name is there at the bottom but shortly disappears. 3) Using C write something back: A receives the message, B does not receive the message Using A click X to close the Ad-Hoc session Using C click X to close the Ad-Hoc session PART 2 – Voice Test 4) Using A return to the Nearby tab Select both B and C Click the Call button: a voice call session is established only with C

      Description

      As a resident, I need to be able to block ad hoc conferences initiated by people whose purpose in Second Life is to cause problems. Current service and viewer behavior seems to allow blocking messages from the initiator but I still get added to the ad hoc sessions and see the messages from other people in the sessions. The initiator tends to open many ad hoc conference sessions during his "fun time". He then asks questions or makes inflammatory statements to elicit responses. Each of the sessions he is including me in opens with a bell to display the responses to me.

      I must not be added to ad hoc conference sessions initiated by a resident in my block list. Adding me to these sessions is failing to meet my expectations of service behavior, consistency and usability.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              peqa.team PEQA Team
              Reporter:
              ardy.lay Ardy Lay
              Extended Group Visibility:
              jira-users
              Watchers:
              15 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  PagerDuty