jks

Well that's pretty strange. As mentioned in the v1.688 thread the most recent changes (including v1.687) were very simple and should have only effected stuff completely unrelated to spot uploading.

Here's a 70+ post thread from the wsprdaemon forum describing how the wheels are falling off wsprnet.org (again) https://groups.io/g/wsprdaemon/topic/problem_uploading_spots/106716937?dir=asc

I'm going to give them some time to sort out their mess before I look at it.

I had started looking into integrating various Fldigi decoders in a Kiwi extension. But that work got sidelined by more important tasks (only so many hours in a day). I got as far as getting RSID working. Wanted to work on MFSK next. And also replace the CW and FSK decoders we have now with the better Fldigi versions.

Well, that's why I said "probably".

The day any of this nonsense starts to impact me is the day I shut everything down.

Alright. After a barrage of emails I've implemented a new checkbox on the admin config tab that says "Show user names to user connections" The default is checked (i.e. yes, show the user names). It will be available in the next release.

No matter the setting the user names will continue to be shown on the admin users tab, admin log tab etc. This setting compliments the existing checkboxes controlling whether geolocation information is shown and if the geolocated city is shown.

And this is all independent of whether a user name is demanded at all as set by the checkbox on the admin control tab.

There is currently a bug where certain non-ASCII, non-UTF8 user names formed by using the Kiwi API directly causes the admin users tab to disappear even though it should have valid entries. Fix coming in the next release.

Well, none of this is really new. It's just operating in the modern context of SDRs and the Internet.

Hams have been "bootlegging" callsigns for nearly 100 years. Pirates have always existed.

Most countries technically have regulations allowing radio monitoring for personal use, but prohibiting "retransmission". But the precise interpretation of those terms for HF are vague at best given the border-crossing nature of HF. And HF is mostly uninteresting to everyone except us anyway.

Much more applicable to VHF/UHF short-range communication services that might be impacted by retransmission. Although encryption in recent times has made that point mostly moot.

To your last point: I don't think it makes any sense to be including, on a public list, any Kiwi that requires a password likely to be unknown by 99% of the users connecting. That makes its inclusion completely worthless. Perhaps a separate area listing "private" access Kiwis? But that doesn't seem worth the effort.

No. Didn't want to make things quite so easy for China.

We've received another run of boards. Assembly, programming and test are in progress.

One issue is that a huge quantity of the enclosures we had shipped by cargo container instead of air freight. But due to bad weather the container was delayed. So the finished units won't ship until later this month (June).

Where's Rodney Dangerfield when we really need him?

Okay, I can take out the newline chars in the next release. If it breaks any other programs then I can add an option to include the newline or not.