bluesky-firehose: fix dead endpoint, upgrade to Jetstream v2, mobile-friendly UI - #308
Merged
Merged
Conversation
The tool was hardcoded to jetstream2.us-east.bsky.network, which currently accepts WebSocket connections but never sends any events, so the page connected and then sat silent. The Jetstream API itself is unchanged - the other three public instances stream fine. Connect now tries each public Jetstream instance in turn, moving on when a connection errors, closes without data, or goes 5 seconds after opening without a first message. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014acKDTPNLLk3iknch2Dsp5
Bluesky's new Protocol Services launch introduced Jetstream v2 at jetstream.us-east.bsky.network and jetstream.us-west.bsky.network. The live /subscribe stream is unchanged: same query parameters, same unauthenticated access, same event JSON, and options_update messages still work (verified by switching a live v2 connection from posts to likes). Put the v2 hosts first in the fallback list and keep the legacy v1 instances as backup. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014acKDTPNLLk3iknch2Dsp5
Drop the legacy v1 Jetstream instances from the fallback list now that the two v2 endpoints are confirmed working. Link to the Jetstream v2 docs and the Protocol Services announcement from the page. Make the layout work better on small screens: wrapping flexbox controls with full-width buttons, border-box textareas, 16px textarea font to avoid iOS focus zoom, horizontal scrolling for the example code block, and tighter spacing under 600px. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014acKDTPNLLk3iknch2Dsp5
Contributor
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
Deploying tools with
|
| Latest commit: |
335a045
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://35d5766f.tools-b1q.pages.dev |
| Branch Preview URL: | https://claude-bluesky-firehose-debu.tools-b1q.pages.dev |
Bluesky-blue accents on the heading, links, and primary buttons, softer bordered panels with rounded corners for the textareas and example code block, hover and focus states, and a subtle off-white page background. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014acKDTPNLLk3iknch2Dsp5
Contributor
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fable 5 PR
Why the tool was broken
The page was hardcoded to
wss://jetstream2.us-east.bsky.network, which currently accepts WebSocket connections but never sends any events — the handshake completes (101 Switching Protocols) and then the stream sits silent forever. Protocol-level testing showed the other public Jetstream instances streaming data within seconds while this one delivered 0 bytes. The Jetstream API itself had not changed.Changes
connect()now walks a list of Jetstream instances, moving to the next one when a connection errors, closes before any data arrives, or opens but delivers no message within 5 seconds (the exact silent-failure mode that broke the tool). The log shows which instance is in use. Also fixed the Connect button passing its click event intoconnect().jetstream.us-east.bsky.networkandjetstream.us-west.bsky.network. Verified they are drop-in compatible: same/subscribequery parameters, same unauthenticated access, same event JSON, andoptions_updatesubscriber messages still work (tested by switching a live v2 connection from posts to likes). The endpoint list now contains only the two v2 instances; legacy v1 instances were dropped.box-sizing: border-boxon textareas so they don't overflow the viewport, 16px textarea font to prevent iOS Safari zoom-on-focus, horizontal scrolling for the example code block, and tighter spacing plus a 50vh log output under 600px.Testing
options_updatefiltering works.🤖 Generated with Claude Code
https://claude.ai/code/session_014acKDTPNLLk3iknch2Dsp5
https://claude.ai/code/session_014acKDTPNLLk3iknch2Dsp5