

It’s also not that hard to host on Codeberg… especially if they’re already doing something disruptive like forking…
Install Guix


It’s also not that hard to host on Codeberg… especially if they’re already doing something disruptive like forking…


You do have to ask for permission. https://docs.codeberg.org/ci/
Asking permission involves creating an issue on the Codeberg-e.V./requests repo: https://codeberg.org/Codeberg-e.V./requests/issues/new?template=ISSUE_TEMPLATE%2FWoodpecker-CI.yaml
Here’s an example issue asking permission for CI: https://codeberg.org/Codeberg-e.V./requests/issues/1663
They get back to you fairly quickly. I think the main thing they check for is if your project is FOSS. They don’t seem very strict otherwise.
After you get permission, you can go to https://ci.codeberg.org/login to access CI.
You’ll also need to create a .woodpecker folder in your repo.
Woodpecker docs are here: https://woodpecker-ci.org/docs/usage/intro
# .woodpecker/my-first-workflow.yaml
when:
- event: push
branch: main
steps:
- name: build
image: debian
commands:
- echo "This is the build step"
- echo "binary-data-123" > executable
- name: a-test-step
image: golang:1.16
commands:
- echo "Testing ..."
- ./executable


I mean, if Zig and Guix can do it. It’s possible.
I’m in a similar boat. So far:
Next I gotta update the readme on GitHub telling everyone that I’m going to move to Codeberg. I’ll let that sit for a few months.
Also, I gotta update consumers like homebrew to consume from Codeberg instead.
I was gonna close/merge any open PRs on GitHub.
Issues, I’m not totally sure about. I thought I read there was a way to migrate those. Although, I’m kiiinda ok with starting fresh… not totally sure this part needs more thought.
Once the Codeberg repo is ready, I’ll make the GitHub repo read-only, with the readme pointing to Codeberg.
Way, way, way down the line, I’d consider deleting the GitHub repo (and finally my account).
I’m OK with breaking things. I’m gonna try my hardest to not break stuff, but I’m not going to let the fear of breaking stuff prevent me from getting on ShitHub by Macroslop.
Can’t do that anymore
What is “that”? I just bought a Google TV and was able to install Projectivy Launcher fine?
Definitely not WebOS. I have an Nvidia Shield that runs Android TV, which is nice because there’s a wide selection of apps and you can install custom launchers, Tailscale, Jellyfin, SmartTube. The downside, as I recently learned, is that your parents probably will have a harder time switching between the TV’s native OS and the Shield.
So I recently got a Google TV, which is (just?) Android TV, and that allows me to install Tailscale and Jellyfin, but since it’s 1 system, it’s easier for some folks to use. I also installed Projectivy Launcher for my parents to get rid of the default ad-ridden launcher. I haven’t yet had time to try to install SmartTube, but I think I read it’s possible…
Curious to learn more about https://plasma-bigscreen.org/ I didn’t know about that. Thanks!


Why Forgejo Actions and not Woodpecker CI, isn’t Woodpecker on Codeberg more stable? Yes, absolutely, in fact the documentation for Forgejo Actions on Codeberg is out of date right now
Waah?
Forgejo Actions will just feel way more familiar coming from GitHub Actions. The UI and YAML syntax is almost identical, and the existing actions ecosystem mostly works as-is on Codeberg.
Ah, ok. I don’t care about that.
Setting up woodpecker.
Yeah, not handled well. They’re doing slimy corpo bullshit.
On the other hand, I like that they’re open source and don’t block stuff like vaultwarden.
I hope they can take the extra money and make the product better. Cuz I definitely don’t love Bitwarden, but it’s a better alternative than 1Password.


I thought the Iranians specifically chose Legos because the US bombed a girl’s primary school. Seemed like a fitting way to fight back.


Yes, it should be Nucleus. Them calling it PiedPiper is a propaganda campaign to try to earn good will from people. Fuck Google locking down Android.


I really do not understand the hate :/
The itsfoss interviewer goes into this:
A lot of backlash isn’t about the code change, but about what it represents.
You say this is “just attestation, not verification” but we know that infrastructure always gets repurposed later. This is where the legit fear lies.
Do you think regulations like these will reshape desktop Linux in the next 5-10 years where we might have “compliant Linux” and “Freedom-first Linux”?
Sam Bent’s article also goes into this (although, fuck that clickbait title): https://www.sambent.com/the-engineer-who-tried-to-put-age-verification-into-linux-5/
He read the laws, decided compliance was the correct response, and went to work. Every objection the community raised went nowhere: that this enables surveillance infrastructure, that lying is trivially easy, that the laws themselves are unconstitutional overreach. He’d already accepted the law as legitimate and moved to implementation.
He read the law, took it at face value, and started writing code. The word for what that is sits somewhere past malice, something more insidious: an engineer who treats compliance as engineering, who sees a legal requirement the way he sees a technical specification, and will implement whatever the spec says regardless of who wrote the spec or why.
The reason to name him is the pattern. The surveillance state runs on volunteers: people who do the implementation work for free, out of genuine conviction, with no paper trail connecting them to the money that wrote the laws.


Not surprising, this guy is also onboard with Google locking down Android: https://dylanmtaylor.com/posts/2026-03-19-googles-new-android-sideloading-flow-is-a-fair-trade


Why not let someone else do it then? Why eagerly sign up to be the one to do it?


squidward opens chair: ooh, AGPLv3, nice
squidward closes chair: sign our CLA


which by the way was not expected to give perfect answers to questions
Except that’s how a lot of people treat it. And there’s so way to guard against that.


Related: https://brainmade.org/


… You know… yeah, that’s true. One of the huge benefits of using some open source library is that you don’t have to maintain it. But if you clean room it, then it’s all on you.
Although, companies like Amazon will have the engineers to maintain it internally. But a lot of other companies won’t.
And then you have the chardet guy: https://github.com/chardet/chardet/issues/327


Does anyone have any ideas on how to fight back? Should we start withholding test suites now? Withhold docs?
It’s a little more nuanced than that.
I will gladly write my own small, half-assed framework that I 100% know, can reason about, can debug, and can extend to fit my requirements. I will gladly pass on a fat-assed, bloated framework with a million dependencies, where I only need a few features, and where if I need something that isn’t offered by the framework I have to submit a PR or add some janky-ass workaround.
Codeberg is absolutely an alternative hosting place that is ready to go today. Medium and large players like Zig, Guix, Librewolf, Forgejo, and Comaps are on Codeberg. These aren’t random people with projects that no one uses. These are large projects with lots of collaborators that ship software to lots of people. (Even Alpine Linux seems to be experimenting with Codeberg.)
Codeberg has a similar UI/UX to GitHub. It’s got CI too, either traditional CI with Woodpecker, or you can migrate your GitHub Actions to Forgejo Actions (which are similar).
Codeberg is big and popular enough that it shows up in web search results, search for “zig source code” and you’ll get a result for Codeberg. It’s not like people only search for code in the GitHub search bar.