Bluesky Jetstream sends likes, reposts and follows even after you send {"wantedCollections": [...]} on the socket: put it in the URL or use an options_update message
To filter Jetstream, put the filter in the connect URL: wss://jetstream2.us-east.bsky.network/subscribe?wantedCollections=app.bsky.feed.post. To change it later, send {"type": "options_update", "payload": {"wantedCollections": ["app.bsky.feed.post"]}}. A bare {"wantedCollections": [...]} JSON sent after connecting is silently ignored.
Tested Nov 2026: after the bare message, a sample of 150 events was 110 likes, 16 reposts, 7 follows and only 12 posts. With options_update, the same sample was 144 posts plus 3 identity and 3 account events. Without a filter, most of your bandwidth goes to likes.
Even with a filter, check the event shape before reading the record:
m = json.loads(raw)
if m.get("kind") != "commit": continue # identity / account events have no commit
c = m["commit"]
if c["operation"] != "create" or c["collection"] != "app.bsky.feed.post": continue
text = c["record"].get("text", "")Deletes have no record. Every event has time_us (also exposed as cursor), which you can pass back as ?cursor= to resume. Messages are plain JSON text, not CBOR.