jks

Lol. I don't even remember how this stuff works anymore.

So kiwirecorder has a new option "--tlimit-pw" ("--tlimit-password") to specify the time limit exemption password. That was easy. No server changes required (for a change).

What was interesting was that I found an old exemption mechanism in the code that I had forgotten about. It doesn't use a password. I must have put that in there when people were complaining about their kiwirecorder sessions being disconnected (on a time-limited Kiwi) before exemption passwords were implemented. But a hacker who discovered this mechanism could use it in an injection session to get unrestricted browser access, which is exactly what you are seeing.

So the next release will remove this old mechanism and people will have to get the actual password from the Kiwi owner for making long recordings that exceed the time limit (if configured).

After checking a few things I ran the build manually. It resumed compiling files in the middle of the expected sequence. Like it had gotten stuck or interrupted previously. The build took a long time because v1.364 did not yet cache DRM compiles.

So I don't know what went wrong. Seems to be fine now.

Even with the majority of the DRM compiles cached these recent updates take a bit longer than before. Please be patient (although if it's been more than an hour something is wrong). Also, if your Kiwi knows its timezone then updates will now occur in the window 1AM - 6AM local time instead of UTC as before.

@Jim v1.369 fixes this problem: If a Kiwi was registering on sdr.hu then when decoupled registration was introduced in v1.365 I forgot to also set registration for kiwisdr.com/public. That's why there are so many purple (inactive) markers on the http://rx.linkfanel.net map currently even though they are actually active (they still respond if you click their map markers). Once they all update to v1.369 the map will return to normal.

Yes, in the next release the DRM button will be properly disabled (greyed-out) when DRM is disabled.

Yes, SAM (synchronous AM) is a placeholder. I figured people were going to be upset enough when I changed the mode buttons (they were) that I better only do it once. Even if it meant using placeholder(s) for anticipated future changes. Depending on your browser if you hover over SAM a tooltip should say "not yet implemented".

When one channel is running DRM today's v1.367 release allows the other channels to connect (audio and waterfall), with the limitation that they cannot use any extensions. This is because the Beagle cpu processing requirements of most extensions might be beyond the point needed to support DRM. This condition might be relaxed in the future as more improvements to the DRM code efficiency is made.

You can limit the number of non-DRM channels allowed to connect with a new setting available on the DRM sidebar of the admin "extensions" tab.

The code to detect and enforce these conditions was tricky to write and it is quite likely that there are problems remaining.