2 Commits

Include renames

Author	SHA1	Message	Date
thatguygriffandClaude Opus 5	6325f0ff32	Add Reddit with its comment threads, and show quoted posts whole ... Two changes. They share the `Segment` model, which is why they arrive together. ## Reddit A new adapter under /reddit, plus the thread beneath the post -- on Reddit the conversation is usually the reason the link was shared, so a viewer that showed only the post would be showing the wrong half. The `.json` twin of a post URL is the post and the whole first page of comments in one response, far better than anything the page gives up, so it is the only layer that normally runs. Reddit refuses it to a browser it has never seen and answers with a JavaScript challenge, which any ordinary navigation solves by itself; the adapter navigates once and retries, and the cookie left behind serves every later post. Below that, `shreddit-comment` elements are read from the rendered page -- flat, each carrying its own `depth`, so `treeFromDepths` rebuilds the nesting. `Post.comments` is a tree rather than a flat list with depths, because folding a comment has to take everything under it along and nesting is what makes that free. Each comment renders as a `<details open>`, so collapsing works with the stylesheet off and from the keyboard, and a collapsed one says how many replies it is hiding. "Collapse all" is the only part that needs the script, so it ships hidden and appears once the script has run. What sits behind a "load more" is not fetched -- that is a second page and often a third -- but it is counted and said out loud rather than quietly dropped. Four things the payloads got wrong on the first try, each now with a fixture: `fallback_url` is the video track alone whenever `has_audio` is true, so a post with sound has to use `hls_url` and only a silent one gets the proxied MP4; `scrubber_media_url` looks like a poster and is a second MP4 for the timeline thumbnails, while the still is in `preview.images`; a gallery's pictures live in `media_metadata` keyed and unordered, with their order only in `gallery_data`; and `replies` is the string "" rather than an object when there are none. Comment bodies are Markdown, rendered by a new render/markdown.ts that escapes first and then puts back only the constructs we chose to support -- never Reddit's own `body_html`, which would mean trusting markup a stranger caused to be generated. An app share link (/r/<sub>/s/<code>) is a plain 301, so one request told not to follow it is enough. The permalink it resolves to is what the copy button hands back, since an opaque share code is a tracking parameter by another name. ## Quoted posts Both X and Bluesky lifted the quoted post's media out and showed it as the quoter's own, dropping the quoted words and the quoted author entirely. A quote of a photo post therefore rendered as somebody else's picture under the wrong name with nothing to say so, and a quote that had a picture of its own dropped the quoted one instead -- the two could never both appear. Half the quote posts people share are someone answering a stranger and the other half are someone continuing a thought from an earlier post; neither reads with only one side of it on the page. `Segment.quoted` now carries the whole thing -- author, words, pictures, time and a link to it -- and renders as a post inside the post. Neither payload carries a usable address for it: X has no permalink and it is rebuilt from the handle and `id_str`, Bluesky has an `at://` URI nobody can open and it is rebuilt from the handle and the record key. On Bluesky the record sits at `embed.record` for a plain quote and at `embed.record.record` when the quoting post has media of its own, and a quote can also point at a feed, a list or a post since deleted, which arrive in the same slot under a different `$type` -- only `app.bsky.embed.record#viewRecord` is taken. Two things about X's text, both visible on any post and not only a quote. It arrives pre-escaped, so an ampersand someone typed was reaching the page as the literal `&amp;`; it is decoded in the adapter, where the encoding comes from, leaving the escape-on-the-way-out rule alone. And every link is a `t.co`, which tells the reader nothing and routes them through X's click tracker to find out -- `entities.urls` carries the real address alongside, so it is put back. The shortlink X staples onto the end of a quote post is dropped rather than expanded, since the post it points at is already on the page; `display_text_range` is where that boundary is and it keeps a link the author put there deliberately. Its indices are UTF-16 units into the escaped text, so the slice happens before decoding and before expanding, and splitting to codepoints first overshoots past an emoji -- checked against a post carrying one. A quote is context, and context that fills the screen has stopped being context, so a segment carrying one gives up the window-filling cap on its own media. ## Along the way setupMedia only ever wired `document.querySelector('.media')`, the first rail on the page. That was already wrong for a Bluesky or Threads chain with media in more than one post, and a quoted carousel would have hit it too. It now runs per rail. ## Verified 108 tests, typecheck and build clean. Resolved end to end against the live platforms: Reddit self, gallery, video, link and share-link posts; X quotes with no media, with media on the quoted side, and with media on both; Bluesky quotes in both embed shapes, including a ten-post chain where every post quotes a different account and all nine quotes come back under the right name. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_017nMQ2eDKnqALYhAibpTKTu	2026-08-27 11:45:40 -03:00
thatguygriffandClaude Opus 5	b5f9483615	Initial commit: read social posts back without the app ... antisocial is the other half of a StopTheMadness redirect rule. Links to X, Threads, Instagram, TikTok and Bluesky get rewritten to /<prefix>/<original path>, and this resolves the post and shows the media and the words, with a badge saying where it came from and a button to copy the original URL. Every request drives a real headless Chromium, logged out, from a residential IP. One code path, and it survives markup changes better than parsing from the outside would. Extraction is layered, most structured first: the platform's own API response caught in flight, then an inline payload, then the rendered DOM, then Open Graph tags. Media is never linked straight at a CDN. Instagram and TikTok reject requests without a matching Referer and cookies, and proxying keeps the viewer's browser from talking to the platform at all. Range is forwarded so the native video scrubber can seek. HLS is the exception, since proxying it would mean rewriting playlists. TikTok sometimes answers with a slider puzzle. Rather than reporting that as a failure, the page is parked and the viewer is handed the puzzle: screenshots stream out, pointer events are replayed back. Solving it leaves the cookie in the shared browser context, so the retry is an ordinary request. A failed resolve is never a blank error page. The card carries the platform, the original URL and the copy button, so a broken adapter still leaves the link one tap away. Verified end to end against real shared links on all five platforms, in the container, including multi-image carousels, reels, TikTok short links and photo posts. 49 tests run the adapters against captured payloads with no network. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01BGkRmLfiWuJHx6tQ12EELY	2026-08-26 11:32:25 -03:00