dustyData

I skim them all. The options I wrote are soft parodies of what each said. There’s a ton of problems with this model of governance, but I’m no voting member, so my opinion has no impact.

That said, it makes it so a single posture has to be voted on in its entirety, which is dumb (as some legislative bodies of the world have proven). As a result, nuance is erased alongside with any sense of ideological vision or compromise, and instead it promotes vagueness in every action and glacial institutions that break slowly break apart.

The very person who wrote the proposal that won reacted to winning with:

I regret the loss of contributors (which would have happened with either option winnign [sic]). It is just too early to take a final decision on the mater [sic]. Let’s revisit this in two years or so, and let this mess of a GR be a warning for our future selves.

The proposal was designed to win time without having to take any real stance while taking the smallest loss of contributors in the process. And thus it was written as the most milketoast nothing burger. When an infinite set of possibilities exists that actually do address real concerns like climate impact, social impacts, copyright and legal problems related to generated code, etc. in relation to the principles and overall values of the project. Instead, they are deferring the practicalities to pull request’s bickering.

But again, I’m not a voting member or contributor. So my opinion is null. I still think the way the process is designed and conducted is stupid and prone to cause the eventual failure of debian via governance collapse.

The Debian vote was so stupid:

Option A: Psychotic breakdown
Option B: Ethical impracticality
Option C: Political extremism
Option D: Two contradictory things at once
Option E: Something that doesn't prevent the other options but packaged with something nasty and unpalatable
Option F: Sensible but ultimately vague and action-less common place neutrality.
Option G: Nuclear option
Option H: Do nothing

It was such a brain dead exercise in futility.

Yeah, it’s going the be a whole ordeal. I will have to block an afternoon for the migration. Definitely not a “never breaks anymore” scenario. Everything can be broken, there’s no perfectly stable software.

Funny enough I had to rollback, since it doesn’t start in the latest version in my setup. I have to make a conscious effort to keep it one or two subversions behind. It is not the first time an upgrade breaks my install.

Right now, the latest update doesn’t run in my otherwise until now perfectly working environment. It’s frustrating because there’s no easy way to downgrade it in my setup.

Navidrome for service. Dsub2000 on android and feishin on desktop.

There, all your needs covered.

A VPS with a reverse proxy connected to your tailnet and a dyndns domain. It would be cheaper than Plex premium, you can use the vps for other stuff, and you have 100% certainty it will never ever show ads.

Yeah, that is the kind of concern for the service developer or a very opinionated sys admin. For self-hosting, few people will reach the workload where such a decision has any material or measurable impact.