Been switching to Codeberg because it's nice but increasingly looking like I soon will HAVE to abandon Github, because the entire interface will soon be just one giant maze where at each intersection one path leads to the feature you wanted and the other path is Copilot
https://fosstodon.org/@anuytstt/115009836366326911
Several people sent me this: Github is no longer an independent company; rather as of today Github is under the AI team. As far as I'm concerned, this is an open admission the function of Github is not to host source code, but rather as an intake for Microsoft to harvest source code to train their AI.
https://www.theverge.com/news/757461/microsoft-github-thomas-dohmke-resignation-coreai-team-transition
I guess it always seemed unlikely MS would've paid all that money to altruistically host the open source community. "Oh, I didn't get rich by writing a lot of checksβ¦"
@mcc@mastodon.social Itβs not about the source code alone (they can crawl it elsewhere), but about building a toolchain that many OS projects will become dependent on (with GitHub actions, Copilot and many more βAIβ tools in the future)
@mcc@mastodon.social Make fake source code. Get people to download it.
@mcc@mastodon.social love how like yesterday he was like "copilot is the future" and then today yeets himself out.
https://www.theverge.com/decoder-podcast-with-nilay-patel/720075/github-ceo-thomas-dohmke-ai-coding-copilot-openai-interview
I guess the curse of Sourceforge comes for us all, eventually
@mcc@mastodon.social I wish we would have figured out a workable self-hosting solutionβor even better an actually-distributed VCSβinstead of everyone just switching to The Next Popular Platform so we could have it happen all over again.
@tedmielczarek@mastodon.social As far as I am concerned self-hosting and code backup are mutually exclusive goals
@tedmielczarek@mastodon.social As far as I am concerned self-hosting and code backup are mutually exclusive goals
@mcc@mastodon.social yeah that's fair. I guess "actually distributed" would be nice, although you'd need some way of actually ensuring replication. Maybe the right goal here would be "all of the project details exist in the repository alongside the code"? It's easy enough to publish a git repository to some other host, but the issues/pull requests/etc are much harder.
@mcc@mastodon.social yeah that's fair. I guess "actually distributed" would be nice, although you'd need some way of actually ensuring replication. Maybe the right goal here would be "all of the project details exist in the repository alongside the code"? It's easy enough to publish a git repository to some other host, but the issues/pull requests/etc are much harder.
@tedmielczarek@mastodon.social In general the story of the last 20 years in net tech is
- P2P tech arises, shows several powerful proofs of concept, is ready to be applied to virtually everything
- CDNs ("cloud providers") arise, are very cheap, so cheap there's no reason to investigate P2P
- Enough time passes for everyone to forget how to function without cloud providers
- Cloud providers enshittify intensely and rapidly, enter into a state you would have never chosen, but now P2P knowhow is mostly lost
@tedmielczarek@mastodon.social In general the story of the last 20 years in net tech is
- P2P tech arises, shows several powerful proofs of concept, is ready to be applied to virtually everything
- CDNs ("cloud providers") arise, are very cheap, so cheap there's no reason to investigate P2P
- Enough time passes for everyone to forget how to function without cloud providers
- Cloud providers enshittify intensely and rapidly, enter into a state you would have never chosen, but now P2P knowhow is mostly lost
mcc
