still no takers as far as I know

Reply to this note

Please Login to reply.

Discussion

back in january I started working on a github replacement.... until I saw the bounty get posted;

I thought it would immediately get filled so I moved on to other stuff

can't believe it's April and it's still not ready

My team and I are working on it daily. Adding large file support in a secure manner is not easy. NIP-94 will not working for large files like repos due to delay attacks. Great things take time.

Awesome! Thoughts on this protocol for file transfers? nostr:note1es4674ajsdp3n5w8asyhdt3d7qkcdw4rpalkhkuglj74nljh8pvsn0nlhm seems like a new approach at the very least

I saw this the other day. Looks overly complicated. We’ve evolved Merkle DAGs significantly. Excited to share when it’s ready. You’ll see! I promise it’ll be worth the wait.

I agree

I don't think a github replacement should be a bounty itself: it's too large a project imo

are you planning on keeping the repo itself on relays???

I disagree. It’s the only way I was able to motivate a few other coders to help me with the project. Robin at ZeroSync even cracked Sats4File — a way to atomically swap files for coins off-chain over Lightning.

Yes, repos are stored on relays — but it isn’t quite that simple. We’re creating a layered architecture. It will take a few more months, but I’m hoping an open-source beta will be ready by November.

Any ZeroSync people on nostr?

Can you link the repo? Would love to see the building process and everything you and your team have already come up with.

It’s too much of a mess right now. We’ll open-source everything when it’s ready. Satoshi released a solid paper, then functional code. We’re following the same style.

Thought it would not be open source yet or I would have found it by now. So does that mean you're communicating with the team privately also?

Satoshi posted super shitty code too; he didn’t wait to make it all nice, and pretty and functional

I don’t understand the approach of building it in stealth mode, honestly;

don’t you think your approach/designs/implementations might benefit from people who are not exclusively in your team?

Super shitty code that worked, though. Everyone can critique our alpha/beta when it’s ready. I’ve chatted with Naval, Robin from ZeroSync, and other people I respect/trust about the fundamentals already.

ok, so sounds like you consider that you've discussed this with enough experts to not benefit from opening the designs

ok, sure, let me ask you this, then:

do you not feel like opening the architecture/design might help inspire building some other stuff?

I honestly don't understand what's the reticence to opening it up, is it that you want to prevent others from copying it or something like that?

What are you talking about? I’ve opened up a ton about it. I wrote about it on Twitter before the bounty even began.

We’re not releasing code until it works, that doesn’t mean we’re being secretive about how it works. Just read the paper: https://medium.com/@colbyserpa/nostr-2-0-layer-2-off-chain-data-storage-b7d299078c60

Wait is not open source now?

Why isn’t docker a good alternative to GitHub as it supports open source and the code can run in clean environment too?