

almost as if using a memory safe language actually reduces the CVEs related to memory


almost as if using a memory safe language actually reduces the CVEs related to memory


it’s not like the whole driver is written in unsafe rust


Maybe. The problems I have with codeberg are the lack of support to private repos and the 100 repo limit. I have some personal stuff in version control that I prefer to keep private, like notes, dotfiles, and shell history.
At the same time, I’m not sure I want to maintain a self-hosted forge.


but the whole thing is self-hosted, not just the action runner, right?


any alternatives to GH that allow private repos and self-hosted action runners?
btw, the prices of managed runners are going down, not increasing
https://docs.github.com/en/billing/reference/actions-runner-pricing#standard-github-hosted-runners
still good to have a self-hosted alternative though
ah right, my bad
fwiw, you can self host a GitHub actions runner


maybe they resumed development then, it was removed from Ubuntu and RHEL repos about 5 years ago when I had to look for an alternative


are you using a maintained alternative? Distros started to remove it from their repos years ago because it was not maintained anymore afaik


I’m the only user of my setup, but I configure docker compose stacks, use configs as bind mounts, and track everything in a git repo synchronized every now and then.
It doesn’t require, but it runs better on GPU. It’s not for nothing that modern terminal emulators like Kitty, Alacritty, Ghostty, and Wezterm ship with GPU support. Sure, they just “render text”, but it is a rendering workload that is highly parallelizable. There’s no reason to waste CPU cycles with that.


English, duh
need a hand? man touch


check you SSH_ASKPASS and SSH_ASKPASS_REQUIRE variables


and now that the handover was confirmed, it’s unlikely they’ll do anything without hard evidence of malicious intent


TL;DR: the original fork of Syncthing under the GitHub user Catfriend1 vanished without any clarifications from them to the community. Recently, another GitHub user researchxxl acquired the release keys and published a new version v2.0.12.1:
Shortly after the repo was moved to a brand new account ‘researchxxl’ who was not able to properly explain how or why the repo was handed over to them nor why the original maintainer handed over the release key to them. Or why the original maintainer did not bother communicating this to the community in advance.
The new version v2.0.12.1 under researchxxl seems to be free of malicious code, and the repo has reproducible builds.
Since the whole situation is a bit sketchy, some are advocating for the F-droid account to be locked and any release after v2.0.11.2 to be purged.
Update: it seems that as of a few hours ago, Catfriend1 broke the silence and confirmed the transfer to researchxxl:
Therefore, I did hand over all my stuff to my inheritant @researchxxl inluding the com.github.catfriend1* apps, digital signing material and wish them the best to fulfill the mission of carrying on the Syncthing-Fork app. :woman_technologist: We have met in online gaming and developing modding code together for a level that tells the story of a research station attacked by some alien-like monsters. Two players do have to cooperate on fixing electrical devices, a low power emitting nuclear reactor and avoiding a bath in acid. If you stumble upon the game, say hello to us during our test sessions. :slightly_smiling_face:
IME the longer I wait, the higher the chances of an update break something, so I update my main desktop multiple times a day.
along with the compose.yaml file, unless I need it in a different drive for any reason