You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been asked if it would be feasible to apply a kind of role filtro, so we avoid receiving inappropriate questions in the live interventions during the assemblies. Could those questions be previously eliminated by the NA team before they are visible to the rest of the attendees, so we can have more control over the questions asked during the assembly?
On the other hand, I have been asked if it would be possible to remove the emojis during the round of questions, or keep it as something optional, as the ESN Spain team is concerned that in this way the speaker may be put under too much pressure with certain questions that may be controversial.
GA CT perspective
...I will bring the GA CT’s perspective, hoping it will be useful in designing these requirements. Starting from the second request: emoji are keyboard characters, so yes, they could be potentially filtered out; but, since the standard is changing quite often (and new emojis are appearing every day), it may be a time-consuming activity to keep up with this kind of automatic filtering. Instead, we could tackle this issue through the first point you raised, i.e. having the option to let the CT approve questions and appreciations before they are added to the public view (to filter out the inappropriate or controversial ones). The downside is that it would add burden and extra work to the CT: while managing the assembly, they’d also need to keep up with the approval of everything being posted. As GA CT, instead of choosing preemptive filtering (i.e. extra work), we decided to implement the “ban” feature: whenever we see an inappropriate message, we can delete it indefinitely and ban the user that posted it, preventing new messages from being posted — of course, this feature doesn’t work on anonymous appreciations (that can anyway be disabled). Finally, the app already supports some roles filtering, even though we are not sure it would cover your scenario (but it’s good to know): for each topic, from its configuration, you can restrict the ESN Account roles that are able to post a new question/intervention/appreciation.
The text was updated successfully, but these errors were encountered:
ref. email thread: Assembly app implementation - ESN Spain
Requests
GA CT perspective
...I will bring the GA CT’s perspective, hoping it will be useful in designing these requirements. Starting from the second request: emoji are keyboard characters, so yes, they could be potentially filtered out; but, since the standard is changing quite often (and new emojis are appearing every day), it may be a time-consuming activity to keep up with this kind of automatic filtering. Instead, we could tackle this issue through the first point you raised, i.e. having the option to let the CT approve questions and appreciations before they are added to the public view (to filter out the inappropriate or controversial ones). The downside is that it would add burden and extra work to the CT: while managing the assembly, they’d also need to keep up with the approval of everything being posted. As GA CT, instead of choosing preemptive filtering (i.e. extra work), we decided to implement the “ban” feature: whenever we see an inappropriate message, we can delete it indefinitely and ban the user that posted it, preventing new messages from being posted — of course, this feature doesn’t work on anonymous appreciations (that can anyway be disabled). Finally, the app already supports some roles filtering, even though we are not sure it would cover your scenario (but it’s good to know): for each topic, from its configuration, you can restrict the ESN Account roles that are able to post a new question/intervention/appreciation.
The text was updated successfully, but these errors were encountered: