-
Notifications
You must be signed in to change notification settings - Fork 53
Discussion: how do we want to handle relay pooling? #40
Comments
I think it depends on the use case you have in mind. I've removed the default I don't know what should be made of noscl. Is it being used for someone actually browsing their social feed and interacting with people? Or is it more like a developer debugging tool? Or what? What do you think? |
I personally use noscl as a developer debugging tool and I think there are many clients better suited for social. Viewed through this lens, should - noscl publish [--reference=<id>...] [--profile=<id>...] <content>
+ noscl publish [--reference=<id>...] [--relays=<urls>...] [--profile=<id>...] <content> |
What if we add an optional
This would allow us to remove the dependency on |
I think it may be time to revamp noscl entirely and make it a pure developer tool, with (optional) stdin inputs and always JSON outputs, probably, so they can be consumed by other tools. And for having an actual "social" experience on the CLI https://github.com/mattn/algia is probably better (although I haven't tried it). |
I think that's a great direction and am happy to help with the effort, as needed. |
The
go-nostr
library deprecated theRelayPool
mechanism. We need to implement our own if we want to upgrade to newer versions of the library.Do we have any thoughts on how to handle that?
The text was updated successfully, but these errors were encountered: