wuwei on nostr

Open in Damus

Problem: we don't have a good way to focus the action of multiple humans while remaining sovereign When Bitcoiners organise around shared goals, they tend to rely on the State to anchor their organis...

wuwei @wuwei 1688384724

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?

19🤙2

gsovereignty · 169w

Problem: the Nostrocket problem tracker is clunky and annoying to use Now that we are using the Nostrocket problem tracker to build nostrocket itself, the most pressing problem is that the problem tracker is annoying to use. Solution: Log problems with the problem tracker, nest them under this pro...

gsovereignty · 169w

Problem: people can't use Nostrocket for their own projects It's somewhat possible for people other than myself to begin working on nostrocket, but no one can use Nostrocket for their own projects.

gsovereignty · 169w

Problem: the Nostrocket Unprotocol cannot be read by anyone No one can actually read the nostrocket unprotocol because it has not been published anywhere. Solution: implement primitives of the protocol, which allows the protocol to build itself according to the protocol.

gsovereignty · 169w

Problem: spaceman site gets fully re-rendered every time state gets updated This is pretty annoying. Especially when adding problems to the problem tracker.

gsovereignty · 169w

Problem: segfault in eventcatcher ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x1044c9564] goroutine 20 [running]: nostrocket/messaging/eventcatcher.SubscribeToTree(0x1400008c120, 0x1400006a300, 0x1400008c...

gsovereignty · 168w

Problem: can't submit merit requests Merit requests are how we indicate and communicate the value we believe our work has in comparison to that of others. This is the basis by which merit cap tables enter nostrocket state in order to distribute revenue when someone pays for a product or service of...

gsovereignty · 168w

Problem: difficult to see how merits relate to different participants The page displaying merits is not very clear about who has what merits soution: use some borders etc to show groupings of different rockets and merits

gsovereignty · 167w

Problem: can't test the Merits state machine I have implemented Merits. But I can't test this without impacting the mainnet state. Solution: create a new rocket for testing things

gsovereignty · 167w

Problem: can't vote on merit requests People can log merit requests in response to problems they have solved, but the existing merit holders cannot approve or reject these requests

gsovereignty · 167w

Problem: people without any solved problems can't see merit request page There's a bug preventing the merit request page from rendering if the person logged in does not have any closed/solved problems.

gsovereignty · 166w

Problem: invalid memory address or nil pointer dereference in eventcatcher.go:88 ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102b89298] goroutine 37 [running]: nostrocket/messaging/eventcatcher.Subscribe...

Problem: no such file or directory when running engine ``` rm -rf ~/nostrocket/data go mod tidy go run cmd/engine/*.go # github.com/prashantgupta24/mac-sleep-notifier/notifier In file included from ../../go/pkg/mod/github.com/prashantgupta24/[email protected]/notifier/notifierMain.go:7: ....

gsovereignty · 166w

Problem: we sometimes create a new consensus tree when we shouldn't Sometimes when reproducing the current state of nostrocket, it publishes a new consensus tree when one exists already. It seems to be missing an event or something. Solution: A quick and dirty solution would be to check the times...

gsovereignty · 166w

Problem: there is no maintainer tree Some actions require a maintainer - e.g. changing which rocket a problem is tagged with, closing a problem if the person who logged it disappears, merging pull requests, etc. The maintainer tree is documented in the Nostrocket Unprotocol but it has not been imp...

gsovereignty · 165w

Problem: can't modify products I want to be able to modify the description of a nostrocket product that I have created but this is currently not possible. Solution: allow the product creator or a maintainer (of the parent rocket) to update product data (price, and the event ID of the product descr...

gsovereignty · 163w

Problem: we sometimes publish consensus events when we shouldn't Sometimes when consensus events are slow to come from relays we start building a new consensus leaf node when a better one already exists but we just don't know about it. I think simplest way to deal with this is to classify consensu...

gsovereignty · 163w

Problem: deadlock in consensus handler ``` Previous place where the lock was grabbed goroutine 22 lock 0xc0005259f0 engine/library/debug.go:9 library.ValidateSaneExecutionTime { mu.Lock() } <<<<< ~/go/pkg/mod/github.com/sasha-s/[email protected]/deadlock.go:84 go-deadlock.(*Mutex).Lock { func (m *...

gsovereignty · 163w

Problem: merit requests can be submitted to the wrong rocket Arkinox just submitted a merit request which SHOULD have been sent to the Flame Bucket rocket, but was instead sent to the master nostrocket rocket. Solution: Engine: validate problem rocket and merit rocket match Client: don't let user ...