AT being backed by VC is false—it's Bluesky the company that is. AT is merely a spec for signing, storing and propagating structured data (records) + the identity that owns said records.
Not really. It's very open for everyone to participate. Further, Bluesky has been working on standardizing AT at the IETF [0][1]. They have also made a patent non-agression pledge: https://bsky.social/about/blog/10-01-2025-patent-pledge
In short, they're actively working on making AT as neutral as possible.
We have already talked about this. In the end it comes down the index for the instances that bsky maintain it will inevitably be the dominate ones vs others who run AT Pro.
It would be all good if the index is shared via DHT, bittorrent, ips or other means. Same goes for the google search index, etc.
> 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 the next social collab platform—focused solely on indies & communities.
Darcs & Pijul as the Patch Theory-based approach eliminates an entire class of merge conflicts which make working in a distributed manner more feasible. These DVCS have good (subjectively “better”) foundations & need better tooling like forges—unlike Git that already has a ton of things to choose from.
You don't need to, Jujutsu[1] gives you most of mercurial with some additional stuff. And relevant for this subthread, Tangled appears to work with it[2].
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 place for free software communities.
Also recently wrote about our vision and commitment to indies and communities (and never enterprise!): https://anirudh.fi/future
Aside: Bluesky PDSes are configured to let you upload up to 100MB per blob. Perhaps it might be worth exploring as a medium for hosting release artifacts? Maybe the web interface can merge multiple blobs as fragments of large release files exceeding 100MB (or 15MB for PDSes using the out-of-box config which seems to be the case for Tangled’s instance)
can tangled support a forum-styled or subreddit-like thread discussion interface, on a per-repo basis so that "anyone could start a subreddit" via creating a discussion-only repo?
> public-inbox implements the sharing of an email inbox via git to complement or replace traditional mailing lists. Readers may read via NNTP, IMAP, POP3, Atom feeds or HTML archives.
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.
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 around, or even just archive from GitHub.
Case in point: Gitea (ironically), they’re stuck on GitHub because their 30k+ issues and PRs cannot be migrated from GitHub due to API rate limits.
"Real decentralised thing" here I meant 'using Git in that way that was kind of invented for but no one seems to do,' aka distributed/decentralized with no central server at all.
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!
First Question: is it possible to change your handle or delete your account on the tngl.sh PDS instance?
Second Question: how much resource does creating and hosting a new AppView entail? For example let's say I make an appview that's essentially the PDS-hosted equivalent of Cloudflare Pages, where a user upload a folder of a static website and the appview just forwards it verbatim at a hypothetical https://atprotocities.org/@cool.guy/... , would you need to bear the brunt of the traffic cost as an AppView host?
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?
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.
