26.8.1

• Posting: the submission form is a sheet over the thread it replies to instead of replacing it. Drag it down to half height or swipe it away to read the posts you are answering, with the captcha and the send button pinned at the bottom at whatever height it settled at. The full-screen form is still there as User interface → "Classic style".
• Posting: the form reuses the captcha you just solved instead of solving a reCAPTCHA or hCaptcha again on every open. The reuse window is two minutes — that is how long such a token is actually valid.
• A small bar floating in the bottom corner carries a thread's Reply and Contents and a board's New thread and Refresh, plus a ⌘ for the App commands the forum and board are in scope of. Long press and drag reorders the buttons, a two-finger tap turns the bar between horizontal and vertical, and an item the page hides is no more in the bar than in the toolbar.
• Captcha: reCAPTCHA 3. Version 3 shows no challenge — it scores the client behind the page — so the token is minted in the background, inside the site's own page with its cookies and history, and reported as a solved captcha. Extensions pass the action the token is minted under per request.
• Every forum keeps a ban log: each post refused as banned is stored with its board, reason, expiration and the address the forum saw at the time, under "Ban log" in that forum's Additional section. Before a fresh captcha is requested the log is asked whether the current address is already banned on that board, so none is spent on a post that will only be refused again.
• Visible IP: flag a command "Run to change visible IP" for a forum and the address row names it, with a button that runs it — from the forum's settings, from the toast a banned post puts up, or from a script — dropping the pooled connections afterwards. No proxy service has any code in the app: ready-made commands for Asocks and DataImpulse ship in docs/commands, with credentials kept in the command environment.
• A forum's proxy can be limited to what you send: with "Proxy for sending only", posts and reports — together with their firewall resolution and their captcha — go through the proxy, while browsing, thumbnails and files load directly. A proxy takes a login and a password now.
• Commands reach app (the application's settings, by the key the settings screens store them under), chan (the forum the run belongs to and its cookies — the same store "Manage cookies" edits) and store (the command's own key→value store), each granted per command in its editor. The IP a forum sees and the proxy its traffic takes are granted apart, being the one thing here that reaches off the device.
• Commands can put a question to the user: show, confirm, prompt, choose and chooseMany raise a dialog mid-run and hand back what was chosen, or null for one that was cancelled. alert, confirm and prompt are bound to the same dialogs — until now a WebView cancelled every one, so confirm() answered "no" without ever asking.
• Commands gain an App target, for a script that operates on nothing and does its work through what it was granted; it runs from the Commands screen, and it is what the app runs when it needs another visible IP. Behind the proxy grant a script can read the IP and location a forum sees, read and write that forum's proxy as one connection string, and ask for the visible-IP command to be run.
• Toasts stack instead of covering one another, up to three, so a warning landing after a failure no longer takes its Details button away.
• 4chan hands out captchas again. A header's case is the protocol's choice rather than the server's — HTTP/2 requires lowercase — so lookups written in the familiar spelling (CF-RAY, Server, Content-Type) silently found nothing on exactly the hosts modern enough for HTTP/2, leaving a Cloudflare challenge unrecognised. Its "Verification Required" title is recognised too.
• A forum's Connection settings take a User-Agent of their own; left empty, the WebView default is kept.
• References to deleted posts are links now: a bare >>NNN the forum emitted as plain greentext is linkified and marked X, and tapping it opens the thread's last-seen copy instead of a single-post fetch that would 404.
• Threadshots no longer crash on a post carrying a country flag or an extension's decorator icon.
• Extensions: a drag-slider captcha — the user drags a puzzle piece across a background image — and a TAG_SECRET markup tag drawn in the theme's capcode colour, with a posting-form button that wraps the selection in it.
• Ripples take the corner radius of the surface under them, and the ⌘ menu gets its shadow, rows themed to read against their own card, and a width that hugs what is in it.