New tomorrow: "Spaghetti", a no-code platform to run your business on, and "Lock-in", a vault to keep all your important data safe.
Tangled, a Git collaboration platform built on atproto
51–60 of 88 posts
Re: Tangled, a Git collaboration platform built on atproto
#52Earlier quoted context omitted.
One easy way to tell is to browse lexicons ( https://ufos.microcosm.blue/ ) and filter by "sh.tangled". For example, I can see: - https://ufos.microcosm.blue/collection/?nsid=sh.tangled.repo - https://ufos.microcosm.blue/collection/?nsid=sh.tangled.publ... - https://ufos.microcosm.blue/collection/?nsid=sh.tangled.repo... Here's a link to all of them: https://ufos.microcosm.blue/collection/?prefix=sh.tangled
Having a hard time understanding what that website is showing (eg. what is a lexicon?). Could you explain? Is it meant to be some kind of filtered sampling from the stream of ATProto events?
Yes.
Think of these as names of tables (or collections) in a distributed database. Or as type definitions. Or as app-defined data formats.
Each lexicon is a schema for a model. So you’re looking at a list of such “types” — a “repo”, a “follow”, a “star” etc.
There’s a “Tangled repo” lexicon, a “Bluesky post” lexicon, a “Leaflet publication” lexicon, and so on. Lexicons are specified and evolved by developers of each concrete application. Other apps can use those type definitions to read or write that kind of data.
See https://www.pfrazee.com/blog/why-not-rdf#lexicon for a short intro.
The UFO tool samples the global event stream and keeps stats on which lexicons are showing up in it (i.e. types of JSON that are being created on the network). You can expand the “samples” tab to show a few concrete JSON blobs so you get the idea of what the data represents.
Re: Tangled, a Git collaboration platform built on atproto
#53This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies. I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services. For example, most forges: host your git repo, web view, collab too…
"Git is already decentralized"
Decentralized is a big word.
Git never tackled the decentralized aspect, being served over a master-slave protocol like HTTP means you have a tendency to centralize it again.
Re: Tangled, a Git collaboration platform built on atproto
#54This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies. I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services. For example, most forges: host your git repo, web view, collab too…
There is stagit as well, but it does not support branches:
https://codemadness.org/stagit.html
Does Pgit support branches?
Re: Tangled, a Git collaboration platform built on atproto
#55Github is no longer a trusted nor a reliable platform. Moving at least the oss stack to atproto (or any other open network) is an excellent way to safeguard it against Big Tech, Government censorship etc. Love to see this.
Re: Tangled, a Git collaboration platform built on atproto
#56Earlier quoted context omitted.
I see you hand waved people who pay money so that forges can operate. If you have a company you don’t want to pay 20 invoices to different vendors. If you have a company you don’t want to deal with debugging integration between your CI/CD and web view and git providers, you want to make a ticket and have it fixed. When you are developing a project you don’t want to spend time figuring out which task management will i…
Inevitably someone will end up paying for Tangled. Their architecture demands an infrastructure piece that actually hosts the forges and PDSs through BlueSky won't always be free. They're also non-trivial to run.
The vast majority of this comment is false, btw
The infrastructure to host the forges is still a problem yes, but PDSes are VERY trivial to run, they’re just a Node.js app and they have a Compose file to make running it a quick shell script to run. And they will always be free, Bluesky is well aware that making access to the platform a paid thing would kill the project outright, and even then the code is open source and in the process of being written up as an RFC, so… please fact check your comments before posting :)
Re: Tangled, a Git collaboration platform built on atproto
#57Earlier quoted context omitted.
Does Tangled offer any solutions or suggestions for backing up data stored on the Knots?
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/migrate solutions though.
That sounds reasonable, but do your repos get replicated into your PDS? Where else does the data end up?
Re: Tangled, a Git collaboration platform built on atproto
#58Earlier quoted context omitted.
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/migrate solutions though.
That sounds reasonable, but do your repos get replicated into your PDS? Where else does the data end up?
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" (git).
Re: Tangled, a Git collaboration platform built on atproto
#59Earlier quoted context omitted.
Inevitably someone will end up paying for Tangled. Their architecture demands an infrastructure piece that actually hosts the forges and PDSs through BlueSky won't always be free. They're also non-trivial to run.
The vast majority of this comment is false, btw The infrastructure to host the forges is still a problem yes, but PDSes are VERY trivial to run, they’re just a Node.js app and they have a Compose file to make running it a quick shell script to run. And they will always be free, Bluesky is well aware that making access to the platform a paid thing would kill the project outright, and even then the code is open source…
Regardless that increases the barrier to entry for the median developer compared to e.g. Github. In any case, there are several other providers for PDSs coming up and infra is one of the hot areas in the atproto community
Re: Tangled, a Git collaboration platform built on atproto
#60Hey 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). We just discovered this and pushed a fix—please log out and log back in again and you should be able to create repositories! Otherwise, happy to answer any questions!
Cool product! Knowing a little bit of AT protocol, I can assume that the expression you used, “social-enabled”, is related to that. Does Tangled have plans for more social features or social-enabled simply means AT protocol?