leaflet/appview/ at feature/pub-pages · jack.is/leaflet · Tangled

jack.is / leaflet

0

a tool for shared writing and social publishing

0

leaflet / appview /

at feature/pub-pages 3 files

Jared Pereira don't trigger newsletter sends on firehose update events (#302) 2mo ago

don't trigger newsletter sends on firehose update events (#302) The firehose UPDATE path was also running the newsletter claim/send logic. Combined with the fact that the idempotency row in publication_post_sends is only inserted when newsletters are enabled at upsert time, this meant that editing an old post after newsletters were turned on for the publication would mail the post out to subscribers retroactively. Gate the newsletter block on event_type === "create" so only firehose creates can fire sends. Metadata sync (indexed flag, bsky like counts, bridgy deletion) still runs on updates as before. Co-authored-by: Claude <noreply@anthropic.com>

2 months ago

Feature/reader (#224) * started the reader * pulling in the right data, styling adjustments * changed styles for pub listing, added stuff to SubscriptionContent * added empty states and fixed some issues * moved discover from reader header to nav sidebar * added comment and quote counts to post listing, cleaned up some other stuff * fixed little alignment issue thing * mostly removing console logs * some pageheader color and spacing fixes as well as getting share button to work in reader * shenanigans making a silly separator show sometimes and not others * thing i did that seemed smart was actually dumb, reversing lol * wip start to paginate followers * add infinite scrolling feed * make subscriptions infinite scrolling as well * use shared idresolver instance * use compound cursors and fix subscriptions pagination * fix getting last updated date for pubs * make handles consistent * store tab state in search params * fix compound cursor logic * remove unread state from reader and text from discover * make external links a's --------- Co-authored-by: celine <celine@hyperlink.academy>

9 months ago

don't trigger newsletter sends on firehose update events (#302) The firehose UPDATE path was also running the newsletter claim/send logic. Combined with the fact that the idempotency row in publication_post_sends is only inserted when newsletters are enabled at upsert time, this meant that editing an old post after newsletters were turned on for the publication would mail the post out to subscribers retroactively. Gate the newsletter block on event_type === "create" so only firehose creates can fire sends. Metadata sync (indexed flag, bsky like counts, bridgy deletion) still runs on updates as before. Co-authored-by: Claude <noreply@anthropic.com>

2 months ago