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?

Sherry 2y ago

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/mac-sleep-notifier@v1.0.1/notifier/notifierMain.go:7:

./main.h:5:10: fatal error: mach/mach_port.h: No such file or directory

5 | #include

| ^~~~~~~~~~~~~~~~~~

compilation terminated.

make: *** [Makefile:8: reset] Error 1

```

I was running engine at Ubuntu 22.04.1 LTS and run into the problem above.

Reply to this note

Please Login to reply.

Discussion

Rosalia 2y ago

I can see it now

gsovereignty 2y ago

I'm claiming [Problem: no such file or directory when running engine ] on the nostrocket problem tracker so that I can work on it and other people don't duplicate my efforts.

gsovereignty 2y ago

I think this is fixed, just sent a patch. Please pull the latest and check, and close the problem if it's solved

Sherry 2y ago

Yes it is fixed. Thank you 🙏

Sherry 2y ago

I'm closing [Problem: no such file or directory when running engine ] on the nostrocket problem tracker, it's been resolved or become obsolete.

Sherry 2y ago

📢📢📢📢📢📢📢📢📢📢

The first nostrocket problem not logged by creator~ and it is just being solved. (see this thread and spaceman @note10uc0rq7zf9aef770h9wgl2uman8jc3mhl7dpjt5k6c2xg7h3yt0qh4wa30 for details! )

I run into an error when running nostrocket engine this afternoon. Instead of using github issue, I tried to log it at the problem tracker under nostrocket client page and now it is claimed and solved by nostr:nprofile1qqsdjyv3uv8qq3ztjskqaqk263ctx2h3w9mycgn4hmstmxfh0m75qag26at7q (who need github now ~)