This is a note to people moving their repositories blindly to do you know Google is actually a huge investor in Gitlab?

The issue is not about Microsoft buying Github. The issue is about centralization and silos.

You do not solve that by moving your data from one silo to another.

You solve that by relying on small providers you can trust, or by becoming a provider yourself.

PSA: try to avoid boosting / answering to a status that is 9 months old ;)

Show thread

@eliotberriot .......and we need to setup a tool/protocol to manage identities in that way, using some kind of federation, so that sharing could be as easy as with those silo.

@beaufils Yeah, it's a huge part of the problem. Distributing identities and authorization is hard, to say the least :/

@eliotberriot @beaufils OAUTH?

Anyway, without being able to create a pull request from one instance to another, self-hosted gitlab (or whatever) instances are no workable replacement for contralized platforms like github, where basically everyone already has an account and can easily contribute to other projects hosted there

BTW, gitlab has an open issue for this:

@eliotberriot one upside of Gitlab is that it's open, so you can stand up your own instance if Google starts pulling shit.

Not an option with Github

@jjg @eliotberriot That's true, but Gitlab is heavyweight and probably not the sort of thing you can host on an ARM board.

@bob @jjg @eliotberriot there is also gitea as a lightweight alternative FYI

@jjg @bob @eliotberriot @rugk I converted my gitlab instance (that I ran for 3 years) to gitea over the weekend. It was VERY easy.

(I went with docker for some reason, rather than my usual vm style deployment... but as it's a single executable even that should be easy - point it at your database and go.)

Various other places have info on self-hosting it like who are here as @cloud (I think.) I didn't use their setup, but know some who have...

@bob @jjg @eliotberriot gitea is pretty lightweight and easy to spin up at least.

Personally I’d like to see things like issue tracking and wikis be handled as a file convention within the repo itself. So forks automatically pull the state of affairs at that point in time and merges merge in changes to them.

@jjg please read my toot carefully: I'm explicitely talking about

I've got nothing about Gitlab the software (or the company). But the way things are going, will become a new Github in the upcoming months.

@eliotberriot Sorry about jumping the gun, just a bit wound up this morning :)

@eliotberriot I've never understood why someone hasn't written a program that autosyncs your git repo with a bunch of online repositories run by different people. Then Github and Bitbucket and X would all need to collaborate to screw with your stuff.

@Canageek the difficulty is not about syncing git repositories. Git itself is pretty much decentralized by nature and designed to handle that.

But federating issues and pull requests, and authorizations, and so on... Well, that's not that easy.

@eliotberriot Right, but it seems a logical extension of gits decentralized nature, doesn't it?

@Canageek it is needed, yes. It does not mean it's an easy problem to solve though ;)

you can selfhost gitlab... or use a nive gitlab instance... anywayzzz #fuckoffgoogle

@ajeremias yes, I'm explicitely talking about their hosted solution (it says in the initial toot, but I believe it's in fact called now)

somehow some1 posted here that servers are hosted in ms azure :wicked:


You solve that with open federated protocols tying many small solutions and providers together.

@eliotberriot I recommend setting up a server on DigitalOcean and slapping gittea on to it

@eliotberriot They've also taken investment from In-Q-Tel, the CIA's investment company:


I guess you need to choose your silo these days. Self-hosting appears better, but in reality just appeals to a different (and arguably more frightening) set of providers.

Hosting stuff in AWS is appealing to a much more terrifying entity than Google, imo. The companies that we lease lines to the internet from are also quite terrifying.

@mcread I don't know why, but I'm suddenly getting a lot of feedback on this post since yesterday, and it's a bit weird

@eliotberriot Or maybe more than usual ... I guess that's the problem : a break in routine, a distortion in the matrix ;)

@eliotberriot A main difference between #github and #gitlab is that the second let you use it on your own server, not on a cloud server. That's a basic difference. The second difference is that gitlab is an opensource project, and people can fork it if necessary ;-)

It's not the same, is it?

@arbocenc this very old toot refers to the hosted version of gitlab.

The fact that the underlying source code is open does not really change the fact that a single platform hosting thousands of projects is a silo.

I'm not talking about self-hosted Gitlab instances here.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!