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 outbound TCP connection to play a local file from my local disk?!?! The answer was in the source. It is called telemetry. Back then when I used mp3blaster we used to call this spyware, but the times had changed since then.

▲

senko 3 hours ago | parent | next [-]

Back in the day I used to use mpg123. It's still available, but most of the time today I use mpv (successor to "mplayer", handles video too, opens a separate window, zero chrome) or ffplay, since they have wider format support.

No playlist or even file management - they do show id3tags, that's about it. No telemetry, SaaS chicanery or "improvement" upgrades every few days, either.

▲

samplatt 9 hours ago | parent | prev | next [-]

The times haven't changed. It's still spyware, it's just been normalised.

▲

liendolucas 6 hours ago | parent | prev | next [-]

You can still set up an mpd server: https://www.musicpd.org/ that runs on your local files.

▲

tosti 9 hours ago | parent | prev | next [-]

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

▲

GrayShade 3 hours ago | parent | next [-]

It's gone: https://github.com/bjarneo/cliamp/commit/085734a86343a80176d...

▲

taneliv 2 hours ago | parent | next [-]

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.

	▲	stavros an hour ago \| parent \| next [-]
		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.
	▲	kgwxd 15 minutes ago \| parent \| prev [-]
		Opt-in via extension, fine. Opt-in via flag, unreliable. The spyware code should never be anywhere near the main codebase.

▲

tosti 2 hours ago | parent | prev | next [-]

Yay! Also, I hadn't noticed an entire section about building from source. Sorry about that. Good work!

▲

blamesoft 2 hours ago | parent | prev [-]

Woo, good on them

▲

userbinator 6 hours ago | parent | prev | next [-]

No personal data is collected

IP address (which can be geolocated) along with a unique identifier is not considered "personal data"? This is basically a tracking cookie. It also seems to use HTTP, which is itself widely fingerprintable based on what request headers it sends.

▲

gesis 9 hours ago | parent | prev | next [-]

There's a config variable and a cli flag to disable.

That seems reasonable to me.

	▲	userbinator 6 hours ago \| parent [-]
		to disable All such surveillance behaviour should strictly be OPT IN.

▲

Habgdnv 9 hours ago | parent | prev | next [-]

I saw it, it is NOT spyware. It just sends a random UUID. It is just a personal disappointment for the fact that it is something so simple as a console player and yet connects somewhere. But that's just me. I grew up in other times.

Also I just compiled mp3blaster and I am listening to it again. So cool!

▲

9 hours ago | parent | prev [-]

[deleted]

▲

8 hours ago | parent | prev [-]

[deleted]