The #FSD purpose is to help people “find freedom-respecting programs”. Browsing the directory reveals copious freedom-disrespecting resources. For example:

FSF has no tags for these anti-features. It suggests a problem with integrity and credibility. People expect to be able to trust FSF as an org that prioritizes user freedom. Presenting this directory with unmarked freedom pitfalls sends the wrong message & risks compromising trust and transparency. Transparency is critical to the FOSS ideology. Why not clearly mark the freedom pitfalls?

UPDATE

The idea of having exclusive clubs with gatekeepers is inconsistent with FSF’s most basic principles, specifically:

  • All important site functionality that's enabled for use with that package works correctly (though it need not look as nice) in free browsers, including IceCat, without running any nonfree software sent by the site. (C0)
  • Does not discriminate against classes of users, or against any country. (C2)
  • Permits access via Tor (we consider this an important site function). (C3)

Failing any of those earns an “F” grade (Github & gitlab·com both fail).

If Cloudflare links in the #FSF FSD are replaced with archive.org mirrors, that avoids a bulk of the exclusivity. #InternetArchive’s #ALA membership automatically invokes the Library Bill of Rights (LBR), which includes:

  • V. A person’s right to use a library should not be denied or abridged because of origin, age, background, or views.
  • VI. Libraries which make exhibit spaces and meeting rooms available to the public they serve should make such facilities available on an equitable basis, regardless of the beliefs or affiliations of individuals or groups requesting their use.
  • VII. All people, regardless of origin, age, background, or views, possess a right to privacy and confidentiality in their library use. Libraries should advocate for, educate about, and protect people’s privacy, safeguarding all library use data, including personally identifiable information.

The LBR is consistent with FSF’s principles so this is a naturally fitting solution. The Universal Declaration of Human Rights is also noteworthy. Even if the FSD is technically not a public service, the public uses it and FSF is an IRS-qualified 501(c)(3) public charity, making it public enough to observe these UDHR clauses:

  • art.21 ¶2. Everyone has the right of equal access to public service in his country.
  • art.27 ¶1. Everyone has the right freely to participate in the cultural life of the community, to enjoy the arts and to share in scientific advancement and its benefits.

