281–290 of 380 posts
> The CTO publicly apologised and said capacity needs to scale 30x to keep up with AI-driven load. I hope they don't start charging for regular use of GitHub, but when I see how some of the vibe coders make thousands of commits a day, I'm becoming more and more skeptical. Would be a real shame if we can't share and cooperate on code for free.
What if you don't want to self host? Who offers low feature git hosting for a small price? Something like the old $7 account before github was bought by MS? All I want is hosting and a read only web interface, plus access control in case I have collaborators. All the offerings are enterprise priced because they offer "minutes of CI", "AI assistants" and other icing on the cake.
People constantly cry out for decentralization. In reality, however, most systems eventually end up centralized. Perhaps when people ask for decentralization, they are actually seeking a new center where they can become the new pioneers. It seems that when they feel they have no chance of winning under the existing rules, they use decentralization as a pretext to overturn the board.
One of my friends made fremforge.com (an EU-sovereign CI/CD with Git included). It's currently in closed beta but goes live next week (tm). It is built upon Forgejo and EU-based services using T-Cloud as the underlying hyperscaler. Have a look! I don't make any money from it, by the way. And yes, it will cost a little bit, but rest assured: because you are paying for it, you will not be the product.
I now use syncthing for the .git directory, excluding HEAD file and a few others, between my few devices and a vps on hetzner. Most of git is append only immutable blobs - just sharing these between devices just works for me. "users" and authentication is handled by syncthing. I have pre and post hooks to make sure no device tries to change HEAD of branch owned by another device, just to be safe, be it hasn't been ac…
Super interesting, mind sharing your exclusions and hooks?
Earlier quoted context omitted.
Yes, but GitHub is more than just git. The most important aspect of the platform that everybody seems to forget is the social component and how easy it made to create a persistent, off-site repository and collaborate across repos.
What on earth is the social component of GitHub? I assume I’m missing what’s useful to people here as it keeps getting brought up, but what is it? Is it the stars on a repo? Are people doing something else big with all of this?
Everyone seems to be leaving GitHub, and forgetting the entire spirit of what git is in my eyes. Git was always meant to be decentralized, the problem here is that all the tooling around git was centralized to GitHub because it was a cleaner experience, they scaled nicely, and were properly maintained. I would prefer to still see mirrors on GitHub that are auto-synched because I've seen projects for years either self…
> Git is decentralized, GitHub is just another place you can host your code in, but you can push your code to multiple remote servers. That's precisely what I have been doing for years, I still get to keep one foot in the GitHub ecosystem. I still get most contributions on GitHub, and that's fine by me. When a PR comes it I check it out locally, review it, and when it's done I merge locally to master, push to origin,…
Earlier quoted context omitted.
If you have a VPS that's always running, you can just use it as a git remote through SSH without moving things around or any third party software, just put the Git repo on the VPS and clone it via "git clone ssh://user@host/path". You get authentication, encryption and synchronization out of the box with just ssh/git.
Had to vouch for your comment, not sure why it was marked as dead. Definitively the easiest way to approach this, and the most standard way too. If you already have ssh, which I'm guessing you do if you managed to setup syncthing on it in the first place, then you can literally just point git to host+path and it'll use whatever ssh authentication you already have in place. Can hardly get simpler :)
Also syncing is automatic and immediate, I don't have to initiate push and pull.
Earlier quoted context omitted.
it's about GitHub's issues in general, including outages. every section gets somewhat equal amount of attention
The section named “Why outages aren't actually the reason” never tells me why outages aren’t the reason. It just continues taking about outages. I’ll admit I got tired of reading about outages and didn’t absorb the remainder of the article well.