timharek-no-pcrdnm.txt (5271B)
1 [1]Skip to content 2 [2]Tim Hårek 3 4 • [3]Blog 5 • [4]About 6 • [5]More… 7 8 1. [6]Home 9 2. [7]Blog 10 3. [8]Goodbye SourceHut 11 12 [9]Tim Hårek Andreassen [10][email protected] [11]PGP key 13 14 Goodbye SourceHut 15 16 Published September 9, 2026 17 3 minutes read 18 19 Back in August, SourceHut wrote about their [12]terms of service regarding LLMs 20 . I was behind on my RSS-reading, so I didn’t learn until last week that this 21 was the new stance. 22 23 The new terms of service, which take effect on September 10th, prohibit 24 original content written with, or which facilitates the use of, LLMs. Using 25 them privately to review your work or ask questions is discouraged, but 26 allowed. They also say they will not go through projects looking for 27 violations, but they expect people to comply, and that makes sense. 28 29 I was not prepared for this. I have been using LLMs to help me do a lot of 30 grunt work for my projects, proof-reading my prose, helping me plan out 31 migrations, and much more, and I don’t plan on stopping. Not all of it goes 32 against the new terms, but I don’t want to second-guess where the line is every 33 time I push something. So this is my excuse to leave and try something new. I 34 have been advocating for using SourceHut, or just not using GitHub, for years, 35 and I know who runs SourceHut, so I completely understand their official stance 36 on the use of LLMs. But I won’t pretend I could happily stay. 37 38 I have always loved the minimal UI and how things are put together, except for 39 how projects (not repos) are configured. The semi-official CLI was top-notch, 40 and I even [13]contributed to it! SourceHut felt snappy, and it was 41 hacker-like! The mailing-list stuff was cool, and it makes sense: everyone can 42 contribute, even without an account. It took some time to get used to, but I 43 got there. The thing I loved the most was the CI/CD system, SourceHut builds. I 44 have even written about it [14]a few times. 45 46 After cloning all my repos and taking copies of my mailing lists and tickets, I 47 am left with 43 repos, a handful of emails and tickets, and five years of happy 48 coding/hacking. 49 50 Since learning about their new stance last week, I have spent a lot of time 51 thinking about what I was going to do. Should I just use bare repos? Should I 52 use [15]cgit? Should I use [16]legit? Should I use [17]Tangled and self-host my 53 own knot (their name for an instance)? Or should I just go back to GitHub full 54 time? I was leaning heavily towards setting up my own [18]atproto [19]PDS. I 55 was reading up on it and listening to podcasts about it. It sounds really cool! 56 But atproto doesn’t officially support private data yet (I believe they’re 57 working on it), which means no private repos, and I’m not familiar with atproto 58 beyond reading about it. I don’t need all the social features either (I left 59 social media behind five years ago). And choosing either cgit or legit would 60 mean I had to give up some of the niceties of collaborating on a project with 61 other people. All of that forced me to look elsewhere. And I settled on a 62 self-hosted instance of [20]Forgejo with its built-in CI-runner (I have 63 thoughts). 64 65 I have spent a lot of time today migrating everything I have from SourceHut to 66 [21]src.timharek.no. I have been working on getting the CI/CD system to work 67 like I want, and I have updated all my public repos on SourceHut to say that 68 they have moved. There’s still work left to do, but I’m 90% there. And I must 69 say, self-hosting my own forge is not that bad — it’s fucking fast — and all 70 the data is stored in my garage. And don’t worry, I haven’t opened any ports on 71 my home network (yet) ;) 72 73 Tagged with 74 75 • [22]#sourcehut 76 • [23]#git 77 • [24]#cicd 78 • [25]#forgejo 79 • [26]#homelab 80 • [27]#ai 81 82 603 words 83 84 [28]Reply via email 85 ← Previous 86 [29]August 2026 87 Next → 88 [30]Kaizen #5: Backups (and a lot more)! 89 Last deploy: 2026-09-30 90 91 • [31]Stats 92 • [32]Privacy 93 • [33]Connect 94 • [34]Subscribe 95 96 97 References: 98 99 [1] https://timharek.no/blog/goodbye-sourcehut/#main 100 [2] https://timharek.no/ 101 [3] https://timharek.no/blog/ 102 [4] https://timharek.no/about/ 103 [5] https://timharek.no/more/ 104 [6] https://timharek.no/ 105 [7] https://timharek.no/blog/ 106 [8] https://timharek.no/blog/goodbye-sourcehut/ 107 [9] https://timharek.no/ 108 [10] mailto:[email protected] 109 [11] https://timharek.no/public-key.asc 110 [12] https://sourcehut.org/blog/2026-08-27-tos-changes-and-llms/ 111 [13] https://git.sr.ht/~xenrox/hut/commit/af9d503fb5da5ab518d98500517753974804d14e 112 [14] https://timharek.no/tags/sourcehut 113 [15] https://git.zx2c4.com/cgit/about/ 114 [16] https://tangled.org/anirudh.fi/legit 115 [17] https://tangled.org/ 116 [18] https://atproto.com/ 117 [19] https://atproto.com/guides/glossary#pds-personal-data-server 118 [20] https://forgejo.org/ 119 [21] https://src.timharek.no/tim 120 [22] https://timharek.no/tags/sourcehut/ 121 [23] https://timharek.no/tags/git/ 122 [24] https://timharek.no/tags/ci/cd/ 123 [25] https://timharek.no/tags/forgejo/ 124 [26] https://timharek.no/tags/homelab/ 125 [27] https://timharek.no/tags/ai/ 126 [28] mailto:[email protected]?subject=RE:%20Goodbye%20SourceHut 127 [29] https://timharek.no/blog/2026-august-recently/ 128 [30] https://timharek.no/blog/kaizen-5/ 129 [31] https://timharek.no/stats/ 130 [32] https://timharek.no/privacy/ 131 [33] https://timharek.no/connect/ 132 [34] https://timharek.no/subscribe/