Sr.ht, the hacker's forge, now open for public alpha

I love this, and wish it well.

I currently host my personal repositories on GitLab, as I see the monoculture that has developed around GitHub to be dangerous for the community in the long term. I went ahead and created an account on sr.ht, and subscribed for the $20 / year plan. Whether or not I end up using the service (though I think I will), I'm happy to spend $20 to support this work.

One note - the billing plans seem to be recurring right now. If you could offer an option to make a one-time payment, that would be much appreciated. If anyone else is interested in subscribing to support the project but doesn't want a recurring charge on their card, you can go to https://meta.sr.ht/billing and "cancel", which will turn off autorenewal but leave your account active for the term for which you've paid.

I love that you are able to support FreeBSD but Travis CI couldn't even be bothered. Is there support for Windows as well?

got a source on that?

I noticed that there's no link from, for example, https://todo.sr.ht/~sircmpwn/man.sr.ht to https://git.sr.ht/~sircmpwn/man.sr.ht - is there any way to link a project's pages together across multiple sr.ht services? Otherwise the navigation isn't so friendly for someone just discovering a project.

>* If we had syntax highlighting in the file browser, that would be a win over GitHub, which insists that there be "hundreds of GitHub repositories" before accepting a syntax highlighting pull request for a new language. I could imagine it would be reasonable to support "repository-local" highlighting configuration.

We use pygments, so patches to pygments would make it to sr.ht's syntax highlighting.

>* Transferring existing content as mentioned above. It would be unwise for us to give up all the issues and discussion.

Planned. Also planned to let you sync between both.

>* The fact that the build service supports FreeBSD is already a win. However, to switch from Azure DevOps we would lose Windows builds. Is that ruled out due to the open source nature of sr.ht, or is that planned? Related, it would be attractive if sir.ht offered more architectures, e.g. i386, ARM, RISC-V (I believe this was mentioned but I could not find it in the docs)

Eventually users will be able to add custom base images, which will permit the use of Windows (if you can get an sshd running there, at least). As for multi-arch, experimental support for aarch64 is there, and by the end of the year I expect to have RISC-V builds backed by HiFive hardware.