Happy 20th UNIX dYear everyone!

Lol, my relay has reliably exceeded 30TB/month for all of 2023. It is a bit wild and inefficient.

I've got a black lightning beanie and a macbook, CTF'ing near the DJ stand.

For anyone at #DefCon I will be in the SomaFM chill-out lounge for the next hour. Anybody who wants to meet up and grab lunch or talk, send me a DM!

Let's do it. Maybe grabbing lunch tomorrow after getting badges?

Anybody going to be at #bsidesLV or #defcon next week? I will be at both, would be great to have an informal Nostr meetup for anyone in LV.

Sorry, this one escaped onto the network, was meant to be local only (and this is a broken example). Reviewing https://github.com/nostr-protocol/nips/pull/635 to see what we should do for escaping control characters other than /n and ", such as the bell character (\b or 0x07).

We made it guys, we are on the map! https://anvaka.github.io/map-of-github/#9.34/-29.1725/45.2594

If you used my sample docs to setup HAproxy for a relay, check out this patch that ensures Damus requests make it to the correct backend: https://git.sr.ht/~gheartsfield/nostr-rs-relay/commit/1595ec783d1312206c0a1d7c66b5bfa1ff83f3a4

Fixed! Minor difference in how Damus sends a Host header (for default ports, damus sends hostname:port, even for default ports) compared to other clients. My HAProxy rules were doing an exact match for the hostname, changed it to a prefix match, and all works!

Loaner iPad acquired, gonna finally figure out why Damus and wellorder relay can't seem to talk. #[0]

What service is hosting that? I am not running on a CDN, but hetzner has free egress (I do 30-50TB/month on my instance for about $40/month).

My impression is there are lots of tradeoffs between concurrency, read/write workloads, appends vs updates, compression, query complexity... LMDB is not known for fast writes, as I understand it.

No problem at all, you have made a good argument with all the confusion in this thread that we need a good relay conformance test suite!

Are you sure that one of those pubkeys doesn't have 40 events more recent than the other?

I can't duplicate on nostr-rs-relay/sqlite. This query shows results for both pubkeys:

```

["REQ", "lim", {"authors": ["35d26e4690cbe1a898af61cc3515661eb5fa763b57bd0b42e45099c8b32fd50f", "887645fef0ce0c3c1218d2f5d8e6132a19304cdc57cd20281d082f38cfea0072"], "limit": 10}]

```

I agree that would be a bug. The query should sort by time, and show the most recent 40 events taking into account both pubkeys and the age of their respective events. I will try and duplicate it myself.

lol, those black keys are like AI hands

Heading back home from bitcoin++; Thanks to all the great speakers, organizers, volunteers, and attendees (best of luck to all for the hackathon) and many new friends. Thanks #[0] for the invite, it was a fantastic experience for me!

Thank you, so glad it went well, and I hope it helped demystify how nostr works for people. This crowd is building such wildly cool stuff.

nostr-rs-relay 0.8.9 out; includes experimental pay-to-relay support, new jemalloc allocator, and other various improvements. https://git.sr.ht/~gheartsfield/nostr-rs-relay/refs/0.8.9

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

wss://nostr-pub.wellorder.net is pumping out >100mbits/sec of nostr traffic right now.