I find it incredibly surprising that many #FOSS or #FLOSS folk take the 0th pillar's "freedom of use" to mistakenly mean "freedom of usage by creating a software feature" instead of the true intended meaning: "freedom of usage under the license conditions".
Because that's what RMS has always been about: the software licenses being symmetrical in power between the distributor of software and receiver of software. It creates a level playing field in terms of what "politics" are contained in the software.
Because that is the core of Software Freedom/Liberty: the right for a Person to take a software that expresses a [political] view they disagree with, obtain a copy of that software with equal capability as the distributor, modify that [political] view to be more amenable, and then redistribute it without any additional licensing burdens.
It's never about what specific views or capabilities are in the software itself. Heck, you could fork and purposefully add bugs and it is still no less Freedom respecting.
So trying to argue the 0th pillar "freedom of use" is about specific software capabilities is mistaken. It's a gateway to the un-reconcilable "well N users demand my software have feature X, and an equal number also demand an incompatible feature Y." How could one ever satisfy the 0th pillar under this condition, and why would RMS never discuss this situation?
Perhaps because it is the wrong interpretation. :) RMS spends time at the "licensing level", not at the "what does your software do exactly" level.
@cj while I agree in principle I think it's murky territory to conflate what Tusky did vis-a-vis Gab with implementing a feature or not. If Tusky removed boosts for everyone the freedom of use is respected: anyone can use Tusky to do what Tusky is designed to do. If they removed boosts only for left-handed people then freedom of use is infringed because not everyone can use Tusky the same way.
That said, I use Tusky and I think Gab should be de-federated.
@cj it isn't about what features the software has, but rather if one can get the software binary, then they are entitled to the source as well, per the license. Gab could for Tusky, call it "Gab mobile," then patch out the block mechanism. They could distribute "Gab mobile." That is how the license is supposed to work, right?
@cj I think you're straining at the gnat & swallowing the camel. I can accept the arcane points stated here about FOSS, maybe Tusky is still FOSS "free". I think we're missing the big issue: Many saw the toots trying to pressure instances to ban gab, apps to ban gab, egging on monopolists Google & Apple to ban the "bad" apps. People can see that this was an attempt to collude & deny freedom to Gab users. People see through this FOSS side debate to the issue of real freedom
@AndreiRublev1 I disagree. The Freedom and Rights granted to users by FLOSS is just as real as other Freedoms/Rights such as free speech of users, free speech of developers, the right of association, right of privacy, etc.
I think, and maybe you do too, that it is a balance of these rights that are needed. Not demeaning one set (FLOSS) as lesser.
I still think that the FLOSS Freedoms will allow determined hate speechers to circumvent any code bans, preserving their Freedom.
@cj Not demeaining one set as lesser. Think of it like this: Suppose the anti-Gab campaign had been totally successful. The result would have been a complete crippling of Gab (oddly by, in part, partnering with anti-freedom big tech). Can you see that people would think it very hollow and inconsistent to read arguments from groups touting FLOSS freedom, yet many of those same groups had in practice acted to severely deprive those people of their freedom to use Gab?
@cj Had the anti-Gab campaign been a total success, I think ordinary people looking at this would rightly wonder: "What good is FLOSS freedom when many of these same groups colluded to deprive Gab users of their freedom to use Gab? Where is the consistent commitment to freedom? It does not make sense to, under the cover of FLOSS freedom, deprive Gab users of their freedom. Why do some say it is fine to use one freedom to deprive others of another freedom?"
@AndreiRublev1 I don't think your premise is possible: users can still always used forked software. Just means there will be two Fediverse that refuse to communicate with each other, or have sparse bridges. And the cultural/societal force pushes people to the non-hate-speech less-potential-real-world-violence outcome. That's a feature and morally good outcome in my book.
Gab can't ever get kicked off the Fediverse. No deplatforming. They can be isolated to wallow on their own.
@AndreiRublev1 And again you keep using the "FLOSS Freedom" meme that has been repeatedly debunked. Regardless of their isolation, Gab users always have and retain their FLOSS Freedom. It's just other Freedoms like association that let people isolate Gab. No hypocrisy with FLOSS Freedoms just different values for other Freedoms. The balancing act between freedoms and rights of different people.
@cj Sorry, not sure what you mean by the "FLOSS freedom" meme. I only use that term truly and simply because I don't know how else to describe the freedoms inherent in FLOSS as part of a 500 character limit toot! ;)
@cj Well, you are adressing how things would likely play out (I think you're right); my point is about the mindset motivating those who attempted to ban Gab, who touted the FLOSS freedom of apps that were made to ban Gab while hoping thereby to deprive Gab users of their freedom to use Gab.
@AndreiRublev1 Please read my post and my blog post linked from within:
Your usage of the word "usage" in terms of "using Gab" is of the software feature kind, which is not what FLOSS pillars are about. Instead it is about "usage" of the license kind.
@AndreiRublev1 TL;DR: they still have the freedom to use as a software feature Gab, even if the software has a feature to block Gab, because the user has the Freedom (FLOSS) to fork and remove the block without any license restriction.
@cj I understand your distinctions, and think you are correct. But,
1) Had the anti-Gab people met all their goals, I think, practically speaking, Gab would have been unable to widely disseminate a forked app - an attack on the freedom of Gab users (clearly that was part of the ultimate goal).
2) The common guy is going to see talk of FLOSS type freedom as meaningless when he sees people also trying to prevent Gab from getting forked apps into the hands of users.
@AndreiRublev1 I think the "attack on dissemination of a forked app" is hypothetical, right now. There's already plenty of forked apps available for side loading or on proprietary app stores. So no reason to spread FUD.
@cj it's the difference between how a program is setup vs how the license is setup.
So if it won't technically connect to a particular server that's one thing but for the license to prohibit that connection is another.
@cj Agreed, this notion that "freedom to use" somehow extends into the development stage is truly bizarre. And reeks of entitlement.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!