Skip to content

Yumak Bot 0.6.1

Choose a tag to compare

@github-actions github-actions released this 19 Nov 22:40
· 175 commits to main since this release

Added

  • The bots' browsers can leave through Cloudflare WARP instead of the server's own address, which some sites behind
    bot guards refuse for being a data centre's before their page even loads. An optional warp service in
    docker/compose.yml (YUMAKBOT_WARP=1 with the installer) and YUMAKBOT_EGRESS_PROXY turn it on; the person's own
    computer still comes first when it is connected. Addresses are checked on the server as before, the operator's
    local hosts go straight, and while the proxy cannot be reached the browsers leave from the server again.
  • The iPhone app gets notifications while it is closed. It hands its device token to the server with the phone's
    notification level, muted bots and language, asks for permission once after sign-in, and opens the conversation of
    a tapped notification. Settings → General has a Notifications card with the level, the phone's permission, a test
    notification and a hint when the server has no Apple key. While the app is open, only the conversation on screen
    stays quiet.
  • Settings → Import and backup reads Grok Bot marketplace links (x.ai/bot/marketplace/bots/…) as well as share
    links, and takes the bot from the page's add button.

Fixed

  • The bots' desktop browser no longer shows bot guards such as Akamai two marks of a program: started with the
    DevTools pipe, Chromium reported navigator.webdriver as true and sent an experimental TLS extension Chrome does
    not, and these sites cut the page's requests after the first one.
  • The bots' desktop browser speaks the bot's language: menus in Turkish for a Turkish bot, and pages asked for in its
    language instead of always in English. The "unsupported command-line flag" bar no longer covers every page.
  • The bots' desktop browser draws WebGL again, in software, as the desktop has no graphics card. Pages got no WebGL
    at all, and a browser without it is one bot guards such as Cloudflare's check rarely let through.
  • The bots' desktop browser is Google Chrome instead of Debian's Chromium. Sites behind bot guards see the browser's
    brand and trust the one most people use. Chrome opens the bots' existing profiles; a profile Chrome has opened may
    not open in the older Chromium again.
  • Bot guards such as Cloudflare's check let the bots' desktop browser through while a bot drives it. The server drove
    it with a Playwright that turns on a DevTools domain pages can detect, and ran its page reads in the page's own world,
    where the page can watch them; the desktop's browser is now driven by patchright-core, the same Playwright without
    that domain and with its scripts in an isolated world. Without that domain the desktop pages' console messages no
    longer reach the bot. The passkey wall, which left a binding on every page, is no longer put into the
    desktop's browser; a passkey window shows on the desktop's screen instead.
  • A connection whose refresh token the service refuses for good asks for a new sign-in. X refuses a spent token with
    invalid_request rather than invalid_grant, so the connection stayed connected while every call failed, and
    signing in again failed on the kept token. Any OAuth error other than a server error, a pause or a rate limit now
    signs the connection out, and a sign-in the person starts drops a refused token.
  • Bold text followed by a suffix after a quoted word, such as **"Yenile"**ye, shows in bold in the desktop and
    mobile apps instead of keeping its asterisks.