Ok. Yeah I was testing strfry stuff on my development machine. Maybe make an exception for localhost?

Idk. I know you had a line of thought to decide to limit it, but I don’t know what it was, so I’m not criticizing. I guess I could change that in my wording branch just for my case.

Thx 🙏

Reply to this note

Please Login to reply.

Discussion

*working

Thwarted by spellcheck again. 🙄

You can fork gossip and tweak it. In particular you'll have to fork nostr-types, edit src/types/url.rs and search for "is_global". Then you'll need your gossip Cargo.toml to use your local fork of nostr-types.

oh, and you'll need to fork gossip-relay-picker just to make it use the same local fork of nostr-types otherwise rust will see them as different types. Then make gossip use your fork of gossip-relay-picker.

I’ll do that and keep a “relay testing” copy with a different nsec, etc.

Good thinking. 👍

Make use of your hosts file. Put host name in gossip. >> profit

Who is this genius? I don't have your relays. Can't get your metadata.

But yes nostr:npub1wtuh24gpuxjyvnmjwlvxzg8k0elhasagfmmgz0x8vp4ltcy8ples54e7js try this first, way easier.

Tis a smart thing to try. 👍

I'm curious why you see no metadata, I would assume you at least see displayname?

If you don’t share a relay, you’d be just a pubkey I believe.

Looks to me like I share several🤔

I've got your metadata now. But I restarted the client not to long ago. No, I wasn't seeing displayname alphakamp. I am now.

I guess I could investigate by pulling your events (kinds 0, 3, 10002) from relays and seeing what is up, but I'm feeling sleepy

It’s about that time here too.

I assume you mean from gossip?

Pulling the events from relays. I want to see which relays have your events. Then use that data to find out why gossip didn't have them.