Nostr Web Client

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?

gsovereignty 2y ago

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 consensus events into RAW (we haven't seen a consensus event for this event height yet and are creating a new lead node in the consensus tree) and ACK (we have seen a consensus event and agree with it).

We should only produce RAW events when we are at the current Bitcoin tip. In the case of a stalled network, we can manually set a flag to produce RAW events when we aren't at the Bitcoin tip so that we can catch up to it.

Reply to this note

Please Login to reply.

Discussion

gsovereignty 2y ago

I'm closing [Problem: we sometimes publish consensus events when we shouldn't] on the nostrocket problem tracker, it's been resolved or become obsolete.