search

wavelog / wavelog

Webbased Amateur Radio Logging Software - Log your contacts from everywhere!
https://www.wavelog.org
MIT License
158 stars 40 forks source link

Feature Request: Add Button to Report New Spot to Cluster Server #932

Closed besynnerlig closed 2 months ago

besynnerlig commented 2 months ago

Feature Request: Add Button to Report New Spot to Cluster Server

What Feature is Missing?

It would be a great enhancement to add a button on the page for adding a QSO. After entering a callsign, users could report a new spot to the cluster server with just one click. The feature would use the newly entered callsign, frequency, and traffic mode to automate the spot reporting.

Why is This Feature Important?

This feature would streamline the process of reporting new spots to the cluster server, saving time and reducing manual input. By integrating this directly into the QSO logging process, users can quickly contribute spots while logging their QSOs, enhancing the overall user experience and workflow.

Is This Feature Personal or Beneficial to Others as Well?

This feature would benefit the entire Wavelog community, particularly those who regularly report spots to the cluster server. It adds a valuable layer of efficiency for all users who engage in both logging and spotting, making the software more versatile and user-friendly.

int2001 commented 2 months ago

Wavelog is a tool which runs on your websever (or at a hoster) and provides a logbook (and cluster) to many users. Most DXClusters do not have any kind of authentication. You simply login via Telnet and post your spots.

All on a trustlevel with only a Callsign.

if we put a spot-function into wavelog, all spots would come from the IP of your WL-Server. That means: If someone is doing evil things (e.g. spotting everyone he sees on FT8) with that, your instance/IP will be banned very quickly on the Cluster.

This is (one of) the main reason(s) why we decided not to implement a spotting-function within WL.

Maybe this changes one day, when clusters are more secure. But currently it is readonly.

besynnerlig commented 2 months ago

Thank you for sharing your thoughts on implementing a spotting function in Wavelog. I understand that the main concern isn't that shared servers inherently increase the likelihood of abuse, but rather that a single user's misuse could lead to the entire server's IP address being blacklisted.

There might be potential solutions to mitigate this risk. For example, if spots could be forwarded directly from the user's web browser to the cluster network using secure methods like HTTPS, and if the cluster network provides a defined API for spot submissions, the spots would originate from the user's own IP address instead of the server's. This approach depends on the availability of such APIs from the cluster networks, which likely exist.

Additionally, if someone intended to abuse the cluster network, they would probably find more direct and efficient methods than using a logging program. It's possible that this kind of misuse isn't a significant issue in practice.

Perhaps the ability to send spot reports could be made optional and configurable on a per-server basis, allowing server administrators to enable or disable the feature according to their specific circumstances and trust levels with their users.

I appreciate your careful consideration of these concerns. Maybe in the future, as cluster technologies advance and offer more secure options, this feature could be revisited. Thank you again for your dedication to improving Wavelog and for engaging with the community's suggestions.

int2001 commented 2 months ago

Happy to help. Would be very nice if you can share informations about a Cluster which provides a https-API for End-Users.