nerdypepper

selfhosted knots default to sha256.

we have already got a working demo of private repositories that works very similarly to atproto spaces alpha, but without requiring spaces to be stabilized, we will have something to show off in the next couple weeks :)

> I really had no backup plans for something like a Neovim plugin's source forge being down

this problem could exist with any package manager, the go package manager is one example, where it allows specifying packages from any git url. we host a mirror of all git repositories on our infra, and serve that when the backing knot is down. you could choose to trust that and pull from there (verifying that the tarball has a known correct hash), the way the go package manager pulls from proxy.golang.org.

for collaboration policies: its already part of the protocol, just needs to be baked into the flagship client!

private repos are coming very soon, we have a working demo of private repositories.

don't need to signup for bsky to try out Tangled however, you can directly just signup for an account with Tangled.

all they would need is an atproto account. you can get one of these on Tangled itself, or bring your own. they can then open issues on your repository.

soon, repos will be able to declare a contribution policy: presently its open to all (anybody can open an issue), but owners can choose to limit this to just contributors for example.

input.djr.com, haven't used a different font in many years!