engineering blog at https://blog.tangled.org
intro: minor rewording
+9
-9
+9
-9
pages/blog/intro.md
+9
-9
pages/blog/intro.md
···
15
15
open source communities can freely self-govern and most importantly,
16
16
coding can be social and fun again.
17
17
18
-
There are several models for decentralized social networks, ranging from
19
-
ActivityPub's federated model, to Radicle's entirely P2P model. Our
20
-
approach attempts to be the best of both worlds by adopting atproto -- a
21
-
protocol for building decentralized social applications with a central
22
-
identity.
18
+
There are several models for decentralized code collaboration platforms,
19
+
ranging from ActivityPub's (Forgejo) federated model, to Radicle's
20
+
entirely P2P model. Our approach attempts to be the best of both worlds
21
+
by adopting atproto -- a protocol for building decentralized social
22
+
applications with a central identity.
23
23
24
24
25
25
···
34
34
clone and contribute to repositories hosted across different knots --
35
35
completely seamlessly.
36
36
37
-
Tangled is still in its infancy, and we're still building out several of
38
-
its core features as we dogfood it ourselves. We developed these three
39
-
core tenets to guide our decisions:
37
+
Tangled is still in its infancy, and we're building out several of its
38
+
core features as we dogfood it ourselves. We developed these three core
39
+
tenets to guide our decisions:
40
40
41
41
1. Ownership of data
42
42
2. Low barrier to entry
···
44
44
45
45
Collaborating on code isn't easy, and the tools and workflows we use
46
46
should feel natural and stay out of the way. Tangled's architecture
47
-
enables common workflows to work as you'd expect, while remaining
47
+
enables common workflows to work as you'd expect, all while remaining
48
48
decentralized.
49
49
50
50
We believe that atproto has greatly simplfied one of the hardest parts