alpha
Login
or
Join now
jack.is
/
leaflet
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
a tool for shared writing and social publishing
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
leaflet
/
app
/
api
/
inngest
/
functions
/
at
feature/pub-pages
12 files
Jared Pereira
don't trigger newsletter sends on firehose update events (#302)
2mo ago
3e9583ca
batched_update_profiles.ts
update inngest to v4
3 months ago
cleanup_expired_oauth_sessions.ts
update inngest to v4
3 months ago
come_online.ts
update inngest to v4
3 months ago
fix_incorrect_site_values.ts
update inngest to v4
3 months ago
fix_standard_document_postref.ts
update inngest to v4
3 months ago
fix_standard_document_publications.ts
update inngest to v4
3 months ago
index_follows.ts
update inngest to v4
3 months ago
index_post_mention.ts
update inngest to v4
3 months ago
migrate_user_to_standard.ts
update inngest to v4
3 months ago
send_post_broadcast.ts
email template fixes
3 months ago
sync_document_metadata.ts
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
write_records_to_pds.ts
update inngest to v4
3 months ago