Good point, KC9SIO.? And, it kind of leads to why I'm requesting a way to block the user. Based on other comments here, I have sent polite emails to both folks who are connecting and spamming our ratflector asking them to both stop sending us their QSTs.? If they respond, problem solved!? If they don't understand me or don't care, I've still got a problem.??
We typically use the ratflector as a "back channel" for communications during events. We actually used it for a "hospital move" one time where all the patients at our small town hospital were moved to a new hospital.? In that case, EMA specifically asked that we use DRATS to track and log the movement.? Of course, no PII or HIPAA sensitive data was used.? The communication was along the lines of "Patient A456892 loaded onto ambulance 123. Ambulance 123 enroute.? Ambulance 123 arrived at ___".? In the end we had a complete log of every patient moved with accurate time stamps.? Lots of ways to do that. EMA asked us to do it with D-RATS.
If we are asked to use it in a situation like that and we're getting Portuguese weather bulletins blasted out in the middle of our event, it doesn't help.? And, in that situation, I don't have time to wait for the polite email method.? I'd like to be able to quickly (even if temporarily) black list the individual to get them out of the way.? ...without relying on everyone to filter him out correctly during the event.
Dan Ozment