Live data from Hacker News

Migrating Dillo from GitHub

dillo-browser.org

81–90 of 219 posts

Re: Migrating Dillo from GitHub

#81
post #52

A good reason to move away from GitHub is it is from Microsoft (FAMAG; a company who kissed Trump's ring). Sourcehut is hosted in The Netherlands, and Codeberg in Germany.

What would be nice is an aggregator site one could submit to and everyone just host it on their own internet connection, and nobody be dependent on a source for hosting their projects. Maybe something like bluesky with the AT protocol but with git repositories.

Re: Migrating Dillo from GitHub

#82

> To avoid this problem, I created my own bug tracker software, buggy, which is a very simple C tool that parses plain Markdown files and creates a single HTML page for each bug. I love this. I used to be a big fan of linear (because the alternatives were dog water), but this also opened the question "why even have a seperate, disconnected tool?" Most of my personal projects have a TODO.md somewhere with a list of th…

> As it is simply plain text Well, if your bugs can be specified clearly in plain text and plain text only, then yeah, I'd also advocate for this approach. Unfortunately, that's not really the case in any bigger software project. I need screenshots, video recordings that are 100 megs, cross-issue linking etc. I hate JIRA (of course) but it gets it right.

Even in the case of Dillo, the migrated bugs from GitHub include ZIP files (that are still hosted on GitHub): https://bug.dillo-browser.org/50/

Re: Migrating Dillo from GitHub

#83
post #78
post #18

Earlier quoted context omitted.

In answer to my own question about in-depth decision making, I just found this presentation from February 2025 by seven-year GitHub veteran Joel Hawksley: https://hawksley.org/2025/02/10/lessons-from-5-years-of-ui-a... Relevant quote: > But beyond accessibility and availability, there is also a growing expectation of GitHub being more app-like. > The first case of this was when we rebuilt GitHub projects. Customers w…

Who has ever used github on mobile? I'd like to see their logs about this.

Me, every day.

Re: Migrating Dillo from GitHub

#84
post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

One concern the post brings up - single point of failure. Yes, in this case, blah blah big company microsoft blah blah (I don't disagree, but..). I'm more worried about places like Paypal/Google/etc banning than the beast from Redmond.

Self hosting, it's still a single point of failure and the article arguing "mirroring", well... it allows redundancy with reads but writes?

It's an interesting take on a purist problem.

Re: Migrating Dillo from GitHub

#85
post #56

I hope you will continue maintaining a mirror in GH. Some tools like deepwiki are excellent resources to learn about a codebase when their is not much documentation going around. But these tools only support pulling from GH.

How is pulling dependent on github? Git pulling isn't unique to github and it works over http or ssh?

A neat thing about GitHub is that every file on it can be accessed from URLs like https://raw.githubusercontent.com/simonw/llm-prices/refs/hea... which are served through a CDN with open CORS headers - which means any JavaScript application running anywhere can access them.

Demo: https://tools.simonwillison.net/cors-fetch?url=https%3A%2F%2...

Re: Migrating Dillo from GitHub

#86
post #54

Earlier quoted context omitted.

GitHub pull request pushes you a notification/e-mail to handle the merge, and you have to handle the pull request mostly online. I don't know how you can download the pull request as a set of patches and work offline, but you have to open a branch, merge the PR to that branch, test the things and merge that branch to relevant one. Or you have to download the forked repository, do your tests to see the change is relev…

You could set up a script that lives in the cloud (so you don't have to), receives PRs through webhooks, fetches any associated diff, and stores them in S3 for you to download later. Maybe another script to download them all at once, and apply each diff to its own own branch automatically. Almost everything about git and github/gitlab/etc. can be scripted. You don't have to do anything on their website if you're will…

Why complicate the workflow when it can be solved with a simple e-mail?

> Almost everything about git and github/gitlab/etc. can be scripted.

Moving away from GitHub is more philosophical than technical at this point. I also left the site the day they took Copilot to production.

Re: Migrating Dillo from GitHub

#87
post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

One concern the post brings up - single point of failure. Yes, in this case, blah blah big company microsoft blah blah (I don't disagree, but..). I'm more worried about places like Paypal/Google/etc banning than the beast from Redmond. Self hosting, it's still a single point of failure and the article arguing "mirroring", well... it allows redundancy with reads but writes? It's an interesting take on a purist problem…

I think it’s a fair concern, e.g. forgejo is a simple directory on disk, with an option to make that into an S3 storage. It really is a no brainer to set that up for as much resilience as necessary with various degrees of “advanced” depending on your thread model and experience. The lack of a FAANG/M in the equation makes it even more palatable.

Re: Migrating Dillo from GitHub

#88

Earlier quoted context omitted.

Seems like you found it, but for others: one of the easiest ways to get a PR's diff/patch is to just put .diff or .patch at the end of its URL. I use this all the time! Random PR example, https://github.com/microsoft/vscode/pull/280106 has a diff at https://github.com/microsoft/vscode/pull/280106.diff Another thing that surprises some is that GitHub's forks are actually just "magic" branches. I.e the commits on a for…

It’s bonkers to me that there isn’t a link to the plan patch from the page. Yes, it’s trivial to add a suffix once you know, but lots of people don’t—as evidenced by this thread. Discoverability in UX seems to have completely died.

> It’s bonkers to me that there isn’t a link to the plan patch from the page.

It's yet another brick on the wall of the garden. That's left there for now, but for how long?

IOW, It's deliberate. Plus, GitHub omits to add trivial features (e.g.: deleting projects, "add review" button, etc.) while porting their UI.

It feels like they don't care anymore.

Re: Migrating Dillo from GitHub

#90
post #71
post #60

Earlier quoted context omitted.

> I'm really excited about Forgejo Our product studio with currently around 50 users who need daily git access moved to a self hosted forgejo nearly 2 years ago. I really can’t overstate the positive effects of this transition. Forgejo is a really straightforward Go service with very manageable mental model for storage and config. It’s been easy and cheap to host and maintain, our team has contributed multiple bugfix…

Wait, forgejo offers a built-in container registry? How does that work? I don't see that in the admin section at all.

Just run podman or docker login your.forgejo.instance.address then push to it as normal. An existing repo must exist. You can check the images under site administration -> packages.

Speaking of authentication it also works as an openid provider meaning you can authenticate every other web software that supports it to Forgejo... which in turn can look for users in other sources.

It also has wikis.

Its an underrated piece of software that uses a ridiculous small amount of computer resources.

Post reply on HN