We got a tip from #[0] that he was seeing ONLY #[1] in his posts/posts&replies section of Damus (people you follow). We use primarily Damus so we aren’t sure what impact this has on other clients.

I didn’t think much of it at the time but last night #[2] had only Cameri in her posts too so we started thinking about.

Here’s what happens:

- Damus client makes a request with many authors with certain kind events (1,42,7,6).

- The protocol doesn’t dictate that relays return events in any particular order so some relays return this request sorted by author pubkey and some return it sorted by created_at timestamp.

- Strfry returns this request ordered by author pubkey. Since Cameri has a pubkey with lots of preceding 0s and has posted > 500 times, you will receive exclusively posts from him.

- Nostream returns this request sorted by recency (totally different results).

- nostr-rs-relay returns this request sorted by recency.

When the cache is purged, Damus makes this request with a limit of 500. If the first pubkey has posted more than 500 events, the posts section will appear to be only their most recent 500 events. On subsequent calls, Damus requests this page with a since filter, pulling a more distributed set of events, which makes this phenomenon less noticeable. In either instance, once events are streaming, they will show all recent events.

We’ve made adjustments to filter.nostr.wine to chunk these requests so that you get a more representative sample of posts from people you follow.

Have you paid admission for nostr.wine and PuraVida relays?

That must be annoying AF. I mostly shitpoast.

Ah, yeah - I’ve heard of it. But I’ve never practiced regularly. It’s more of a theta wavelength compared to a meditative alpha? I’ll check out that link. Thanks for sharing!

Websockets are everywhere this week. In addition to the work on nostr.wine, I spent most of today optimizing a push pattern integration that I like to use for distributed and highly available ML models (or really any high compute and/or long running task), which relies heavily on websockets, queues, and pub/sub. One of those “when it rains, it pours things”, but in a good way. Keeps my mind spinning on enhancements we can add to the filter. But now I need to find a good book to read before bed, or I’ll be dreaming about data movement all night.

Anyone have any tried and true ways to get their brains to stop at the end of the day?

My next issue is getting wallet of satoshi working. It gave me a lightning address of fittedrussia90#[1].com. I guess they like stringing random words together.

I've tried to send some sats to this using my exodus wallet; but it just says "Send failed". I guess Exodus and Lightning aren't quite all together yet.

Can someone send me a sat to see if this wallet works? I know, throw pennies at me right? I promise I'm not that uncle in Kenya.

New people! Follow me for a follow back and a zap! #introduction #plebchain #pv #global #saynotoshowergirl

it’s insane how many zaps I’m getting, and this is only testflight! I will try to push a new App Store build soon.

Hey #[1] . I don't quite get what this means as we already ZAP in some clients...

Built the #damus app this afternoon; was absolutely surprised how smooth that went as I have no exp with mobile app dev. Then some good old C progging to fix an issue, pure nostalgia 😊