Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.
-
when you're a corporation with billions of dollars and US politicians cost millions on the high end, you can choose to do whatever you want.
It is still an unnecessary risk for them.
-
We need something like Forgejo, but decentralized, like Lemmy. I don't want to create a new account for every Forgejo instance.
You know, git initially was that kind of thing where people would send diff commits on mailing lists. And that is perfectly decentralized! And there's no need for federation too.
-
It is still an unnecessary risk for them.
true, but let's not pretend that they were without agency in this decision and in decisions leading up to the current context.
-
Russia is free to fuck off out of Ukraine, simple as.
I’m sure there is a lot that the random developer who happened to be born in Russia can do about that.
-
The issue tracker is usually the concern
How would decentralization work for an issue tracker? The issues have to be stored somewhere.
-
Yeah, that was my point in the first comment... But not only that...
The development with multiple people is decentralized, yes...
But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don't have an account on each of these... Try pushing code or making a pull request and see how it fails, because you are not authenticated...
SourceHut encourages an e-mail–based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it.
-
I always kept telling Free-software & OpenSource projects to move to GitLab, Codeberg or SourceHut
You cannot fight capitalists on a capitalists platform.
& if you want something that's even more independent try Fossil
By what standard is GitLab not a “capitalist platform”? It feels even more corporatey than GitHub. From their homepage:
GitLab is the most comprehensive AI-powered DevSecOps Platform.
-
Sanctions are bullshit economic violence. This is a great example.
Probably better this economic violence than I dunno, the physical violence Russia has exerted on the Ukrainian populace?
-
Yes, also remember to completely avoid Typescript and C# since they are also Microsoft. And Rust since heavy ties to Amazon. Actually, just to spare you the time, avoid programming altogether and do something like farming, since no Big Tech influence there. /s
Yes, also remember to completely avoid Typescript and C# since they are also Microsoft.
This, but unironically.
-
Welcome to the "free world".
conservative: says a racial slur
Online Platform: bans user
conservative: "sO mUcH fOr tHe tOlEraNt lEfT
" -
Going by their Mastodon account, seems they were erroneously detected as "from a US-sanctioned region" and it took too long for said error to be resolved, so they just made the switch.
Given now that the US has a russian president, maybe the US should sanction itself lol
-
So a person that happens to be iving in a sanctioned country, makes them banned? Bullshit
I assume most Russian GitHub users use a VPN to avoid it. He has chosen not to in order to make a point.
The real worry is what happens when the US declares sanctions on random allies in their stupid "trade war"...
-
conservative: says a racial slur
Online Platform: bans user
conservative: "sO mUcH fOr tHe tOlEraNt lEfT
"Person: *makes an app for everyone to use*
Twitter baby: "Racial slurs! Racial slurs!"
-
How would decentralization work for an issue tracker? The issues have to be stored somewhere.
naturally on the instance that hosts the repo
-
You mean git inherently requires you to identify yourself?
Huh, shock
git identification has nothing to do with authentication, as any sane person with git experience knows
-
- that's really too bad, I hope that gets resolved soon
- that's a pretty old version of podman (4.3 looks like?); also, why have nested podman? My infra is something like this:
Bare Metal ├─ Rootless Podman ├─ Forgejo ├─ Rootless Forgejo Runner (planning to run on another machine entirely) ├─ <Actions Containers Run Here>I doubt the extra level of nesting is the issue though. If your issue is networking, then maybe the version of podman is the issue, since they switched out the networking layer in 5.0. I upgraded for a related reason, though I'm still getting some odd issues (mostly w/ the DNS resolver).
I haven't gotten to cross-compiling just yet, nor have I needed to build a docker image since my projects are very much in the testing phase. But maybe I'll give it a shot soon, since it's better to catch these types of issues before it becomes a bigger problem.
I agree that it is quite possibly related to the version of Podman moreso than an inherent issue. I am currently satisfied, however, and have no desire to fiddle with it any more... Or at least until Debian 13 gets released.
My use of PinP is almost entirely for cleanliness. It allows me to more easily for me to wipe clean the build environment (clear out space, troubleshooting). It also mildly improves security as the 'untrusted' actions containers run on a separate environment from the important Forgejo container.
-
Boycott all US based services.
-
I think that's bad (for my personal use) because if I accidentally commit a secret key, how do I claw it back? Basically, how would I claw anything back if it's on a blockchain aka on thousands/millions of computers already (you can't).
that's already a concern. what if someone just cloned your repo? there's also plenty of people that mirror public repos to their personal forgejo server. forgejo makes it very easy.
the only solution to mitigate such a mistake is to
1) invalidate the token
2) remove the commitIn that order.
-
when you're a corporation with billions of dollars and US politicians cost millions on the high end, you can choose to do whatever you want.
"Microsoft continues to work with Russians despite sanctions due to ongoing war in Ukraine" is probably not a headline they want to see.
