OK, I understand your concerns OM Irad. However, in practice I have seen time and time again, many VARAC users simply do not send beacons; thus you do not know that they are QRV. But anyway, it was just an idea.
I see a risk for frequency "Abuse". If many will shout out this call it will create a mess on the freq... as we have a single QRG unlike JS8. I believe a beacon is a good mechanism that utilzie the frequency in a better-not-clogging way. I understand once need to sit on the freq for at least 15 minutes to see who he can hear.
But lets hear some more thoughts and idea around that from other members in teh community.
Irad has a very valid point here. JS8 uses a large freq domain to send it's heartbeats. VARAC uses the one center freq, as Irad has pointed out.. The programs go about their ways in a different manner and that is inherent in their coding. While I too think that JS8 makes it easier to see who is hearing you... it is not an unsurmoutable problem. For instance, If I need to establish if Irad is there, even though I have not seen a beacon from him, I will ping him.
Granted, not as straightforward as JS8 does it, but... in fairness to VARAC, it has so many extra nice features that I consider it a small price to pay.
This is my own person opinion and of course others may disagree.
OK, I understand your concerns OM Irad. However, in practice I have seen time and time again, many VARAC users simply do not send beacons; thus you do not know that they are QRV. But anyway, it was just an idea.
I appreciate your work and THANK YOU for it
Hi Franz.
I see a risk for frequency "Abuse". If many will shout out this call it will create a mess on the freq... as we have a single QRG unlike JS8. I believe a beacon is a good mechanism that utilzie the frequency in a better-not-clogging way. I understand once need to sit on the freq for at least 15 minutes to see who he can hear.
But lets hear some more thoughts and idea around that from other members in teh community.