Similar. 95-100 degrees C under load, while 70-85 (or something like that) is normal according to the support. It's also very hot in idle (60-80). And when it gets hot, it throttles to unusable 400 MHz.
Still in contact with support, I have warranty, so I'm hoping they get me new thermal paste or whatever is broken. It's not a software thing.
Why exactly would it not be ok with the gdpr? I can't think of anything right now. Having a few diverse isn't really a new idea, it's basically the www all over again and mastodon and lemmy &Co exist already.
Or are you referring to registering CI workers? That might be a bit of a problem, yeah, as you're basically giving the git hoster remote code execution (on a docker container). Not really a problem if you host your own of course.
I disagree somewhat. In general, the network effect is very strong of course, but git is already decentralized. You can pretty much just git push to somewhere else or even use email.
Holding back? I'm not held back. Codeberg would be a step back, I self host Forgejo and am so hyped up for forgefed.
I set up mirrors for my more important stuff to Codeberg and GitHub for visibility.
About CI/CD: does Codeberg not let you enable actions, which are basically the same as GitHub actions but for self hosting? That's what I use for my self hosted CI. I think you can add your own workers for orgs, repos, and profiles too on Forgejo, should be doable on Codeberg too. (I don't use Codeberg CI, only my own)
PRs? Isn't the point of @nocommit that something does not get committed, and therefore no credentials are stored in the git repository? Even if the PR does not get merged, the file is still stored as a hit object and can be restored.
Why do you need to "tell" some "application"? Why do you need a "finder" if you know the absolute path already? Does this imply that "finder" always runs, ready to be told something?
That's correct, but it still can be separated without too much effort, unlike if it would just be one thing.