5,913 karma · joined September 10, 2011
Spare-time projects wind up here: https://code.ivysaur.me/
I was a bit surprised this is not a Debian Policy violation (and any Debian patches for security support may no longer apply), but at least the user experience will "just work". Cross-reference https://bugs.debian.org/1040507 .
The old RV40 had some small advantages over H264. At low bitrates, RV40 always seemed to blur instead of block, so it got used a lot for anime content. CPU-only decoding was also more lightweight than even the most optimized H264 decoder (CoreAVC with the inloop deblocking disabled to save even more CPU).
The disks for Glacier cost $0 because you already have them.
The "open core" (Gitea Enterprise) is not Gitea, it is a downstream fork by CommitGo, who you can pay for contract development for custom features. The features are expected to be upstreamed, there are open PRs, they just don't yet meet Gitea's code review standards. You can run them from the PRs if you like.
It is a reasonable change to make. Do the rest of their native Win32 UI controls still use MS Sans Serif (Windows 98) or Tahoma (XP) instead of Segoe UI (Vista)?
A general "wayland" protocol for it didn't exist back then, but in this thread we see ext-session-lock exists now, and jwz was recently trying to use it where available: https://www.jwz.org/blog/2025/07/xscreensaver-wayland-and-lo... so you might see an xscreensaver port soon.
My 2c as an outside observer - It is all about sponsored work.
Gitea long wanted a CI feature but from the outside, all anyone could see, was a Drone/Woodpecker integration. Codeberg started to spend a lot of time investing in this.
Then one day, Lunny(? i think) appeared suddenly with a fully compliant and working Github Actions CI implementation. The development had been done under a private sponsored contract.
It's great that Actions was managed to be open sourced. It's significantly better. But Codeberg really took it the wrong way and started agitating and sponsoring a fork. Nobody wants to be left in the dark.
There is a huge amount of interest in Gitea (and its forks). Everyone wants this to remain MIT, and it obviously will since there's no CLA. IMO all the "gitea company" stuff is about having a better legal structure for contract work on big features like that. That contracting is happening anyway so it may as well have a good legal structure.
Forgejo PR managed to twist that good announcement into seeming as a conflict of interest, because the "Gitea" name was reused for two different concepts. Now that it's CommitGo as the (legally independent) contract development agency, it's much clearer. There is a Gitea company as well but it just needs to hold trademarks and domain names and cloud stuff.
It's really a story of some great developers maturing into a more sophisticated legal and contractual level. The model is quite good, similar to e.g. Debian being the community project and Freexian being one of many commercial contractors for it.
Anyways, compared to Forgejo today, Gitea has the most development activity, all of the core developers, and Forgejo have given up tracking Gitea's main branch and are now adrift. Best of luck to them.
> Secondly, how do get in contact with contributors for sponsored work?
CommitGo is the legal vehicle for contracting the core developers. For other contributors, bounties are managed via https://algora.io/go-gitea/home
EDIT (bit better source):
> Gitea Enterprise is an offering of CommitGo, not the Technical Oversight Committee of Gitea or the Gitea project itself. CommitGo remains committed to contributing back functionality to Gitea under the MIT license.
Luckily the Gitea devs had recently implemented `REQUIRE_SIGNIN_VIEW = expensive` as a fix. It was minimally invasive for regular users, most pages can still be accessed without login, and it completely solved the AI bot problem, my traffic and load averages are back to normal.
Thank you Gitea devs for a great product, happy user for over a decade both personally and professionally.
Who is saying those are impossible use cases? I think your two apps have just not updated, that happens often with software.
The deb package here didn't run for me on Debian 12 nor under distrobox Ubuntu, i think the dependency list needs a little attention, but that can be easily solved.
Have you seen the French revolutionary decimal time? It's closer to your proposal but with 10 hours/day instead of 25, for more consistency.
For humans i would say a shorter summary is Linear.app syncs a client IndexedDB with the server using naive last-write-wins, no conflict detection, no OT, no CRDT. There's a global sync ID that the server is in control of. Most of the article describes minutae of the json schema.
Then you wouldn't need a unique kernel/OS image. For devices that have u-boot in ROM the DT is usually there (fdt).
Did AI write the README.md as well?
I love what you've made, docker label orchestration is really convenient, but I would be extremely uncomfortable relying on a vibe-coded backup system.
I found one such switch: Install Linux