Group invites via scripted objects
tracked
Zi Ree
These days, we have to resort to bots when we want to send another user a group invitation. This is pretty annoying and uses additional resources while scripted objects are pretty cheap in comparison. I propose:
llInviteToGroup(key target_avatar, string group_role);
group_role can be either the name of the role or its key.
Limitations:
- The object must be set to the group it should invite others to, so no group name/key needed in the command.
- The object inviting the avatar must be owned by someone who is a member of the group and has the necessary group role ability to invite others to the selected role.
- The object must be in the same region as target_avatar.
- The object can not be an attachment.
- The object can only send invites inside a touch_* event.
- The object will sleep 10 seconds after each invitation (optional? not sure if it's needed)
Log In
Darling Brody
We do need this function, but those restrictions mean the group invite is limited to people visiting an in-world location who choose to touch an object to get an invite.
What about people unpacking a product they purchased from marketplace where the creator wants to offer them access to a product support group?
These restrictions mean a customer can't be invited to a group as part of unpacking a product they purchased from marketplace, because those restrictions will prevent a remote object or the object now owned by the customer from sending the invite.
- The object must be set to the group it should invite others to...
- The object must be in the same region as target_avatar...
- The object can not be an attachment...
- The object can only send invites inside a touch_* event...
We should also consider giving the ability to remove people from groups by script too, as this is also a function of bots. As is being able to assign roles to people, providing the object is owned by someone with that ability.
Signal Linden
tracked
Anna Salyx
As it stands the only way to invite to a closed group, or to invite to group to a specific role, is either a) a human agent sends the invite request, or b) a scripted agent (bot) sends the invite request.
When you get down to the very basics: using a scripted agent (bot) or being able to send the invite request programmatically (script) is functionally identical, with the latter's only difference is one less avatar logged into the grid. I have zero problem with the request with the limitations listed. But I would modify one: "The object can only send invites inside the touch_* event OR the money event." That way if someone pays a rental box, they can automatically be invited to a required land group without having to perform an additional step. that's more of a QOL tweak though.
All the discussion below about group moderation and privacy requirements are a dodge, or a fundamental misunderstanding on what is being request here, IMO.
Qie Niangao
We have needed this for a long, long time. The proposal already requires the invitation to be inside a touch_* event so limiting it to once per event might be both better and easier to implement than a time-based throttle.
And no, using the viewer URI is not even relevant to this need. Yes, that's all we can do now, short of the expense and absurdity of adding a whole damned bot to the group just to do invites. And chatting out that URI and begging for a click is both annoying and pathetic, and as others point out, totally useless for groups not set to open access.
Cutie Crush
This is an excellent idea.
Currently all we can do via LSL is say "Hey, consider joining our group here: https://world.secondlife.com/group/ec0ac7b5-21e3-265c-d987-6365f7cd7b9e" (or secondlife:///app/group/ec0ac7b5-21e3-265c-d987-6365f7cd7b9e/about ).
This option does no good if the group isn't set to public access.
A great example of this being an issue would be with land rentals. Say you interact with a rental kiosk on an available plot of land. Pay the kiosk.. great, you're a renter! Except the group you need for rezzing isn't public access.. so you're stuck renting land, waiting for the land group's representatives to invite you to the group. Days go by because the someone who normally does that had an extra busy week in RL.. and suddenly the whole experience has left a bad taste in your mouth.
The workaround has always been 'always-online' bots.. that listen for a message from the aforementioned kiosk, and then invite the new renter to the land's group. Using networked systems with large operations may free the individual landlord from needing to operate the bots (example: CasperLet?).. but the problem still exists.. a user account, even a scripted agent, has to invite the renter to the group needed for the land.
Allowing an LSL script owned by a person with 'invite' access within a group, to offer said invitations in their stead, seems a logical and useful simplification of the way landlords, stores, sales events, social groups, etc all try to work with a kludge of improvised solutions, delays with manual invitations, always on bots, and public-access groups.
Perhaps this could be heavily penalized with a throttle per script owner, per region.. possibly per invitee as well. 1 Invitation, per script owner, per invitee with let's say a 180 second cooldown before that script owner can send another invitation to that invitee.
Toothless Draegonne
Honestly I wouldn't bother with the region restriction. That just means the invite-o-bots have a reason to stick around. It may be better to have a viewer option "refuse scripted invites", which would also cover registered scripted agents.
Other than that, yes.