Uploaded image for project: 'Singularity Viewer'
  1. SV-1752

Restore right-click profile identification of object-produced public chat

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Medium
    • Resolution: Duplicate
    • Component/s: None
    • Labels:
      None
    • Sprint:
    • External issue ID:
      1752

      Description

      Would it be possible to restore right-click profile identification of object-produced chat?

      Two or three updates ago (I think), Singularity had the same ability to identify object- or HUD-produced chat as the SL viewer. This was a VERY important function as griefers often use objects or HUDs to produce public chat under another avatar's name. To identify the griefer, all one had to do was open up a separate Chat Window, right-click on the object chat's fake avatar name (which should be blue while the object-chat is green), and the profile of the real griefer would pop up.

      Similarly, if one wants to stop annoying double-repeating chat-extenders, you do the same thing: R-click on the repeating name (also blue, with green chat text), and profile pops up. Then you can just block/derender and the repeating text stops.

      But the importance of this function lies in being able to identify object-spammers, fake-name chat and similar griefing acts.

      The SL viewer still has this function. But Singularity no longer does.

      Would it be possible to restore it? It is an invaluable piece of protection and extremely important.

      PLEASE restore it. Thank you very very much.

      Original reporter: macmcmac...@gmail.com

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                Anonymous
              • Votes:
                1 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: