Post #1873791
2026-02-21 08:52 UTC
@vk6flab #FT2
However, one could contend that, if the modified WSJT-X shares complex data structures or intimate memory spaces with the FT2 encoder-decoder, it is a derivative work. In this case, the proprietary #FT2 "plugin" must be open-sourced, or the developer is in breach.
What would be "acceptable"?
(3/5)
Replies (1)
-
@Ea5iyl@mastodon.radio 2026-02-21 08:55
@vk6flab #FT2 * If the modified WSJT-X software communicates with the proprietary FT2 encoder/decoder via a formal, documented interface (like a pipe, a socket, or a command-line argument), they are often considered separate programs. * If Martino and colleagues added a generic plugin architecture to WSJT-X that could be used by anyone writing "plugins" similar to the one they wrote FT2, and then happens to use it for their proprietary tool, it would be harder to prove a breach. (4/5)