Cool, that was it! Thanks! 😃
Yeah, I'm looking for my own relays in the event content, but I don't manage to get these into an array.
If I filter for kind 3 I'll get something like this:
[p 7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e]] {"wss://eden.nostr.land":{"read":true,"write":true},...
It seems like the prefered relays just follow the "p" tags.
Do you have an example? I had no problems to get all contacts with something like
pTags := []string{"p"}
allPTags = ev.Tags.GetAll(pTags)
but I don't know how to get the relays.
Yeah, but I don't know how to put this in an array. Do you know how?
Take a look at nip65. I think clients are starting to use it. https://github.com/nostr-protocol/nips/blob/master/65.md
Thanks for the info! Actually I can see the relays with the tags filter but I'm unable to put them in an array. I thought there would be some function for this.
It is a search engine with queries other search engines like google, bing or duckduckgo. You stay anonymous, when you use it. Try my instance if you like: https://search.data.haus
Drinking some beers btw.
I just started using #go-nostr . Can anyone explain me how I can get the prefered relays of a contact?
Use a selfhosted meta search like Searxng. I use this for 2 years now and never looked back.
#jitsi is driving me crazy. To get this thing running on distributed systems like #k8s or even docker swarm you must be Batman.
gm 🍄
And off we go with some more #jitsi UDP routing work...
UDP stream proxying for #jitsi with #kubernetes is a real pain.
np, thanks!
Unfortunately, 0.3.3 still crashes (wrote on GitHub).
Docker version still shows 0.3.1. Image seems up to date.
Please no Google libs. I don't have/want this on my GrapheneOS phone.
Loving #nostr so far. But I would really enjoy some tech focussed people here.
