dvach-26.8

• The captcha pass field now accepts more than a passcode

karachan-26.8

• Posting works on the boards that check the captcha: the site asks for reCAPTCHA 3 and the extension was answering with a version 2 token, which /b/ refused every time
• A board that checks no captcha no longer solves one for a field the server never reads
• A ban is explained instead of being reported as the single word "Banned": its reason, when it was passed and when it lapses, and the number the appeal form addresses it by, all kept in the app's ban log
• Needs app 26.8.1 or newer, which is where reCAPTCHA 3 support lives

fourchan-26.8

• Posting, deleting, reporting and the 4chan Pass work again — the extension had been browse-only since the captcha stopped working
• The captcha is solved in the app again, past the check that had replaced it: 4chan's own captcha page is let through in the WebView and the cookies it leaves behind are carried back
• Posts, deletions and reports go to the board they belong to instead of the site root, which had stopped answering them
• A captcha 4chan hands out that the app cannot show — the hCaptcha gate and the pick-the-pictures variant — is named instead of failing as a broken response
• A captcha that cannot be read says what actually arrived instead of "Unknown error", and a ticket cooldown is counted down instead of reported as nothing

e444-26.8

• Private [secret] text addressed to you is revealed in the post itself, drawn in the theme's capcode colour
• The posting form has a private-text button that wraps the selection in [secret]
• The slide captcha is solved by dragging the piece into the gap, in the app's own dialog, instead of the guessing game it stood in with
• Your identity now survives posting, deleting and reporting: the board hands out fresh auth cookies with every one of those and they were being dropped, so managing your own posts works
• Needs app 26.8.1 or newer — the private text and the slider dialog are provided by the app, and an older build does not have them

arhivach-26.8

• Archived posts written by a bot are marked as AI-generated, the same way the 2ch extension marks them

local-26.7.2

• Threads filed into subfolders of the archive are now listed, newest first among the rest
• Their images, thumbnails and deletion work wherever in the archive the thread sits
• Opening a saved thread from a file manager no longer requires it to sit at the top
• A thread saved twice under one name is listed once, the newer copy

kohlchan-26.7.1

• Line breaks inside posts are no longer collapsed into a single paragraph

karachan-26.7.1

• A post the site refused is no longer reported as sent: the reason it gives is shown instead, and a refused captcha is retried with a fresh one
• Deleting and reporting posts work — the request never named which of the two it was, and the site turned it down unread
• A reply now carries its own number back, so the client can find the post that was just made

karachan-26.7

• New extension for karachan.org
• Written in Kotlin for the site's Mitsuba engine, which publishes no API: boards, catalog, threads and posts are all read from the pages themselves
• Boards keep their own categories, and the ones named $ and * are reachable like any other
• Posting, deleting and reporting work, including the invisible captcha the site asks for
• Quote links open the post they point at, in this thread or another one
• Embedded videos are shown as attachments instead of bare links

e444-26.7.1

• Post polls are back: every answer shows its share of the vote, and tapping one votes
• Post reactions are back, with a picker in the post's long-press menu
• The per-post navigator menu is back: its sections and buttons are drawn under the post, wrapped to the width there is for them
• All three read at the size posts are read at and follow the app's corner radius, and a button answers a tap with the app's own ripple
• A menu button leading to a thread or a board opens it in the app; only an address the app cannot claim goes to a browser
• All three are drawn through the app's post decorator API instead of by reflecting into the app, so they need an app build that provides it -- on an older one the extension works exactly as the previous release did