{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
This thread is inspired by another: view original post
Edited by Duardo:
1/16/2013 3:26:53 AM
22
A Viable Option for Group Messaging
For years, group leaders have been wanting to message their group members for important announcements or whatever. Bungie has given us A LOT of features with Bungie.next, but this feature hasn't happened yet. I doubt it ever will.
Perhaps I'm wrong and it will come during this beta, but it doesn't seem likely. I can't see a messaging system supporting 100 people, much less 1000. It would bee too cumbersome.
I might have an idea to solve this issue. What if a thread were created in a group that has an option to "Notify all group members" (perhaps an option reserved for the Admin only?) where members of that group are actually [i]notified[/i] of that thread, rather than messaged.
What do you guys think?
-
4 Replies in this Sub-ThreadIn terms of native Bungie.next functionality, I think your suggestion is the best way to solve this particular problem. A few positive 'howevers' occur to me, though: 1: It doesn't seem terribly difficult to implement an 'announcement' system that allows one way mass messaging, and replies on a one on one basis. If the intent is for one way messages, perhaps Bungie can sqeeze something like this in. 2: The ( hopeful ) release of the Bungie.next platform API may allow enterprising individuals to create a tool that would allow this. For the purposes of preventing spam, its distribution would have to be fairly tight ( by forum Ninjas, to forum Ninjas and group leaders, etc ). I know of a few guys here in #scripts I'm sure could put something like this together :)
-
Nah, I don't see how a user script could possibly work. Well, coup worked like that, so it's possible, but it would be SUPER slow.
-
Well yes, but that could be mitigated by sending the messages asynchronously, then notifying the sender when finished, rather than running synchronously. That would mitigate the 'slowness' of the experience for the user...
-
-
