I haven't looked at which parts of source control they're federating, but one would hope that the developers have enough sense to enhance only the bits that are related to social interactions: change requests, reviewing, commenting, etc, not the repositories themselves.
If you had read to the end of the article you might have noticed that they specifically mentioned private repositories:
This isn’t all. We’re staggering this launch across the next few weeks. Up next are private repos, a CLI, SDKs for different languages and skills for your agent.
yep, the spaces proposal (now in alpha, and already has several implementations!) solves this. we (tangled) have done something very similar here for private repositories. there are many inprogress updates to the protocol (group accounts, permissioned data). we have developed implementations of these based on the proposals, and intend to upgrade to the spec when the spec stabilizes.
I mean how the design of a distributed system preserves the confidentiality of certain information that passes through it. My understanding is that atproto is not designed to preserve privacy, although I'm aware (and skeptical) of some proposals to add such features.
The ones that are not open source. Assuming all code is open source is a little limiting. I mean people can choose to design their forges to accommodate only open source but it excludes a few use cases out there that might somewhat limit adoption. Not only open source projects might want to use federation.
It’s great that people are working on federated forges. I myself a bit meh on ATProto and prefer ForgeFed. Not that I studied them extensively and can give a well reasoned explanation why, more of a gut filling. There are already a few small implementations out there. I can’t wait for Forgejo getting it implemented.
Wake me up when one can change their name in Fediverse… I think ActivityPub got some fundamental stuff wrong from the start, ATproto, while obviously not perfect either, got a lot right.
I'm pretty excited about Tangled, as it seems to aim for a pragmatic decentralised forge, also a lot of overlap on what stuff I like: Svelte, Nix, ATProto.
However reading the blog I also feel the same as reading some more in-depth ATProto stuff, that is, I have no idea what all these special terms mean when I try to put it all together. Appview, firehouse, knots, spindles, bobbins, lexicons; I nod along happily but at the end of it all I'm like: am I too dumb for this?
minimax | 15 hours ago
Should be read in light of https://lobste.rs/s/htgcuc/do_at_proto_users_know_this_is_public
A forge with no privacy model at all doesn't appeal to me, although I can see it certainly has its uses.
[OP] novedevo | 15 hours ago
FWIW, they are planning private repo support soon™: https://news.ycombinator.com/item?id=50307062
arcayr | 7 hours ago
oh nice! i hadn't seen that. i have had issue #60 bookmarked for a long time now. thanks ~icy and team. :)
mariusor | 15 hours ago
I haven't looked at which parts of source control they're federating, but one would hope that the developers have enough sense to enhance only the bits that are related to social interactions: change requests, reviewing, commenting, etc, not the repositories themselves.
uncenter | 11 hours ago
If you had read to the end of the article you might have noticed that they specifically mentioned private repositories:
pksunkara | 13 hours ago
I have read the comments in there and doesn't the new ATproto spaces proposal solve this issue?
Is anyone more knowledgable about ATproto chime in here?
op | 14 minutes ago
yep, the spaces proposal (now in alpha, and already has several implementations!) solves this. we (tangled) have done something very similar here for private repositories. there are many inprogress updates to the protocol (group accounts, permissioned data). we have developed implementations of these based on the proposals, and intend to upgrade to the spec when the spec stabilizes.
ariaaaa | 13 hours ago
what does this mean to you? is it similar to a threat model?
minimax | 13 hours ago
I mean how the design of a distributed system preserves the confidentiality of certain information that passes through it. My understanding is that atproto is not designed to preserve privacy, although I'm aware (and skeptical) of some proposals to add such features.
ariaaaa | 11 hours ago
Right, I see. What parts of your open-source contributions would you want to remain private?
pointlessone | 11 hours ago
The ones that are not open source. Assuming all code is open source is a little limiting. I mean people can choose to design their forges to accommodate only open source but it excludes a few use cases out there that might somewhat limit adoption. Not only open source projects might want to use federation.
ariaaaa | 10 hours ago
Yeah, they seem to be mostly interested in open source for now.
They say they have plans for private repos but we'll see how that works.
singpolyma | 12 hours ago
... why would you want anything on your forge to be private?
tuxes | 4 hours ago
I've considered setting up a private forge because I can't quite get the right auth model for my LLM agents on GitHub.
I want them to be able to read all my repos, and be able to raise PRs, but no commit/merge access.
I know how I could do that with my own private forge.
pointlessone | 13 hours ago
It’s great that people are working on federated forges. I myself a bit meh on ATProto and prefer ForgeFed. Not that I studied them extensively and can give a well reasoned explanation why, more of a gut filling. There are already a few small implementations out there. I can’t wait for Forgejo getting it implemented.
diktomat | 2 hours ago
Wake me up when one can change their name in Fediverse… I think ActivityPub got some fundamental stuff wrong from the start, ATproto, while obviously not perfect either, got a lot right.
zetashift | 12 hours ago
I'm pretty excited about Tangled, as it seems to aim for a pragmatic decentralised forge, also a lot of overlap on what stuff I like: Svelte, Nix, ATProto.
However reading the blog I also feel the same as reading some more in-depth ATProto stuff, that is, I have no idea what all these special terms mean when I try to put it all together. Appview, firehouse, knots, spindles, bobbins, lexicons; I nod along happily but at the end of it all I'm like: am I too dumb for this?
diktomat | 2 hours ago
If you got a few minutes, Dan’s articles linked under tl;dr here are truly great, also explain why/how ATproto differs from ActivityPub.
Knots, spindles, bobbins are Tangled terminology for repo server, CI server and kinda CDN.