icy

8 ms·

61.
by icy 11mo ago
> Perhaps a well-known company or individual will announce one; it will have good marketing, and dominate. Hah, exactly what we’re attempting with Tangled! Some big announcements to come fairly soon. We’re positioning ourselves to be th
62.
by icy 11mo ago
We’d love to have the Dillo project on Tangled! ;) https://tangled.org
63.
by icy 11mo ago
You can already do this for tags, but manually. Via CI, you’ll need to set an app password and use goat ( https://tangled.org/oppi.li/goat ) or similar.
64.
by icy 11mo ago
I'm excited to see this migration happen, mostly because it signals to us ( https://tangled.org ) that large projects are willing to switch! We're working pretty hard to get Tangled out of alpha—we want it to be the
65.
Building for the future(icy.leaflet.pub)
2 points by icy 1y ago|0 comments
66.
by icy 1y ago
We’ve considered this a lot. Our issues implementation is threaded—perhaps more Stack Overflow-like. We’re thinking of renaming it to Discussions, and having the actual issue tracker be collaborators-only.
67.
by icy 1y ago
Not yet, unfortunately. Mostly due to protocol limitations—we use AT ( https://atproto.com ) for federation.
68.
by icy 1y ago
Could also consider running a Tangled knot (lightweight, headless git servers): https://tangled.org
69.
by icy 1y ago
We definitely want to be very social-first down the line! Our focus at present is to nail the core features first, however. The vision is to build Tangled to be a indie/community-focused code forge.
70.
by icy 1y ago
> but you cannot even provide PR's other than by email Are you referring to Tangled? If so, that’s patently false.
71.
by icy 1y ago
What’s the “real decentralised thing”? You can already archive your repo—Tangled doesn’t prevent that. AT Protocol is great for when you’re working with the data surrounding your code: issues, pulls etc. which are much harder to move arou
72.
by icy 1y ago
Git repos don't get replicated anywhere. They live on disk, either on our knot server or yours. Knots are essentially our extension to the AT architecture, allowing user ownership of what's essentially "off-protocol data&quot
73.
by icy 1y ago
Hey HN, co-founder of Tangled here! We recently shipped a change to switch out our OAuth library—which introduced a regression, preventing new users from being added to the default knot and spindle (the git hosting server & CI runner).
74.
by icy 1y ago
Nothing preventing that! You can run a knot server[0] on top of your local git server—which I assume you push to using SSH. Knots serve up your git bare repos over an API (and federate over AT Protocol). If Tangled’s appview is down, you ca
75.
by icy 1y ago
You could mirror it, yeah! Perhaps write a spindle pipeline[0] to push back to GitH*b on merge. :) [0]: https://tangled.org/@tangled.org/core/blob/master/docs/spind...
76.
by icy 1y ago
Potentially! We’ve discussed offering a fully airgapped, non-AT version of Tangled. It’ll be a bit of an undertaking so probably not anytime soon.
77.
by icy 1y ago
Hi! Knots just serve up git repositories over an XRPC API. The actual state on disk is really just a sqlite + your git bare repositories—the two can be tarballed and moved elsewhere easily! We will work on more first party backup/migra
78.
Show HN: Tangled – Git collaboration built on AT Protocol(tangled.org)
14 points by icy 1y ago|0 comments
79.
by icy 1y ago
> already provided on the web through hyperlinks. Yeah except there’s no guarantee of structured data there! With AT, each record is specified using a corresponding lexicon—making for much more straightforward interop. > There is seem
80.
by icy 1y ago
Worth mentioning that Tangled has support for stacked pull requests and a unique round-based PR flow with interdiffing: https://blog.tangled.sh/stacking
81.
by icy 1y ago
tangled being in alpha has no bearing on the submitted content whatsoever. i’m confused by this comment. the author being anonymous doesn’t matter either? there’s tons of good software written by pseudonymous authors. i don’t understand wha
82.
Forever Notes: Note-Taking Method for Apple Notes(myforevernotes.com)
2 points by icy 1y ago|1 comments
83.
by icy 1y ago
Yeah, for now orgs/namespaces are their own accounts (even better if you have a dedicated domain for your org). Private repos aren't a thing just yet since we use AT Protocol, and all data on protocol is public -- for now. This
84.
by icy 1y ago
Glad you liked it! Yes, jj's change IDs are very similar to Gerrit's, but instead of a commit trailer it's now a header in the commit object itself. For example: $ git cat-file commit caa00e20 tree e8418bf7e7c626f
85.
by icy 1y ago
We support stacked pull requests tracked using jj's change-ids: https://blog.tangled.sh/stacking
86.
by icy 1y ago
That's the global timeline. If you'd like to look at a demo repositoy https://tangled.sh/@tangled.sh/core is a good one (monorepo for Tangled).
87.
by icy 1y ago
Thanks! Excellent site-wide performance is something we aim for -- hence our stack of Go + htmx!
88.
by icy 1y ago
https://tangled.sh is an atproto (same tech as Bluesky) git collaboration platform. https://blog.tangled.sh/intro We have a more advanced PR flow (stacking, round-based reviews), jujutsu support and we just laun
89.
Journaling using Nix, Vim and coreutils(tangled.sh)
206 points by icy 1y ago|64 comments
90.
The Lifecycle of a Pull Request(blog.tangled.sh)
26 points by icy 1y ago|1 comments

More ›