Discord: Difference between revisions

Line 113:

* Members are urged to use @everyone rather than @here, as users not currently online on Discord may wish to still receive push notifications so that they can log on to the game for content that interests them. Members are free to make use of the EVE University Auth's [https://auth.eveuniversity.org/fleetpings/ built-in ping tool], which allows you to send out a ping in a channel of your choice and include additional information such as form-up time, location, any possible fleet doctrine, and some free-from text information of your choosing.

* Once the initial ping has been sent, followup conversations regarding the pinged content are to be had in a thread attached to the ping message. Users can create a thread by right-clicking the ping message and selecting "Create Thread". Often, this will have already been done by the person who sent out the ping. Questions and conversation can then move to this thread.

* [In all ping channels but #ping-class] Once the initial ping has been sent, followup conversations regarding the pinged content are to be had in a thread attached to the ping message. Users can create a thread by right-clicking the ping message and selecting "Create Thread". Often, this will have already been done by the person who sent out the ping. Questions and conversation can then move to this thread.

* Pings should be informative enough so that they do not require multiple pings for the same topic. If you need to use multiple lines, type them out before you send the message. Each message sent will notify individuals on their mobile, desktop, and/or emails; do not abuse the pings otherwise individuals will just turn them off.

@@ Line 113: / Line 113: @@
 * Members are urged to use @everyone rather than @here, as users not currently online on Discord may wish to still receive push notifications so that they can log on to the game for content that interests them. Members are free to make use of the EVE University Auth's [https://auth.eveuniversity.org/fleetpings/ built-in ping tool], which allows you to send out a ping in a channel of your choice and include additional information such as form-up time, location, any possible fleet doctrine, and some free-from text information of your choosing.
-* Once the initial ping has been sent, followup conversations regarding the pinged content are to be had in a thread attached to the ping message. Users can create a thread by right-clicking the ping message and selecting "Create Thread". Often, this will have already been done by the person who sent out the ping. Questions and conversation can then move to this thread.
+* [In all ping channels but #ping-class] Once the initial ping has been sent, followup conversations regarding the pinged content are to be had in a thread attached to the ping message. Users can create a thread by right-clicking the ping message and selecting "Create Thread". Often, this will have already been done by the person who sent out the ping. Questions and conversation can then move to this thread.
 * Pings should be informative enough so that they do not require multiple pings for the same topic. If you need to use multiple lines, type them out before you send the message. Each message sent will notify individuals on their mobile, desktop, and/or emails; do not abuse the pings otherwise individuals will just turn them off.