I have to wonder:

What if Muse did "Hello people. We are adding Telemetry to Audacity. It is a compile time option to enable/disable it, but our binaries will have it on by default" would have as much impact as "We added Telemetry to Audacity. Also, the code is ours. Suck it."

@juliobiason that's the thing, isn't it?

If they did the former, I for one would at least consider the option of them potentially being trustworthy and expected not to abuse that trust and misuse the private data.

The way it went down? Nope. Heavy techbro startup vibes, I don't want that anywhere near my data and FLOSS projects I use.

Follow

@rysiek

Heavy techbro startup vibes

You know what, that hits me pretty hard.

I mean, I remember the time when GPL was v2 and we all talked about "no vendor lock in" and "give the source to the user" and "anyone can learn from it" and all that fuss...

But now... "Open source" appears to be more like another thing to be bought and carried with its users and what not by those who have the money to take that as theirs.

And that's incredible sad.

@rysiek @juliobiason

The thing I've learned is that OSS isn't just the license; it's also the developer community.

Chrome (e.g.) isn't *really* OSS despite the license because the entire dev team consists of Google employees who can't (easily) vote with their feet and the project is too big and safety-critical to easily fork.

(TBF, the OSS license *helps*; node.js was extracted from Chrome.)

@suetanvil
Yep, open-source that doesn't accept outside contributions or only does so under a CLA, is often comparable to source-available, because they can re-license at any point.

Sure, in theory a community can fork the last open-sourced code, but in practice that rarely happens, since you essentially have to compete with a professional dev team.
@rysiek @juliobiason

@suetanvil
There is one caveat to that "community-developed == good" theorem, though, which is precisely Audacity.
I thought that was one of those projects that's safely in the hands of a community.

I guess, it's the exception rather than the rule, but yeah, I still found it concerning.
@rysiek @juliobiason

@friend @suetanvil @rysiek @juliobiason I think this is once more a demonstration why complexity cannot be underestimated as risk. Even a once healthy community can be poisoned by even a single individual, and if the project is too complex and large to effectively forked... there you go. Small, simple tools which interact well, I've heard entire OSes have been designed from that philosophy.</riding hobby-horse>

Sign in to participate in the conversation
Functional Café

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!