this post was submitted on 04 Mar 2026
61 points (93.0% liked)
Programming
25936 readers
312 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The other day I was thinking there should be a fork of dotnet. The two things that it would do differently would be telemetry being totally removed, and an alternative to nuget.org with the requirement that packages be published with free software licenses. Setting such a thing up could be insurance in case they pull anything in the future, too.
Dotnet is maintained by the .NET Foundation and is entirely open source. There are thousands of forks and local clones of the repos under that organization. Rather than hoping someone does this, it'd actually be a huge benefit to everyone for you to create a local clone of the repo and update it now and then, assuming you're worried it might go down anyway.
DOTNET_CLI_TELEMETRY_OPTOUT=1, though it's lame that it's an opt-out and not opt-in. The CLI does give a fat warning on first use at least (which hilariously spams CI output). Opt-in would be so much better though, and opt-out by default is really not great.You can specify other package sources as well, so nothing technically stops someone from making their own alternative. That being said, you'd have to configure it for each project/solution that wants to use that registry.
The main thing I'd be worried about here is nuget.org getting pulled. As far as I can tell, it's run by MS, not the foundation. That'd be basically the entire ecosystem gone all at once. Fortunately, it's actually super easy to create private registries that mirror packages on nuget.org, and it's actually standard practice to do this at many companies. This means that at the very least it would be possible to recover some of the registry if this happened.
For a fork, I would think these would be the main goals I'd look for: