Transcript detail
Loading...
Public transcript context with linked callsigns, related nets, and analysis metadata.
Transcript
Public transcript text
Hey, good morning to you, good morning to everybody on the net. Sorry for the little delay there. My repeater felt it necessary to ID and nobody heard it. Man, I'm telling you, in the past couple of weeks we've had a station out of the Caribbean who connects their repeater to drop in and it's, oh man, it's the worst configured system I've ever heard in all my days of doing ham radio I think. It puts its CW identifiers over the air, it shouts the time once every hour, and it's the time in the Caribbean, you know, not relevant to anyone anywhere in North America. And it makes a ton of noise, it's just interference coming out of it left, right, and center. So I've finally, after sending three emails, I finally blocked it, only for it to come on again and connect via All Star. So I blocked it again, sent another email, and now they're starting to connect through other users to get the do drop in that way. So I'm wondering, what can I do about this because I can't block it on every All Star node connected to everybody that uses the system. That's just impossible. But they're a very, very problematic station. It makes a lot of noise, it interferes with nets, it causes loops, it keys up after every transmission. It's just, it's so ill configured that I've never seen anything quite like it. You know, when you're linking a system to a busy network, you definitely don't want to have your CW identifier or your time or your local weather, any of that stuff going out over the system. I mean, it's common courtesy. And if they just don't know how to configure it, well, I was offering to help with that, but they never respond to any emails. So I just don't know. Let me reset one.
Explore