Replying to Avatar DanConwayDev

Is your intention to build something that other people would use or for personal use?

At the moment I think the direction nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s and seem to approve of is using the patch model. Everything else appears not to be fleshed out.

I think the patch model doesn't scale but is a good starting point because of it's simplicity.

I am not used to working in public either. There hasn't been any engagement with my long form posts on the issue. No one has commented on my draft NIP. My plan is to build a prototype and put it out there.

Eventually I want to publish some open source software. Not necessarily on nostr

but I really liked the protocol and I was like what the hell, let's see if it works.

Reply to this note

Please Login to reply.

Discussion

That being said, I understand that there is one major problem with my approach

which would prevent frequently updated, big repos from being posted this way: bandwidth.

One would need to reupload the entire repo for the tiniest of changes.

Works for small / infrequently updated projects ( that's mostly what I work with ).

Fails spectacularly for big ones.

I'll take a look at your approach early next week if you'd like some feedback. I'll be a bit busy during the weekend.

Have fun coding.

Actually I just realized the bandwidth issue isn't that bad...

The repo could just mark certain patches as ACCEPTED, and it would be enough to write them periodically to the repo data.

Like every day or every week. No need to reupload everything for each patch.