Replying to Avatar wuwei

Problem: nostrocket is not currently applicable to more than a few people

The nostrocket implementation is currently lacking most of the features that are described in the unprotocol.

This means most people are not really able to use nostrocket for very much. It's only really applicable to a few people at this stage because it takes a lot of time and effort to understand what it is and even more to get involved.

Solution: start adding problems nested under this one when it relates to the implementation and UX of Spaceman, Engine, the Relay, etc.

Whenever logging a problem, think: does solving this problem make bring Nostrocket closer to another participant getting involved?
Avatar
OriginalSize 2y ago

Problem: Nostrocket depends on centralized platform GitHub for source code management

While the problems in Spaceman are assembled from Nostr notes, submission of patches is done through GitHub. The problem is that GitHub has the power to restrict users and projects from using its platform. Case in point, I created a Github account specifically to contribute to Nostrocket but it was shadowbanned. GitHub support responded to a support request with, "Your account has been hidden from view as it appears to have been one of many created in an account farming effort." even though it's only the second account I've created.

Proposed solution: Store source code in nostr notes and manage patches through Nostr. Available tools that may help are git-nostr and git-nostr-tools listed at https://github.com/aljazceru/awesome-nostr

Reply to this note

Please Login to reply.

Discussion

No replies yet.