It’s been a few weeks, but I finally found time to “join the fediverse” by setting up my own ActivityPub-compatible server. No, it’s not Mastodon, but that doesn’t really matter. TLDR: you can now follow @email@example.com.
a place where my shitposts started conversations (or at least joke threads), and where I could participate in conversations (or at least joke threads) on other people’s shitposts
a comments section for my blog that wasn’t on my blog, and a comments section for others’ blogs even if they don’t have one on their blog
a place to learn about other cool people and projects through the people I already know, and a place for other people to learn about me and my projects through the people they already know
When I was getting the code in the previous post ready to share, I ran into a problem: my checkouts of LLVM and Swift were shallow clones, i.e. git repositories that don’t store the full history of each branch. Working with those locally is surprisingly easy; trying to set them up on a server using
git push is a bit trickier. While trying to figure out what was going on, I was dismayed by the lack of up-to-date documentation about shallow repositories, even on my usual go-to site, git-scm.com. So here’s a collection of information I’ve gathered about shallow repositories.
- 2020-01-22 Setting up gitweb on Shared Hosting