princess_J20

Q for nostr experts: if I open multiple subscriptions with REQ and a new event arrives at the relay which matches multiple of them, should the relay send the same event multiple times (one for each sub) or just pick one sub and send the event?

2023-02-06 05:10:31

- reply

This GitHub issue is pretty funny. Some Grump wants to get rid of 418 in golang :P he gets wrecked in the emoji reactions though.
https://github.com/golang/go/issues/21326

2023-02-06 04:06:53

- reply

beautiful

2023-02-06 03:47:08

T.I.L. about HTTP Status Codes.
Status Code 200 = OK
Status Code 404 = Not Found
Status Code 418 = I'm a Teapot

2023-02-06 01:11:17

what is NIP 111? Nostream supports it?

2023-02-05 07:42:35

- reply

eesh yeah that sucks!

2023-02-04 17:39:33

- reply

1Q84

2023-02-03 06:27:52

- reply

was looking through
https://nostr.watch/relays/find
but it's a bit time consuming and could not find any after checking a few...

2023-02-03 04:28:11

- reply

One idea: on initialization, clients try to open up websockets to a collection of relays. whichever ones successfully establish a connection are published as a parametrized replaceable event with a fixed Kind "K", with "d" tags equal to the URL of the relay. These events ideally would be "sprayed".
Then, as another user, I could query for kind "K" authored by the user I am interested and get the list of relays, with timestamps, they have connected to. By filtering the query I can get the most recent relays, etc.
Obvious privacy concerns. But a good client could prompt user before sending (i.e., "let people know you were using relay wss://XXX"?), and maybe you could set to not send such updates for certain relays.. etc..

2023-02-01 05:30:08

- reply

jury is still out on that. gossip client is playing the long game. #[4]

2023-02-01 05:23:05

yo #[0] I think you need to have the word "Bitcoin" in your bio for nostrgram. and you need to have a "lud06" field in your kind-0 metadata. https://www.nostr.guru/p/2d5b6404df532de082d9e77f7f4257a6f43fb79bb9de8dd3ac7df5e6d4b500b0

2023-02-01 05:13:03

- reply

...not yet... knowing #[4] it will probably be able to translate in a few days :P

2023-02-01 02:43:18

https://fullmoons.art/gnostr_1.png #[0]

2023-01-31 16:14:23

- reply

hahah me too! great machine :P

2023-01-31 01:27:42

- reply

if you want to run it locally:
https://github.com/barkyq/gnostr

2023-01-31 01:24:14

- reply

hosting a recent build here:
https://gnostr.fullmoons.art/
it's quite alpha and a bit quirky :P

2023-01-31 01:07:59

- reply

it's super bare-bones, but pretty snappy, I find :)

2023-01-31 01:07:20

- reply

haha nice! yeah you definitely inspired the name lol :P

2023-01-30 16:29:28

- reply

well the syncing daemon could listen to other filters. e.g., all notes on any of a list of relays which have me as a "p" tag. if the daemon gets a hit and it is isn't on the special relay you are using while travelling, it republishes the note to the special relay.

2023-01-30 16:12:47

- reply

if you are running daemons at home, I would suggest just running one which syncs your notes between a set of relays. then you can simply post to one relay and the daemon at home will see it, and then rebroadcast it.

2023-01-30 07:44:53

- reply

RIP HashCash

2023-01-30 07:34:15

- reply

...so infuriating...

2023-01-30 04:22:01

- reply

Nice!

2023-01-30 04:11:43

- reply

guess you are working in python for this?

2023-01-30 04:08:44

- reply

NP I would be interested in seeing what these rune phrases are like too, do you have anything posted yet?

2023-01-30 04:00:58

- reply

cool! so what would it be like:
only read from relay wss://abc.com _if_ the filter satisfies some conditions (like must refer to a specific event id?) could be cool, wonder what the other NIP devs think

2023-01-30 03:14:14

- reply

Seems interesting, but not really seeing how it uses NIP-23?