These fundamental egalitarian principles & rights are a minimum low bar to set that cannot be construed as “unreasonable” or “purist” or “extremist”.

  •  flatbield   ( @furrowsofar@beehaw.org ) 
    link
    fedilink
    English
    15
    edit-2
    1 year ago

    Going way overboard to the point of being pure is one of the biggest issues the FSF has in terms of relevance and your suggesting they go further down the rabbit hole. It is better to direct people to good FOSS they can and will use then some imagined pure breed that no one will ever use. It is better to have a big tent then a miniscule one too.

    Do I like github. Not really. For that matter do I like git… No. Biggest issue with github is that it mixes FOSS and non-FOSS and even worse not all projects have clear licensing.

    As far as Cloudflair… they are a CDN. relax. Nothing is locked there. Nothing is locked to source hosting either. Just pull the source.

    • As far as Cloudflair… they are a CDN. relax. Nothing is locked there

      Nonsense. Cloudflare (a proxy not a CDN) is exclusive. People like myself are in the excluded group. If Cloudflare gives you no problems personally, then you are in the included group. It’s designed so those excluded are invisible to the included group. You can only see the barriers to entry if you are actually excluded.

        • First of all Cloudflare does not disclose to excluded communities why they are excluded. This non-transparency keeps the marginalized in the dark about both the technical criteria for exclusion and also the business reason for exclusion.

          Why I personally have been excluded is irrelevant trivia. The full extent of CF’s exclusion is unknown but it’s evident that at a minimum these groups of people are excluded:

          • public libraries
          • Tor users
          • VPN users
          • CGNAT users (often poor people in impoverished regions whose ISPs have fewer IPv4 addresses to allocate than the number of users)
          • people who use scripts to access web resources (and interactive users who merely appear to be bots by using non-graphical FOSS tools, blind people IIRC as they are not loading images)
          • all people with a moral objection to exposing ~20—30% of their web traffic (metadata & payloads both) to one single centralized tech giant in a country without privacy safeguards.

          I personally experience exclusion by all of the above except CGNAT.

          •  flatbield   ( @furrowsofar@beehaw.org ) 
            link
            fedilink
            English
            6
            edit-2
            1 year ago

            Sounds to me like this is the kind of abuse blocking any site would use not just cloudflair. Do you have any evidence that Cloudflair is unique in any way in this?

            I mention this because I am not sure not using Cloudflair would change much. You would have to use another CDN or build your own solution. Abuse is a real thing and is the reason we cannot have nice things.

            Edit: By the way, I am sorry you have had issues. I am just not sure what the solution is and am skeptical that this is a Cloudflair only issue.

            • Sounds to me like this is the kind of abuse blocking any site would use not just cloudflair. Do you have any evidence that Cloudflair is unique in any way in this?

              That’s not a meaningful comparison. Blocking sites do indeed block differently in various different circumstances & discriminate against different groups of people. There are patterns (like Tor blocking) but the meaningful comparison is CF to inclusive sites. E.g. gnucash.org. Gnucash demonstrates how a website can be deployed in an inclusive manner that respects user’s rights.

              Cloudflare is unique in how it deceives its users (e.g. tells its users they have a “zero trust” model when in fact you must trust CF with visibility on all traffic payloads). CF holds the SSL keys, unlike other implementations. The recommendation to anti-feature tag CF sites would cover the vast majority of exclusive access-restricted projects. But if a link leads to a rare Siteground site, that should also get an anti-feature tag for being exclusive.

              I mention this because I am not sure not using Cloudflair would change much.

              Of course it would. Cloudflare brings in a long list of problems. Not using CF (like gnucash.org does) solves all those problems of exclusivity and privacy.

              You would have to use another CDN or build your own solution. Abuse is a real thing and is the reason we cannot have nice things.

              The Gnucash project disproves this. Furthermore, a CF link can often be replaced with an archive.org link.

          • and interactive users who merely •appear• to be bots by using non-graphical FOSS tools, blind people IIRC as they are not loading images

            I’m gonna need you to explain that one super chief. Do you seriously believe blind people browse the web through a terminal using Lynx or something?

            • I just encountered a website that uses alt="" on buttons. That means the text description of the button is unreadable in GUI browsers. Mouseovers were coded so you can only get the description in GUI browsers like Firefox by hovering the mouse over the icon. Lynx renders the mouseover text in place of the button. So a screen reader would work on Lynx but not on Firefox for that website.

    •  Adanisi   ( @Adanisi@lemmy.zip ) 
      link
      fedilink
      English
      4
      edit-2
      1 year ago

      To be fair, if the free software “hardliners” like the FSF soften their stance, then that “hardline” just shifts. If nobody maintains that stance the strongest libre software principles will become weaker, if that makes sense.

      The FSF is very useful for preventing that, even if they’re not quite as big as softer movements like “Open Source”

      • Agree and why I am a member. About orgs someone said if you believe in 50% of what they do you should support them and if you believe in 90% of their work then you should be on the board. I think this was about the ACLU but it applies similarly to the FSF, EFF, and others.

        The thing about any org… you cannot boil the ocean. You have to choose your battles. Trying to do everything means you do nothing. I think the FSF needs to think carefully about that. Yes stick with core principles but act wisely and effectively as well.

    • Going way overboard to the point of being pure is one of the biggest issues the FSF has in terms of relevance and your suggesting they go further down the rabbit hole.

      Framing inclusion of all people as a “purist” agenda is a bit rich. The Universal Declaration of Human Rights doesn’t say it’s okay to deny equal access to some people. for example. And we don’t call the UDHR “purist” or extremist for being all inclusive. Being inclusive is where the bar should be set. It’s achievable and there are some projects that prove that.

      It is better to direct people to good FOSS they can and will use then some imagined pure breed that no one will ever use.

      You’re not grounded in reality. Tagging anti-features does not lead to “some imagined pure breed that no one will ever use.” Nor would anyone avoid listings which have no anti-feature tags. It’s the contrary. Projects that lack anti-features are superficially attractive.

      Biggest issue with github is that it mixes FOSS and non-FOSS and even worse not all projects have clear licensing.

      That is not the biggest issue with Github. Github is exclusive, feeds copilot, feeds a company that’s antithetical to the FSF mission, among other issues that were listed in the OP.