East River Source Control

@fromdevoid of course! eventually, we'll have in-repo private files!

@erscio Support for private repos, I hope?

for our friends on X, The Everything App: we have an update on our availability.

@misterclayt0n jj change id. tbd if we want to make a jj-lite of sorts for git users; will depend on customer demand.

@erscio what's the stable identity of a reviewable unit when the underlying commits keep changing? is a review attached to a jj change ID, a git commit hash, a stack position, or an ERAC-native review object, and how does that survive amend, split, squash, reorder, and land?

hello everyone! we're hard at work on a launch. we have scalable monorepo support, jj-first concepts (but deep git compatibility!) and stacked diffs. we're very flattered by the attention today!

@nickgeracehacks @lukerramsden should be fixed now!

@lukerramsden @erscio Someone is looking into it!

@HSVSphere @ellie_huxtable @glcst will need to agree to disagree on atproto (i think centralizing to an appview is fine!), but there are enough features we’d like to do that would be severely at odds with full decentralization.

I don't think ATProto is a good idea for this, forces people down AppViews which end up becoming centralized (bsky.app, tangled.sh, etc). And you still end up hosting separate servers to handle git ops (tangled had to do knots) Locally stored git/jj/etc repos + Libp2p for p2p connectivity, hole punching, identity(public key) + just repo seeding would be a better solution. Radicle.dev stores everything in a git repo (issues, patches, etc everything is a COB, a Collaborative Object), stored in weird git refs, and signs everything to ensure it can be seeded by others. They're working on IO-less core to be able to integrate this into libp2p or iroh too. Repos themselves are public keys too in Radicle, but they don't really have to be. Can do /repo-name easily. For repos with multiple people collaborating, every client fetches each delegate's tip, and sets it to the latest commit that >threshold(configurable) delegates agree on. Banning people is easy too, just reject their COB push onto your repo (like writing a new file in a git ref) Not sure if jj has any "secret revisions", but this can be done in a __private_hack bookmarked branch from the root Also you want to be able to operate on your own repo with only your pubkey, and host the seeder part separately for multi-device (basically don't tie the operation pubkey to the seeder node). This is a WIP in radicle too, and is required for mass adaptation imo.

The only one thing stopping me from moving out of github *right now*: I recently met the folks behind @erscio in person. What they are building is so good, so awesome, so transformational, that I want to wait and see if they can onboard us. Making a change like this is not light, takes a while, and we don't want to be provider hopping. I want to wait for them!!! And praying github doesn't do anything incredibly (even more) insane until then ?

@HSVSphere we are able to understand the jj graph natively when you push the git graph, but we plan on a native jj backend.

@erscio Are you working on a native jj push thing, or can ERAC understand & represent the jj graph natively when you push the git graph?

@ellie_huxtable @HSVSphere @glcst we've got a lot of respect for the design of atproto, but... it's not the right sequencing.

@erscio @HSVSphere @glcst honestly think this is the right way to do it. get something performant and usable first

@HSVSphere @ellie_huxtable @glcst i know. i (david) think atproto is super neat, but we're so heads down on shipping the basics that we didn't think about decentralized stuff. maybe something around identity, but still very early days.

@erscio @ellie_huxtable @glcst :(

@HSVSphere @ellie_huxtable @glcst no, sorry. server side is proprietary; our storage is bespoke and our secret sauce.

@erscio @ellie_huxtable @glcst is it decentralized? maybe even p2p?? actually so excited wow...

@ellie_huxtable @glcst send an email to contact@ersc.io! i'll (david) put you up at the list :D

@erscio @glcst wooo amazing! if there's any possibility to test something early I would LOVE to! best of luck

@ellie_huxtable @glcst soonish, yeah! working pretty darn hard on it. no firm timeline, but... actually soon.

@glcst @erscio I would LOVE to know more about what they're doing! hopefully they can come out with something soon?

@SciumoInc @glcst yea we know

@glcst @erscio @erscio has zero X presence right now