31–40 of 51 posts
Earlier quoted context omitted.
It's gone: https://github.com/bjarneo/cliamp/commit/085734a86343a80176d...
Thanks for pointing this out, to me it seems quite a good response. I wouldn't mind opt-in telemetry, but possibly the participation rate would be too low to make use of it.
I remember with nostalgia the mp3blaster. I spent years listening to it in my terminal. At one point I used only cli without graphical desktop on slackware and one of my TTYs was dedicated to it. Turns out these times are forever gone - never to come back. The huge disappointment when I tried this on the first run to play a mp3 file from my local disk and it initiated outbound connection. Why a local CLI player needs…
Winamp was pretty cool. When I switched to Linux, many years ago, I wanted to have winamp too. I think I used bmp for a while until it died; before that xmms but that one also sort of died. Meanwhile some other GUI showed up, I forgot the name. I kind of gave up on winamp, mostly because my use cases shifted. I went to mplayer, then mpv, and now I am too used to using mpv for literally anything related to audio and v…
XMMS lives on as Audacious: https://audacious-media-player.org/ You can still configure it to look like XMMS.
..and XMMS2 apparently had a few recent releases https://github.com/xmms2/xmms2-devel
https://github.com/tramhao/termusic
The not so good parts are 1) it is written in Rust and therefore packaging is awful with a lot of dependencies; 2) it repeats playlists by default with no option (so far) to turn that off. But there's an issue open on it and it looks like this is going to be fixed.
Earlier quoted context omitted.
Thanks for pointing this out, to me it seems quite a good response. I wouldn't mind opt-in telemetry, but possibly the participation rate would be too low to make use of it.
My issue with telemetry is that 99% of software ends up not using it. Why have it? And definitely don't have it by default. Your users will come tell you what they want, making telemetry useless, especially when it's an OSS project you're mostly building for yourself.
Telemetry on by default in a CLI app seems very weird
Like others the telemetry is hugely undesirable nor necessary. Likewise if they truly don't collect your IP as they claim it's just ripe for endless abuse.
Like others the telemetry is hugely undesirable nor necessary. Likewise if they truly don't collect your IP as they claim it's just ripe for endless abuse.
If you just want to say "like others", you could simply upvote one of the other comments? Anyway, looks like the telemetry has been removed due to popular demand: https://github.com/bjarneo/cliamp/commit/085734a86343a80176d...
Have a great day!
Earlier quoted context omitted.
My issue with telemetry is that 99% of software ends up not using it. Why have it? And definitely don't have it by default. Your users will come tell you what they want, making telemetry useless, especially when it's an OSS project you're mostly building for yourself.
Except that telemetry can give you more complete (and foolproof) information than what users report. But yeah, that could also be solved by having debug info that users can attach to their report, the app doesn't have to "call home" for that...
Earlier quoted context omitted.
OIC: https://github.com/bjarneo/cliamp/blob/main/telemetry/teleme... Should be easy to nerf, but the build instructions are kinda vague. Clone, and then what? Something like "go build" or something I guess. Looks cool though
It's gone: https://github.com/bjarneo/cliamp/commit/085734a86343a80176d...