Live data from Hacker News

FFmpeg moves to Forgejo

code.ffmpeg.org

121–130 of 374 posts

Re: FFmpeg moves to Forgejo

#121
post #98

[flagged]

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 code on something as obscure as Forgejo actively makes it hard for people to contribute. Most developers use GitHub, and only have experience with GitHub.

If I have an issue with something, I'll make a PR and move on with my day. But if making that PR involves creating an account on some obscure website and learning a new user interface just to contribute code to a single project, I'll simply pass. It's not worth the hassle.

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.

If you're afraid GitHub is gonna go down one day or kick you out, just mirror your repo to your own git instance. It's been done for decades, and it works very well, without introducing friction.

Re: FFmpeg moves to Forgejo

#123

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.

Linux kernel today is still managed with patches on the mailing list. It shouldn't be hard to see how this can be extremely effective for a maintainer running a programmable editor like Emacs or Vim.

Re: FFmpeg moves to Forgejo

#124
post #77

Earlier quoted context omitted.

To entice people to support the project. See this comment for a breakdown of the finances of the project: https://news.ycombinator.com/item?id=44926915 Once I reach the $5000 per month goal across all funding platforms, features currently exclusive to the private fork of Anubis for corpos (including changing the images and soon HTML templating support: https://anubis.techaro.lol/docs/admin/botstopper ) will be merged…

Any news on the no-script feature? I love the idea of Anubis, but in practice, it has turned more than a few sites that I visit into sites that don't work without javascript. So instead of being happy to see it, I find myself disappointed and frustrated, often deciding not to bother with the site after all.

Admins need to enable the meta refresh challenge: https://anubis.techaro.lol/docs/admin/configuration/challeng...

It's off by default while the false positive, true positive, true negative, and false negative rates are being evaluated. This is how you make changes like that without breaking user expectations.

Re: FFmpeg moves to Forgejo

#125

Earlier quoted context omitted.

It's impressive how much GitHub dominates with so little lock-in. It's so easy to add a new git remote. Yeah GitHub has its own features too, but for a long time free private repo wasn't one of them.

So little lock-in? Git itself is simple, but is their .md file renderer open? Are their workflow runners available anywhere to re-use? The API also has gaps (esp if you wanted to migrate your PRs or Issues over), though I don't remember what was the thing I couldn't achieve with it. But I guess you are referring to indirect, incidental domination like "social" lock-in (I always smile at job application forms asking f…

> but is their .md file renderer open?

This part seems mostly interoperable. GitHub's alternatives seem to have implemented something mostly compatible. If you migrate from github to gitlab or gogs or gitea or forgejo, that part will probably just work.

Worst case, markdown is still mostly readable as is and a commit can fix the odd non working thing.

But 100% agree with the rest of your comment.

GitHub has managed to create a network effect by trying to be a social network and succeeding. They managed to create fomo for code hosting. This very HN post shows this.

Re: FFmpeg moves to Forgejo

#127
post #92
post #74

Earlier quoted context omitted.

"sufficiently tasteful/professional/anodyne" != "wrong"

I would say you are being unnecessarily pedantic: the GP said "anything wrong", and the original comment obviously believes that there is "something wrong" which makes the choice not "sufficiently tasteful/professional/anodyne" (/me looking up "anodyne"). The obvious positive reading of the GP comment is that they disagree anime characters make it not "sufficiently tasteful/professional/anodyne".

You are replying to the GP.

Re: FFmpeg moves to Forgejo

#128
post #100

Earlier quoted context omitted.

Thank you. I'm sorry if I was overly abrasive or rude, but it's getting really old. People have sent me horrible things because of this. I've had to start withdrawing from joining new places under my main identity. Just please take one femtoiota of care that the other side is also a human being with thoughts, feelings, and that they may just be incredibly tired of hearing people complain about something.

I legit didn't read any rudeness, it was a graceful retort. > People have sent me horrible things because of this. That sucks, and I see how it makes my (somewhat) measured reaction scan differently. > Just please take one femtoiota of care that the other side is also a human being with thoughts, feelings, and that they may just be incredibly tired of hearing people complain about something. Your shit rocks, your stu…

> Can't fault the logic. Will never use it if that's part of what they've chosen to paywall.

Is pretty damn rude. It's the kind of thing you say online but would never say face-to-face.

Re: FFmpeg moves to Forgejo

#129
post #98

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…

Since we are talking Git hosting infrastructure here and comparing it to GitHub, can you explain to me what do you mean with "git instance" in "just mirror your repo to your own git instance"?

Re: FFmpeg moves to Forgejo

#130
post #60

With the calm, respectful understanding that everything is subjective and there's no accounting for taste - and in my personal capacity - I do not understand how cutesy anime characters have been deemed sufficiently tasteful/professional/anodyne enough to be displayed to literally every single person who visits my site. With apologies to fans of the art style, it is a negative signal to me. I do not prefer to use Clo…

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.
Post reply on HN