Even better when someone forked it away from proprietary, closed-source, publicly-traded, for-profit, US-based, account-required, training-AI-on-your-code-then-selling-it-back-to-you Microsoft GitHub forge/social media network often with vendor lock-in to some other forge without all that BS.
toastal
Appointments with doctors is too sensitive of data. I would opt out of that & just add it to your non-Google calendar as soon as you know the date+time.
As is host blocking via OpenWrt
OpenWrt is a great piece of software. …As is the hackers that get it running on the proprietary hardware.
You can start with a few steps in the direction of privacy & slowly build to it rather than dismissing the concept.
Maybe you don’t want the banking corporations to know you purchased lube & a ham sandwich. Inb4 some goober says tap-to-pay with Google or Apple, which now lets the banking corporations & big tech know your purchase history too.
Cash is a great.
Choosing proprietary tools and services for your free software project ultimately sends a message to downstream developers and users of your project that freedom of all users—developers included—is not a priority.
—Matt Lee, https://www.linuxjournal.com/content/opinion-github-vs-gitlab
Same. I miss the IP (especially Arcane) & the friends I made playing LoL—and I think I could have a good time living in the world, but not at the cost of compromising device permissions. Same reason I refuse to use my shitty banking app if they try to tell me what software I can & can’t run/install or how to operate the device I own.
I mean it took the code production of from workers for the Commons, packaged it up, & sold it back to the workers—often in violation of the license if not the spirit of free, ethical, or similar software. All AI generations should be CC0 / 0BSD licensed.
If Lemmy cared about privacy, contributing source code & opening tickets would not require opening accounts with a for-profit, US-based, closed, prorietary service owned by a publicly-traded megacorporation that has shareholders to appease & a history (as well as current) record of EEE (embrace, extend, extinguish).
Will their future MMO have this trash?
https://githubcopilotlitigation.com/ it’s been ongoing
Submitting issues & discussions require an account. Using the search for code requires an account. On Lemmy this week there was also a post about viewing “Discussions” & “Wiki” being A/B tested or whatever with an account required to view. Which is to say, if submitting patches, issues, & or using some features requires giving up personal info & agreeing to Microsoft’s ToS to create an account, you have locked out users & their freedom isn’t respected if their autonomy to not create an account with a company known for predatory behavior cannot be respected.
Users locked out sucks, but so does lock in. Sure you can set a non Microsoft GitHub remote & push to it, but I’m talking about the forge on whole rather than the tool that backs it. The more Microsoft GitHub features you rely on, the more the existance of a
./.github
directory’s or otherwise gets cited as being too hard to move. As more features get locked behind authentication, so will the APIs that allow some ability to migrate. GitHub were the popularizers of the “pull request” model too which is severely limiting but is the only way you can operate on their site (no stacked diffs, mailing patchsets, etc.) which eliminates alternating review methods (while you could use a third-party, due to MS GitHub’s ingrained workflow to too many, I’ve seen alternatives being considered as “too hard” rather than “different” (even if could be “better”)). I’ve also witnessed some communities like Elm freeload on the “free” hosting & require all community packages be upload to only MS GitHub or you can’t publish & by proxy participate in the community (or in their case even refer to other remotes, VCSs, tarballs for packages (even private ones) but that is due to Elm having a terrible default package manager).They’ve embraced a Git forge; they’ve extended the space with Codespaces, Sponsors, Actions, Copilot, even VS Code proliferation far beyond pre-acquisition GitHub; now we just await the extinguish part.