I see you mentioned Radicle. What are the major differences compared to Radicle? Having read just the blog post I would guess it's the source of the identity as a start, so you can use users' existing atproto did s whereas Radicle has to bootstrap a whole new identity web.
Hey, you can indeed push to someone’s knot if they’ve invited you on it. The knot server will automatically populate your ssh pubkeys (if you’ve added them) allowing you to push. :)
The second paragraph of their blog posts suggests Radicle doesn't support central identity. It's really hard to imagine one of the core concepts of Radicle bending (breaking) to allow that.
Building on this, I think Radicle would be described as "peer-to-peer", whereas something like Tangled is "federated". The article differentiates Tangled from other federated systems by saying that you can use a "centralized" ID using AT Protocol, but I don't know if the ID provider itself is centralized, centralized-but-self-hostable, or federated.
atproto uses the DID system, which precedes it by a few years. at the moment, 99% of atproto users have a centralized id from the did:plc database, and a few dozen use did:web. no other DID methods are supported in the tooling yet afaik.
Thanks for this. Looks cool!
I see you mentioned Radicle. What are the major differences compared to Radicle? Having read just the blog post I would guess it's the source of the identity as a start, so you can use users' existing atproto did s whereas Radicle has to bootstrap a whole new identity web.
Great work guys! Haven't had a chance to look into atproto and bluesky, but now because of tangled I will.
Reminds me of git-ssb (git collaboration on top of Secure Scuttlebutt).
https://github.com/hackergrrl/git-ssb-intro
There is also https://github.com/google/git-appraise which uses git-notes and a plugin (with UI server included)
How does authorization work? Is everything pull-only or can you push to someone’s knot?
Hey, you can indeed push to someone’s knot if they’ve invited you on it. The knot server will automatically populate your ssh pubkeys (if you’ve added them) allowing you to push. :)
did you consider integrating atproto with Radicle? if no, why not?
The second paragraph of their blog posts suggests Radicle doesn't support central identity. It's really hard to imagine one of the core concepts of Radicle bending (breaking) to allow that.
Building on this, I think Radicle would be described as "peer-to-peer", whereas something like Tangled is "federated". The article differentiates Tangled from other federated systems by saying that you can use a "centralized" ID using AT Protocol, but I don't know if the ID provider itself is centralized, centralized-but-self-hostable, or federated.
atproto uses the DID system, which precedes it by a few years. at the moment, 99% of atproto users have a centralized id from the did:plc database, and a few dozen use did:web. no other DID methods are supported in the tooling yet afaik.
I'd like to make a feature request for Dark Mode
Populating https://tangled.sh/@tangled.sh/core/issues/new is more likely to get traction than a HN comment
Without giving away too much information here, there is a legitimate reason why I cannot do that at this time.
Noted!
To attract new users, does Tangled plan to offer detailed documentation or migration tools from other Git platforms?