While I think that this would be interesting to know as a developer, I’m not sure what the justification would be. A compromise could be opt-in anonymized analytics vs. turning it on by default. I suspect that also many instances of libretime wouldn’t want to advertise their URL etc as it is often times not-intended for public consumption.
TL;DR: LibreTime should not have usage counts, analytics, or any other form of phoning home.
One of the reasons I use F/LOSS is to avoid the surveillance that commercial software imposes. Transmitting data about my installation just because “it would be interesting” to developers opens a whole can of security and trust issues. Additional software that transmits data is just another bit of software that can go wrong.
What is the benefit to me? To my radio station? I’m wary even of error reports that are sent automatically, even when the data dump is available to me for inspection.
LibreTime already has effective, open communication between users and developers (this forum, Mattermost, Github, maybe other forums I don’t know about. There’s no need to bake in surveillance when there are already so many other means of communication available.
Instead of baking in remote surveillance, let there be robust and comprehensive logging of everything, then if developers want to see how LibreTime is used they can ask the admins of LibreTime installations to send them copies of the logs.
 For security and audit purposes, I would really like to see a log of user activity. Who logs in and when, both WebUI and streaming, what activities they carry out, what tracks they upload, edit, delete, &c. (but I want to install an up-to-date version of LibreTime before making any Github feature requests)
you seem to be arguing against a very large data collection system that I am not even considering and some of the words/comparison you are using are a bit extreme with regards to what my proposal actually is about (e.g. ‘remote surveillance’, ‘commercial software that imposes’).
I understand your position, and I agree. I don’t want to force anything on the users, so this feature will be opt-in (disabled by default), and does give you the choice not to participate.
Obviously, the code for this feature will also be open source.
If we only want to consider you or your radio station in the whole community, and remove the maintainers and contributors of the project from the equation, I would say that on the long term, giving feedback to the maintainers will help them improve, make educated guesses and better plan their work for the software you are using.
Having feedback from the community can give the maintainers/contributors some more motivation.
But again, we are collecting a very small dataset (please see the ticket on Github), and I am happy to remove some of the data because we consider them too private/sensitive (users/files/playlists count).
What I am proposing is closer to debian’s popularity contest system (we collect even less data than popcon) than the system you are describing. This is not about gathering logs/error reports/metrics/…
I made a survey once and it took time, and I am not sure I have the time/energy to do such survey over and over. Users might not be aware of those surveys, nor have to time to answer them. So instead of using a survey to know which distro and LibreTime version you are using, I though we could automate the process.
Again “surveillance” seem to be too strong, when I only want to gather the versions used in your installation of LibreTime, and maybe some usage stats. And again, this is an opt-in feature.
This is unrelated to my proposal, we won’t collect any logs/error reports/metrics/… Please see the Github ticket to get an idea of what I want to collect.
If someone is against my proposal, I understand and am open to discuss or close this proposal, but please don’t be against an hypothetical “forced remote surveillance system” that I am am not proposing.
I support the idea of having something like Debian’s popcon in LibreTime. We do need to be very transparent about what would be transmitted and how. Also I strongly agree with it being opt-in, maybe a question at install time resulting in a flag in the config file?