conquered gRPC! saturday evening well spent 😂
agree. at least let relay operator identify who you are, and what you’re upto by having reverse ip and identifying user agent.
she’s a good egg, and funny too. i see the hate in the comments and it astounds me tbh.
hello 👋
fasten
Nicola Sturgeon is simply not believable or trustworthy. Everything is spin. I'm so glad she's gone.
🤨
not so much, she’s been a great first minister
nice one, where you planning on visiting in scotland? if you’re in edinburgh i’ll take you for a beer 🍺🤙
same kind of applies for content type a week as content topic. i might want to see someone’s notes but not their instagram type photos, git contributions or group messages. do i need a separate identity? or do clients specify what content types they accept and send, kind of like http does.
nostr-rs-relay now supports gRPC for filtering events to your relay! Free relays can now fight back against spam. Still experimental, but check out the schema, and build cool stuff: https://git.sr.ht/~gheartsfield/nostr-rs-relay/tree/master/item/proto/nauthz.proto
can’t wait to have a play with this
#[0]
love it #[0] 🤙
posts & replies mostly
i admire anyone who makes things. unfortunately he seems to be destroying something right now.
Picked up some costa rican coffee, feeling the PV vibes today ☕️🇨🇷
yes!
on my micro relay it’s processor that is the occasional bottleneck, nothing else
#[4] When I use https://nostrgraph.net/relay_recommendation, I notice that even when I put in my own npub, it's saying "Recommended Relays for @wakoinc".
Is that just a typo, or is it actually checking your npub rather than the one I input?
same
i think it’s seeded from https://github.com/dskvr/nostr-watch/blob/develop/relays.yaml
i’m not convinced `ss -s` is a super accurate count. i think it counts all kinds of other connections. i’m no expert, but i think restricting to https ports for example gives a more accurate figure, e.g. `ss -at '( dport = :443 or sport = :443 )'`
i’d love to see other thoughts on this though