search

secondlife / jira-archive

3 stars 0 forks source link

[BUG-139139] Feature Request: Block the ability to create ad-hoc chat sessions if number of participants exceeds a certain number. #2366

Open sl-service-account opened 7 years ago

sl-service-account commented 7 years ago

Information

Occasionally we get agents using illegal tpv's to remotely create ad-hoc sessions involving hundreds to thousands of agents at once. These viewers pull these agent keys from a list of agents from previously visited regions or from group member lists.

The chat server should be blocking ad-hoc session requests if the number of participants exceeds 50, 100 or 125 agents or maybe even reference the agent limit of the region the session starter is in.

Ad-hoc sessions are supposed to only involve friends, nearby agents or a small group, not masses of people.

Other Information

It wouldn't hurt to also delay/block being able to create another ad-hoc session when you just created a session with 100 people or block creating multiple ad-hoc sessions that total over 100 or more people across all active sessions.

I encourage further discussion on this topic. Thanks in advance for any consideration.

Links

Duplicates

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-139139 | | Summary | Feature Request: Block the ability to create ad-hoc chat sessions if number of participants exceeds a certain number. | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Lucia Nightfire (lucia.nightfire) | | Created at | 2017-09-27T03:38:38Z | | Updated at | 2019-08-05T14:24:01Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2017-09-27T10:07:31.829-0500', 'How would you like the feature to work?': "Occasionally we get agents using illegal tpv's to remotely create ad-hoc sessions involving hundreds to thousands of agents at once. These viewers pull these agent keys from a list of agents from previously visited regions or from group member lists.\r\n\r\nThe chat server should be blocking ad-hoc session requests if the number of participants exceeds 50, 100 or 125 agents or maybe even reference the agent limit of the region the session starter is in.\r\n\r\nAd-hoc sessions are supposed to only involve friends, nearby agents or a small group, not masses of people.\r\n\r\nI encourage further discussion on this topic. Thanks in advance for any consideration.", 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': '?', } ```
sl-service-account commented 7 years ago

Whirly Fizzle commented at 2017-09-27T15:07:32Z

How about restricting the ability to start an ad-hoc chat with more then X people a premium only feature? ;)

sl-service-account commented 7 years ago

polysail commented at 2017-09-27T15:19:36Z

It makes sense to limit ad-hoc chats to 7 people. ( That's a decent cluster of friends for a night out! ) With the premium benefit of raising the cap to 25-30. That's sufficient for all those DJ's to spam their friend list. We may hate it, but it's valued 'social interaction' for many.

Also ~ if not one person in your group of 25 friends has premium... get better friends?

sl-service-account commented 7 years ago

polysail commented at 2017-09-27T15:40:03Z, updated at 2017-09-27T15:42:58Z

During the regular Oz meeting this JIRA came up in the discussion.

I don't know how group chats ( not ad-hoc chats ) are handled overall, but I've seen group chats show up as giant ad-hoc chats as per this bug https://jira.secondlife.com/browse/BUG-41604. If this is the case, limiting the size of ad-hoc chat sessions may adversely affect participating in group chats for some people.

Limiting the number of ad-hoc chats that can be created by an avatar per time frame will seriously aggravate people who are simply trying to mitigate the behavior in this bug as well: https://jira.secondlife.com/browse/BUG-10159 as the primary workaround for it is simply to keep creating new ad-hoc chat sessions until all parties are able to confirm they are connected and participating.

Overall I wholeheartedly support a restriction to ad-hoc chat sizes. There's no reason to permit massive ad-hoc chats, as I can't think of a use aside from griefing.