Wednesday 13th of July:
I’ve changed some of the threading and the duplicate resolution behaviour. Previously the duplicate resolution was only considering the message text and the callsign, so if you wanted to re-spot yourself with the same message it would error out as a duplicate. APRS messages include a message number that increments with each message, so I’m now checking that as part of my duplicate resolution as well.

APSPOT will now also re-send it’s position information into APRS-IS once every hour to prevent it from becoming stale. It’s in the water near the Sydney Harbour Bridge as it’s running in AWS/ap-southeast-2 which is the Sydney region.

Monday 4th July:
We’re in the cloud! Now running on AWS ECS/Fargate with better connectivity/redundancy. I still have to implement better CI/CD around the product and a testing pipeline but it’s not running off my laptop anymore.

Turned back on sending messages with ack requests enabled to prevent a deduplication issue with some handhelds where if they’ve received a message with the same text they will assume it’s a duplicate and not display the message. I think this may have been causing some confusion issues for some wheres where they might send in the same request and then get the same text back and the HT wouldn’t display the message, appearing as if the system hadn’t replied.

Friday 1st July:
Fix bug where if a user requests WWFF spots and none are present the user won’t get a reply. If no WWFF spots are present in the system, a message will now be returned advising no current spots.

Added SPOT x: text to the spots return message so the users know which order the spots are in.

Thusday 30th June:
Fix bug with service disconnecting from APRS due to stale TCP connections. We now send in a status “comment” once per minute to verify we have connectivity to APRS-IS. If the TCP connection has gone stale this will force a reconnect of the service to APRS.