Why reinvent the wheel when it comes to UI?

Reply to this note

Please Login to reply.

Discussion

Wheel so old. Can't we have a sphere?

This is always proposed (fork an app and add nostr to it) and is almost always a bad idea. It would deserve its own clients and web uis without a centralized DB. The goal is to not just rebuild another github, but instead to do it right on top of nostr.

That's exactly points 4 and 5 from my OP.

I just want tl fork the frontend part not the backend.

I see no value in starting from scratch when it comes to that. Sure a bunch of useless crap has to be stripped down.

No the plan is the keep git. So it’s not clear to me what nostr adds?

The other stuff. Code review, issues, pull requests, patches, etc

Why so much resistance to just doing it all in nostr?

Seems 100x easier than combining git + nostr.

You've yet to explain what is it about git that would improve with nostr.

Tech redundancy.

git is much better for storing git data. Makes more sense to use nostr for the other stuff and is easier not harder

I think it worth a try to fork gitea. Every git service has pretty much the same UI and I think that convention should be followed.