Closed bruceleerabbit closed 4 years ago
Thank you for this elaborate reasoning why this list should not be on Github. Really appreciate the effort and your dedication to fight for our freedoms.
For the most part I wholly agree with the points you make. This list was created before MS acquisition and part of the also GH-based awesome top-level project, but those are not valid reasons to stay here, of course. But reasons that are, imho (speaking as facilitator of the Humane Tech Community):
On Github this list reaches the attention of the largest developer base on the planet (who have centralized themselves on this platform), many of whom have never heard of the term 'humane technology' but really should make this concept part of their mindset when developing new software.
The list fortunately contains ever more projects that live in other, better code forges. Something I make visible by showing the code repo logo's. This serves to raise awareness for existing GH devs about the existence of alternatives, where most of them never heard of most of these before.
So all-in-all this is a bit comparable to a #DeleteFacebook
campaign which is most effective when directly targeting FB users. For the time being we are here to stay, but if you want to PR a 2-way sync with a Codeberg repo, then I am all ears :)
On a personal level I am actively promoting alternatives too. I self-host Gitea, plus own a Codeberg account. With regards to breaking walled gardens I am an advocate of ForgeFed and the fediverse in general, where I operate @humanetech
and maintain the Feneas research wiki.
Furthermore (unrelated to our Humane Tech Community) I created an alternative to the top-level awesome project at Codeberg, called the delightful project that is exclusively for FOSS, Open Data and Open Science resources. I hereby encourage anyone to become a delightful contributor and create their own curated list in this space :)
PS. It is a bit of a spare time issue (all my efforts are volunteering), but I intend to start a 'delightful-humane-design' list. Maybe I'll just create this already even if I lack the time to hunt for much great content yet.
FYI I decided to just create the delightful-humane-design list already, and here is the URL: https://codeberg.org/teaserbot-labs/delightful-humane-design
For the most part I wholly agree with the points you make. This list was created before MS acquisition and part of the also GH-based awesome top-level project, but those are not valid reasons to stay here, of course. But reasons that are, imho (speaking as facilitator of the Humane Tech Community): ... if you want to PR a 2-way sync with a Codeberg repo, then I am all ears :)
@aschrijver it sounds like this suggestion is welcomed if somebody will do the work to set up syncing. What do the repository administrators need help with to set up syncing? (I didn't know syncing needed any git commits that would go in a PR to set up, but I'm kind of new to the awesome-list norm).
Should this issue be reopened if there's a welcome path to address it?
Hi @xloem thank you.
Given my time constraints and the fact that awesome vs. delightful project have different rules and style, I think I'll leave it at current division with awesome-humane-tech part of awesome list collections on Github and the delightful-humane-design subset of humane technology being managed by me on Codeberg where the delightful project has its home.
@aschrijver what would you need from the rest of us to reconsider your decision?
Thank you for your kind offer of help! I think right now the current set up works fine. Besides the things I listed before, the popularity of github has this list visited by people not aware of all the alternatives that exists outside of this walled garden. The list serves to make them aware of the alternative, better world (in the 'Related awesomeness' section, among other).
If you are interested to set up and maintain a delightful list yourself, then you are of course most welcome to do so :)
@aschrijver it sounds like it's unpleasant to you to consider changing?
For others, another alternative is githide which is in onionspace @bruceleerabbit http://githidep2hynhdmutuv7n2tei4iie2c7lyqz5fes3r5zzoxe5dshtxyd.onion/ can only be accessed over the tor anonymity network which keeps developers safer.
@xloem That onion site has apparently died. But there is a directory of forges here
MS Github is wholly contradictory to the mission purpose. To improve the credibility of the project and attract privacy-respecting developers, please consider moving away from Github.
It's particularly important to get the bug tracker off MS Github to encourage reports. Personally, I'm done contributing to Github projects (apart from asking projects to join the free world).
Direct practical problems with using Microsoft Github
Ethical problems with using Microsoft products and services
1.c
, GDPR article 17, and stores the data outside the EEA (may also be a GDPR breach).Bad alternative: gitlab.com service
The Gitlab.com SaaS is often considered an alternative to MS Github, but it's even worse--
for many reasons
* Sexist treatment toward saleswomen who are [told to wear](https://web.archive.org/web/20200309145121/https://www.theregister.co.uk/2020/02/06/gitlab_sales_women/) dresses, heels, etc. * Hosted by Google. * [Proxied](https://about.gitlab.com/blog/2020/01/16/gitlab-changes-to-cloudflare/) through privacy abuser CloudFlare. * [tracking](https://social.privacytools.io/@darylsun/103015834654172174) * Hostile treatment of Tor users trying to register. * Hostile treatment of new users who attempt to register with a `@spamgourmet.com` forwarding email address to track spam and to protect their more sensitive internal email address. * Hostile treatment of Tor users *after* they've established an account and have proven to be a non-spammer. Regarding the last bullet, I was simply trying to edit an existing message that I already posted and was forced to solve a CAPTCHA (attached). There are several problems with this: * CAPTCHAs break robots and robots are not necessarily malicious. E.g. I could have had a robot correcting a widespread misspelling error in all my posts. * CAPTCHAs put humans to work for machines when it is machines that should work for humans. * CAPTCHAs are defeated. Spammers find it economical to use third-world sweat shop labor for CAPTCHAs while legitimate users have this burden of broken CAPTCHAs. * The reCAPTCHA puzzle requires a connection to Google 1. Google's reCAPTCHAs compromise security as a consequence of surveillance capitalism that entails collection of IP address, browser print. * anonymity is [compromised](https://cryptome.org/2016/07/cloudflare-de-anons-tor.htm). * (speculative) could Google push malicious j/s that intercepts user registration information? 1. Users are forced to execute [non-free javascript](https://libreplanet.org/wiki/Group:Free_Javascript_Action_Team#Ideas_for_focus) ([recaptcha/api.js](https://www.google.com/recaptcha/api.js)). 1. The reCAPTCHA requires a GUI, thus denying service to users of text-based clients. 1. CAPTCHAs put humans to work for machines when it is machines who should be working for humans. *PRISM* corp Google Inc. benefits financially from the puzzle solving work, giving Google an opportunity to collect data, abuse it, and profit from it. E.g. Google can track which of their logged-in users are visiting the page presenting the CAPTCHA. 1. The reCAPTCHAs are often broken. This amounts to a denial of service. ![gitlab_google_recaptcha](https://user-images.githubusercontent.com/18015852/51769530-9d494300-20e3-11e9-9830-1610b3ae9059.png) * E.g.1: the CAPTCHA server itself refuses to give the puzzle saying there is too much activity. * E.g.2: ![ccha](https://user-images.githubusercontent.com/18015852/55681364-07713600-5926-11e9-8874-137e4faaf423.png) 1. The CAPTCHAs are often unsolvable. * E.g.1: the CAPTCHA puzzle is broken by ambiguity (is one pixel in a grid cell of a pole holding a street sign considered a street sign?) * E.g.2: the puzzle is expressed in a language the viewer doesn't understand. 1. (note: for a brief moment gitlab.com switched to hCAPTCHA by *Intuition Machines, Inc.* but now they're back to Google's reCAPTCHA) 1. Network neutrality abuse: there is an access inequality whereby users logged into Google accounts are given more favorable [treatment](https://www.fastcompany.com/90369697/googles-new-recaptcha-has-a-dark-sideby) the CAPTCHA (but then they take on more privacy abuse). Tor users are given extra harsh treatment.There's nothing wrong with self-hosting an instance running Gitlab CE or using the Gitlab instance of another party.
Decent alternatives