[Dxspider-support] For all sysops

[Mike McCarthy, W1NR]

I would suggest that we all step back and pause a moment. Blindly 
disconnecting nodes is not good policy especially on one of the most 
heavily used weekends on the calendar. This just angers people. Before 
you disconnect someone have you personally tried to contact the affected 
nodes sysop directly?

W1NR

On 2/19/2023 8:30 AM, David Spoelstra via Dxspider-support wrote:
> Kin-
> 
> Thank you for your email and thank you for all your work. I've got a few 
> questions and suggestions:
> 
> 1. By your own admission, the method of determining versions seems 
> flawed. Maybe we find a method that works 100% before we send out more 
> block lists?
> 2. Are we going to send out unblock lists, or only block lists? Maybe we 
> can get this automated somehow? Do I need to personally go to all my 
> users (who have all left to other nodes since they are contesters) and 
> the nodes I was connected to and convince them that I'm no longer blocked?
> 3. The first date I can find on this reflector with a block list with my 
> node on it was Feb 17. It's Feb 19 today. I only have time for ham radio 
> on the weekends. Before I could even read the reflector email, I got a 
> call from a user on my node that I wasn't getting any spots. Maybe we 
> could give people a week or two (especially if there is a big contest 
> like ARRL International DX CW this weekend) to respond if they see 
> themselves on a block list before they get blocked?
> 
> Also Kin, thanks for your offer of connecting to your node. But all my 
> users are contesters and they have left me for W9YB (an AR-Cluster) 
> since my cluster stopped getting spots during one of the biggest 
> contests so I'll probably be taking my cluster down and using W9YB 
> myself. Sad since I see my cluster has been on 24x7 since Nov 1, 2010 
> "DXSpider V1.55, build 0.82 (git: b7512d7) started".
>