Ryan Barrett

This is a bit more acute than I realized. For misconfigured subscribers that always start with the same old cursor, if they don't get through the full rollback window in...

In the meantime, I added an occasional 10ms sleep to pre-rollback subscribers to try to keep them from starving the firehose consumer thread, 1dc0e0b6f5342eaf168a7d48d8db29afc09086dc. Seems to be working.

Damn, it wasn't enough. Even with the sleeps, our consumer thread falls behind once we hit 9 subscribers. Guess I need to prioritize this after all.

Design notes: * Dedicated collector threads for each window. Start one when we start a new window. * No preload? * Use a thread-safe consumer-oriented structure for each window, eg...

Fwiw right now, with just one pre-rollback subscriber, it takes us ~1h to load a full ~45k (50k - 4k preload) rollback window.

Maybe deprioritizing? We're holding pretty steady at ~7 relays connected these days, and the last few restarts, we've loaded the rollback window pretty easily, within an hr or so.

So weird. We always manage to fill the rollback window quickly when the hub restarts on its own, but when we deploy a new version, it consistently takes many hours....

Hi! Hmm, interesting use case. Out of curiosity, I'm not aware of any link preview generators that use `u-photo` specifically. Are you? Also, are you maybe looking for [`u-featured`](https://indieweb.org/featured) instead?...

Glad u-featured sounds ok! Assuming this is for blog posts like eg https://cpf.sh/blog/2025/07/06/we-are-all-creatives-genai-threatens-us-all , u-featured is definitely what you want, not u-photo. From https://microformats.org/wiki/h-entry#u-photo (emphasis mine): > **u-photo** - one...

Hah, yes! Great point. It probably shouldn't. I'll take a look at that.