> I used to test out sites on Dillo a lot to see if the experience was absolutely broken Thanks! That should be done more often :-) > Shame to see a project m

> I used to test out sites on Dillo a lot to see if the experience was absolutely broken Thanks! That should be done more often :-) > Shame to see a project moving from a self-hosted Mercurial repository to a US-megacorparate-owned Git repository in Microsoft GitHub Agreed. I decided that it was a good starting point moving to GitHub as a first start, to increase the chances the project gets more visibility and hopefully attract more contributions. I also trust GitHub to be alive for at least 5 to 10 more years, so I can put a redirect notice on the main webpage. But yeah, I agree it would be better to self host or move to a federated forge. There is an issue to cover other options[1], but our current problem is that other forges like Codeberg don't have a way (as a free account) to run the CI pipelines in other platforms like MacOS. My idea was to eventually get hold on some real hardware so we can setup our own runners and also test in different architectures. Feel free to add other alternatives and I will take a look. [1]: https://github.com/dillo-browser/dillo/issues/39 https://github.com/dillo-browser/dillo/issues/39 Keep in mind also, that because the project was previously self-hosted (including the mail server) that created a gigantic single point of failure (which failed very badly) that I'm trying to avoid. > But at least the maintainer is committed to accepting email patches so folks aren’t required to create accounts / accept ToS with them. Yeah, I'm thinking in creating a mailing list for that purpose, but apart from sourcehut (at least on alpha) and googlegroups, I don't know that many places that offer one free of charge.