Post

- Codeberg - self-hosted Forgejo (I was involved in its creation) - GitHub (ugh) - Tangled looks nice but I haven't really used it My preference would be: - self-hostable (hard requirement) - open source (hard requirement) - federated or distributed (important) - nice UI - Rust + Svelte 😉

It certainly looks promising, though the self hosting looks kinda complex if you want to host the whole thing, right? Kind of like hosting a full Bluesky stack, not something I'd run on an RPi or a $5 VPS along with my Forgejo instance. I might spin up a knot though and play around with it properly.

I'd really like to see better documentation for Tangled, especially about self hosting and also protocols / implementation details that would be needed to create a compatible implementation. It would also be nice to be able to self host the frontend alongside the knot or use third-party frontends.

0 reposts1 like

Also since you mentioned Rust, I'm super curious about the mix of Rust and Go (I see more of the latter). Why was that choice made and how do you decide which to use where?

Aside from your own knot and spindle of course. Their resource consumption depends on your use case, naturally. Definitely possible to run the whole stack on very minimal hardware. Re: docs, expect a massive update on this front (among others) very very soon.

We chose Rust for most of the git / other performance layers. Implementing our own git server gives us a ton of flexibility. We use Go for spindles because it's much easier to write concurrent code + deal with things like containers and VMs. Better ecosystem there overall.