I have been using SourceHut since the alpha went public. I think the hardest thing to adjust to is patchsets being sent over email. But when you think about it that is the way git is supposed to work. It keeps version control decentralized. Drew DeVault has also created a site git-email.io I believe to help new users with the process. He has also either implemented or is implementing a good web interface to sit on top of patchsets.<p>It is nice knowing that your data is actually protected and private because Drew is very public about his ideals.<p>One of the cooler features I think is the site runs without JavaScript entirely, unless you need to pay for the first time, which uses Stripe, but even then Drew allows for alternative methods of payments including walking up to him at FOSDEM and giving him a check.<p>The communication of the service to its users is actually really nice. You get monthly updates regarding development, and quarterly updates which I will are similar to like state of the union addresses, where Drew will talk about the financial situation in detail, including a line item receipt of expenses like new hardware and salaries. Drew used to put his own salary down, but since Simon Ser was hired to work for SourceHut, Drew has chosen to protect Simon's salary and reports salary payouts in totality.<p>The performance is also a big bonus. Consistently you will find that SourceHut just outperforms GitHub and GitLab on SSH operations. Now this might have a lot to do with the amount of users who use the site, but if you watch the dev mailing list, performance is a top priority. And it is funny watching Drew complain about Python on Mastodon every once in a while.<p>As far as self-hosting, the documentation seems fairly straightforward. You can pick and choose the services you want, so unlike other options where its all or nothing you can cater to your needs. You can also just move to SourceHut incrementally. Some projects use lists.sr.ht but keep code elsewhere. Some use git.sr.ht, but run CI on Travis. Some use the github.com, but use builds.sr.ht. Any combination is possible.<p>I definitely recommend using the service. Later this year the service will be in beta, and there are some good features coming right around the corner including names.sr.ht and hub.sr.ht.<p>Important note that at least during the alpha you can use the entire site for free. Pricing is a pay what you want scale (for sr.ht, there are 3 options), but you get all the features.