stay discoverable with your local git by annoucing it to nostr git servers
gittr.space
Bye, Bye GitHub
51–60 of 82 posts
Re: Bye, Bye GitHub
#52Earlier quoted context omitted.
Microsoft owns GitHub.
What frontier model did Microsoft train?
Re: Bye, Bye GitHub
#53Earlier quoted context omitted.
It ridiculous, Codeberg did the same. I get why, really, I do, but it's creating a severe damage that will be abused by a third evil actor that will take over the wasteland of GitHub and GitLab by creating a service that will allow anything (until it is enshittified of course) Outcome? Everyone on their own self-hosted git servers, zero collaboration.
> Outcome? Everyone on their own self-hosted git servers, zero collaboration. Everyone sticking to Github, then a year or two from now Github resolves their scaling issues and the competitors miss their window of opportunity to disrupt
Not if they keep putting everything behind a paywall. I'm not going to pay 60 (20/user/month) euros per month to be able to restrict pushes to main. It's absurd. Sorry, this specifically gets my blood boiling so I might be a bit more aggressive than needed.
Re: Bye, Bye GitHub
#54With SourceHut banning projects that use LLMs[1], I’m looking to migrate this weekend. While I can host Forgejo just fine[2], doing so means no one will be able to contribute to the projects, since federation isn’t a thing yet. Heck, getting contributions on SourceHut was hard enough, and it doesn’t even require people to register an account. I might need to bite the bullet and go with GitHub. Regardless of what I th…
Codefloe looks like it could be promising. No real restrictions like other options. Time will tell.
Re: Bye, Bye GitHub
#55I'm in the middle of a Forgejo migration myself for similar reasons. What finally pushed me over the edge was a hour long Actions outage that prevented me from pushing a hot fix for a bug to my webapp. (I relied on GH Actions to build and push an ARM Docker image.) For work that a business depends on, I can't recommend GitHub Actions. It's not just the outages that personally annoyed me, but the fact that I'm paying…
I'm curious what you're replacing Actions with on the Forgejo side, and whether running that infra yourself feels like part of the benefit or another thing you'd rather not own
Re: Bye, Bye GitHub
#56I'm in the middle of a Forgejo migration myself for similar reasons. What finally pushed me over the edge was a hour long Actions outage that prevented me from pushing a hot fix for a bug to my webapp. (I relied on GH Actions to build and push an ARM Docker image.) For work that a business depends on, I can't recommend GitHub Actions. It's not just the outages that personally annoyed me, but the fact that I'm paying…
I'm curious what you're replacing Actions with on the Forgejo side, and whether running that infra yourself feels like part of the benefit or another thing you'd rather not own
Forgejo has Runners that you can install on another server and register with Forgejo Actions. There might be 3rd party Runners you can pay to use, I've just run my own on a hardened VM.
Re: Bye, Bye GitHub
#57I'm in the middle of a Forgejo migration myself for similar reasons. What finally pushed me over the edge was a hour long Actions outage that prevented me from pushing a hot fix for a bug to my webapp. (I relied on GH Actions to build and push an ARM Docker image.) For work that a business depends on, I can't recommend GitHub Actions. It's not just the outages that personally annoyed me, but the fact that I'm paying…
I'm curious what you're replacing Actions with on the Forgejo side, and whether running that infra yourself feels like part of the benefit or another thing you'd rather not own
My gh actions were straightforward and moved to forgejo runners with zero drama.
Re: Bye, Bye GitHub
#58With SourceHut banning projects that use LLMs[1], I’m looking to migrate this weekend. While I can host Forgejo just fine[2], doing so means no one will be able to contribute to the projects, since federation isn’t a thing yet. Heck, getting contributions on SourceHut was hard enough, and it doesn’t even require people to register an account. I might need to bite the bullet and go with GitHub. Regardless of what I th…
Vervis and Radicle both support federation.
Re: Bye, Bye GitHub
#59The problem is nothing competes with GitHub. I know, GitLab. Gitea. Bitbucket. They have some features, but it’s like suggesting I drive a Nissan Sentra because my BMW breaks down once in a while.
My dude, that Nissan will get you from point A to point B just as effectively as a BMW will. Your analogy is working against you, not for you.
Yes, but they were looking at it from the perspective of features, not reliability.
Re: Bye, Bye GitHub
#60With SourceHut banning projects that use LLMs[1], I’m looking to migrate this weekend. While I can host Forgejo just fine[2], doing so means no one will be able to contribute to the projects, since federation isn’t a thing yet. Heck, getting contributions on SourceHut was hard enough, and it doesn’t even require people to register an account. I might need to bite the bullet and go with GitHub. Regardless of what I th…
[dead]