161–170 of 374 posts
Earlier quoted context omitted.
It's the kids. They all like the anime. Not at all like the serious teams I worked with at IBM and DEC that slapped trek logos over everything.
Define kids? I know plenty of Gen X and elder millennials into anime
A full third of them complaining about the anti-bot protection mascot (yes, it's a cartoon character; get over it), others splitting the finest of hairs over software development groups and company politics, and more.
Self-hosting is generally good, well done to FFmpeg. Many large projects self-host, and my own ex-company has physical servers in the city we work at that can be unplugged if necessary.
I just wish Git itself had a more robust means of issue-handling (no, email is a 1980s protocol, it's not good enough, even if it is for Linux) and CI/CD, rather than relegating the matter to different hosts.
And now everyone has to learn GitHub Actions, Gitlab pipelines, Jenkins pipelines, and more.
Earlier quoted context omitted.
It sounds like they're still testing but there's this from https://ffmpeg.org/pipermail/ffmpeg-devel/2025-July/346938.h... : ### July 22nd, 2025, Modernization of contributions The project is modernizing its contribution methods and switching to a software forge. We have setup a platform on [code.ffmpeg.org](https://code.ffmpeg.org/). The new process features continuous integration on all commits and merge requests,…
I wish a certain open source project would take notice of the reasoning here...
Moving to a modern platform with real collaborative development features is a mature move.
OK, not GitHub "because Microsoft". But is there any particular reason why Forgejo and not GitLab, Gitea, or Gogs? I'm not throwing shade at Forgejo or anything like that, I'm genuinely curious if there's anything about Forgejo that made it a better alternative than the other options.
Forejo is/was a soft fork of Gitea due to some licensing / trademark bruhaha that I think got blown somewhat out of proportion. (And Gitea was famous for using Github instead of dogfooding their own software, which I've always thought was a pretty strange choice). I'm not familiar enough with the development roadmap of both teams to make a good call on whether following the fork is a good idea or not, but I know a lo…
I remember thinking a decade ago "wow these guys are biting off a lot to chew, maybe in a decade they'll be able to tackle all these things in a comprehensive way" and my opinion now is they are still probably a decade out. I appreciate their ambition and wish them luck, but it's not for me.
If if a project requires more maintenance than I could potentially do by myself in a pinch because of complexity or having a massive supply chain of dependencies that keep it on a treadmill I will hesitate to depend on it.
Earlier quoted context omitted.
> but I would not use Anubis unless I could disable the imagery, and every time I see it on another site, I think: "hm. weird. whose branding is this?" They do offer an unbranded version, botstopper. It is part of their commercial offering [0] and intended for "professional" environments [0]: https://anubis.techaro.lol/docs/admin/botstopper
Can't fault the logic. Will never use it if that's part of what they've chosen to paywall.
Unbelievable.
Earlier quoted context omitted.
I couldn't care less about the art, but the user-agent discrimination is far worse. Implying that anyone not using an "officially sanctioned" browser is an AI bot is such a devious scheme that I don't think even Google themselves would've come up with it.
I think you've got the logic backwards. It defaults to assuming that user agents that have "Mozilla" in them might be bots. Uncommon browsers don't get challenged. It wouldn't make sense for bad faith bots to use uncommon, easy to block user agents.
How exactly does mailing list contributions work? I've only ever seen a few urls of messages but they are extremely obtuse. You would need to click parent parent parent to get context on the message you originally read. I must be missing something and since mailing lists are dying, would love to understand this relic of the past.
To be honest I think the difficult and learning curve is part of the goal. The people who operate in these worlds don’t want it to be easy for anyone to come along and get involved. One of the main objections to moving to hosted platforms like GitHub or Forgejo is from people who worry it will result in a lot of low quality PRs that have to be dealt with. I’m not suggesting I agree, but it comes up a lot.
Earlier quoted context omitted.
Why would you think this? It is the self hosted part that bothers you? I self host my code. If you can't bother creating an account or sending an email to share your contribution, I guess I'm quite fine not to have it. I'm sure ffmpeg don't need your contribution as well. I don't get this stance. Sending an email or creating an account is so low effort compared to any meaningful contribution. The friction is not inte…
I have contributed to a lot of open source projects for many years. They sure don't need my contribution, but if it were more accessible, I might actually contribute one day. Given that ffmpeg was apparently using mailing lists before (which I didn't know at the time of writing), this is obviously an improvement. But it's still a lot of friction, and it seems that it's friction for no particular reason. Hosting your…
> GitHub is the most popular service by far for a good reason. People build their whole professional portfolio on GitHub, and it's well-known and globally recognized.
I see those things as a big issue. I hate it that github is a monopoly, that open source software projects rely on proprietary software for their infra and that we all depend on Microsoft of all companies for our open source activity.
I personally don't want to participate in helping MS maintain this monopoly.
Hopefully with these developments around forge federation, the "having to create an account is too big of a friction" thing will be less of an issue.
In the meantime, Forgejo already allows login in with open id providers, in many case you are already able to login with your github account.
Earlier quoted context omitted.
Forejo is/was a soft fork of Gitea due to some licensing / trademark bruhaha that I think got blown somewhat out of proportion. (And Gitea was famous for using Github instead of dogfooding their own software, which I've always thought was a pretty strange choice). I'm not familiar enough with the development roadmap of both teams to make a good call on whether following the fork is a good idea or not, but I know a lo…
[flagged]