Thatās just a standard thought in my mind for SOTA stuff⦠everyone seems to be so responsive!
I spent 35 years working in Tech⦠what I needed was all these SOTA apps people⦠instead I mostly got people who might get around to fixing a major fault in six months⦠.
Thereās now two options for monochrome and dark monochrome themes that build off the flatly theme, available under the settings gear (or should be once the build finishes).
If people want to suggest different colours, they need to go into their browserās web development tools (eg, on Firefox, the Web Developers Console (F12) ā Style Editor and play around with the css in there - thereās a 31 rule inline stylesheet that corresponds to the sheet for the spots page). Itās not nearly as simple to pick colors as it looks
Me too, I suggest to take the Sotlas color scheme as the default. That one is well designed and offers clear visibility. It is also well introduced. Thanks.
Probably it will be easier to just check for the words ātestā and āqrtā in the comment section and use them as the trigger. A special summit would be a way of handling it but as a programmer of many years who did a lot of Y2K work (wow 25 years ago!), I do remember the horror stories about old programs that used magic numbers to do things and the knock on consequences when modernising them. Typically it was COBOL programs from 60s onwards with dates of 99/99/9999 used to trigger things. Aside, I did write a COBOL āHello, World!ā program for an ICL 1905S in 1984 but I avoided the language luckily.
The main reason for just contemplating this a little is that SMS spots cost money to receive and so increasing the number of SMS received does has a cost. Itās possible that if every activation had a QRT spot added then the cost could rise noticeably. Iād like to get an idea of what that cost maybe first. (Spots to the UK and US numbers are to a US hosted service so are treated as calling party pays and receiving party pays, spots to OE, ON, I, ZL remote spotters donāt have this charge). Andrew alluded to the fact that part of the update work lowers costs⦠not immediately as we keep some stuff running in parallel for the old API. We are possibly looking at removing 4 servers, 1 load balancer on our primary cloud system and a very expensive DB server on Azure over the coming months, a noticeable saving. So I donāt wont to go increasing the cost and spending more of your money without some research first.
But then it does not collate in a meaningfull way as seen in my screenshot example.
The spot before the QRT should not be in the list I guess as it got superseeded by the QRT spot.
Iāll have to look at the logic. i think it collapses any spots that are the same summit and callsign in order. I donāt think it goes all the way down the list and collapses everything, like a threaded view
Iāll have to check but I think my Lebara mobile doesnāt charge for texts to those countries so I could use one of those SMS gateways and SOTA wonāt have to pay.
If you can do that then why not. Iāve sent more SMS to test the system than using it in the last few years as my 4G internet connection seems to work everywhere in the UK. It was really solid all over Assynt the other week which surprised me considerably.
Posting an alert from a summit page doesnāt work (Submission failed: [object Object]). I think it may be because the Posted by field is empty and there is no way to enter anything there.