Launch pass: hero replay GIF, comparison table, and a live LINK chip in open mode#51
Merged
Conversation
An open-mode backend (ALLOW_UNAUTHENTICATED) accepts the alerts upgrade without a key, but the keyless client skipped the WebSocket entirely, so every fresh 'docker compose up' showed a permanent red LINK-down chip. Attempt the upgrade once: adopt the socket if it opens; if an enforcing backend rejects it before open, stay closed with no reconnect loop (the old skip existed to avoid backoff spam, which only retries can cause).
…ortem README: replace the static hero with a real 19 s capture (live world, fly-in to Europe, an airliner selected with its owned track, the last hour rewound on the scrubber) and add a free-tier comparison table against Flightradar24, MarineTraffic and ADS-B Exchange above the fold. The r/DataHoarder launch post doc gains its outcome: the post was removed or filtered before anyone saw it (absent from sub search and the account's public submitted page; repo traffic showed no spike), and a repost path that starts with mod pre-approval.
… globe The 42px command bar wrapped at ~1600px: fixed cells shrank, the AGENT text broke onto a second line and overlapped the clock. Fixed cells are now shrink-0 + nowrap and the alert ticker is the only shrinkable cell, so the bar holds one line and pans (hidden scrollbar) as the true floor. Low-value text sheds responsively instead of overlapping: below 1920px the brief-ready suffix, the keyless-OSINT note and the rr/ms readouts hide and the search box narrows; below 1440px the app-group captions, the version tag and the incidents word go too. Measured live: zero horizontal overflow at 1280, 1600 and 1920, bar height 41px at all three. The hero GIF's globe rendered as a black sphere: Carto dark tiles average 17/255 luminance, and vp8 recording plus 128-color GIF quantization crushed everything below ~20 to black. The re-record lifts imagery gamma during capture only (product stays 1.0) and picks a cruising airliner for the dossier shot. New r/osinttools draft applies the same positioning as the DataHoarder piece, with a timing warning tied to the account's removal history.
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
1 participant
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.
Three pieces toward the relaunch, after the r/DataHoarder post was removed before anyone saw it (post-mortem included in the post doc).
README conversion
Open-mode LINK chip fix
Keyless clients skipped /ws/alerts entirely, so every fresh
docker compose upshowed a permanent red LINK-down chip — in the product and in any screen recording of it. Keyless clients now probe once: adopt the socket if the backend accepts (open mode), stay closed with no retry loop if it rejects before open. Three unit tests cover both paths and the reconnect-after-drop case.r/DataHoarder post-mortem
The post doc records what happened (removed/filtered: absent from sub search and the account's public profile, zero traffic impact) and the repost path, which starts with mod pre-approval instead of another blind submit.
Verified:
scripts/verify.shgreen — web 393/393, api 1721 passed + 1 skipped, lint and typecheck clean. The hero capture itself demonstrates the WS fix: take 1 shows LINK down, take 2 shows LINK live.