Feature requests for multi-multi

[ki4mcw]

A couple of feature requests related to multi-multi operation. Some of these may be transferable from fdlogger/fdserver:

• Number 1 with a bullet: please keep up the great work on N1MM packet comms! Cross-platform unified logging across multiple stations would be game-changing!

• Please add same-band/mode detection and message passing for connected stations.

• Please include Operator in the log, and in the log viewer. I think Station is already in there, but not sure how to change that.

• Please add a "statistics" type view for showing Qs per Operator per band.

Thank you for all that you are doing!

Rob KI4MCW

[mbridak]

Currently writing the aggregation server.

[aknrdureegaesr]

Please support the following use case:

• The ops bring three computers to the contest station.
• Two are hooked up to a transceiver each and to talk to each other, running not1mm.
• The third computer remains switched off and in storage.
• After hours of happy contesting, at 2 in the morning, coffee is spilled on one of the computers so it immediately stops functioning.
• The third computer is switched on and hooked up in its place.

Wanted features:

After some brief interchange with the other computer that has been part of the game the whole time, all QSOs, multi information, and what have you become available on the replacement computer. In summary, it serves as a full replacement of the broken one. Neither functionality nor data is lost.

As far as I know, n1mm does not get this right. Again, as far as I know, it solves the "CAP theorem" problem by using the original computer, the one with which some QSO was originally logged, as the "single source of truth" for that QSO. If that computer is lost and/or replaced, bad things start to happen. The n1mm documentation specifically mentions this cannot be done. If I understand it correctly, a computer entering the network anew can only learn about a QSO as long as the original ("single source of truth") computer is still available.

[mbridak]

Yup, Already been thinking about this.

The logging computer will be able to ask the server to send back all the q's it has.
As long as you name the logging computer the same as the lost device you should be fine.

Like wise, if the server dies you will be able to spin up a replacement or run an instance on one of the clients computers if you have no spare computer and all the clients will be able to resend all their Q's back to the new server.

[mbridak]

Update

• Added Cabrillo generation
• Group chat
• Current User/Band/Mode
• QSO by band/mode/points
• Serial Number server
• Dupe checking

[mbridak]