As the title implies, private repositories, with seperate view and push access permissions.
atproto doesn't have a concept of "private data" at the moment (we're working on it!), so even if you configured knot's git server to only work with authenticated users on the box, your issues and pull requests will still be public. not even sure if that's possible, honestly...it's just the way i'd think to secure a "bare" git server that doesn't have a fancy UI or anything.
I am very well aware of that — but I thought a tracking issue for when it's possible wouldn't hurt.
Any change we can run a private knot server, not internet facing, and use it to host private repos? I'm all fine if issues are public as long as the content of the repo stays private
The Bluesky team is working on a solution for this called 'Permissioned Data'. You can read more about this in the 'Permissioned Data Diaries' (currently 4 parts).
(spongebob voice) welcome to the future! https://atproto.com/blog/atproto-spaces-alpha
With it now being 2 months since spaces was announced, can an update on the development of private repos be provided? Has implementation started, and what would a rough ETA look like for a first version of it?
From comments by icy (Co-founder / CEO of tangled) on HN
private repos rolling out in the following couple weeks
https://news.ycombinator.com/item?id=50306205
private repos are coming very soon, we have a working demo of private repositories.
I bought a domain to selfhost Tangled on, in anticipation of private repos. This better be good.
+1