309 earlier updates, newest first. Showing 261–280 on page 14 of 16.
Released
H5Backend
Website search discoverability: category terms and structured data
Website titles and descriptions now carry the category terms (Texas Hold'em, 德州扑克, 德扑 — the English homepage title previously said only Poker), and the site gains schema.org structured data for the first time: organization and website info, an application entry with App Store and Google Play install links plus factual fields like 2–9 seats and 7 AI styles, and blog post markup. Every description keeps the practice-chips, no-real-money boundary; gameplay, accounts, membership, and payments are unchanged.
The English homepage title now says Texas Hold'em (previously just Poker); product, pricing, blog, and about titles gain category terms
Chinese pages use 德扑 for the first time, covering 德州扑克 / 德扑 naturally across titles and descriptions
First site-wide schema.org structured data: organization and website info, an application entry (App Store / Google Play install links, 2–9 seats, 7 AI styles), and blog post markup
Released
H5Backend
Homepage: fairness-first hero messaging
This release updates the homepage hero to lead with fairness: matching the product page, it states that standard tables default to server-visible commit-reveal dealing — the deck is committed before the deal and verification material is released afterward — and tunes headline sizing and line height for the new bilingual copy. Poker rules, chip settlement, accounts, memberships, and payment behavior are unchanged.
The hero headline now leads with fairness-first positioning.
Body copy mirrors the product page: default commit-reveal dealing, committed before the deal and verifiable after the hand.
Headline font sizing and line height are tuned for the new bilingual copy.
Released
H5Backend
Table 2 live squid progress is now always visible
This release keeps squid-round status visible during live hands on Table 2 with explicit total holders, remaining count, and holder badges. The player marker now uses an 🦑 icon instead of text, and each in-hand round shows “Round N · Total X · Held Y · Left Z” so everyone can quickly verify progress. This does not change poker rules, chip settlement, fairness, accounts, or payment behavior.
Live Table 2 rounds now keep squid progress visible with round totals and holder counts.
Seat badges now use an 🦑 icon for immediate identification of holders.
Squid progress is no longer hidden during hands; status now stays in sync with current seat holders.
Released
Android
Android 1.1.4: a clearer Me screen and Tools entry
Android 1.1.4 build 338 is now live on the Google Play production track. This update removes the duplicate poker-tools shortcut from Me and keeps Tools in the bottom navigation, while retaining Stats, History, Fairness verification, and Drills with UI stability improvements. Poker rules, practice chips, accounts, memberships, and payment behavior are unchanged.
Me no longer duplicates the poker-tools shortcut; the bottom Tools tab is the single entry point.
Stats, History, Fairness verification, and Drills remain available.
Improves Android UI stability without changing gameplay or payments.
Released
H5Backend
Stricter release regression bindings
This update repairs stale bindings in release verification. The production regression for leaving a table now follows the current friend-room and public-table semantics, both expiry gates continue to share one terminal-state predicate, and QA source receipts are rebound to their reviewed current versions. This reduces the risk of stale metadata blocking a release or obscuring a real failure. Poker rules, chip settlement, table UI, accounts, and payment behavior are unchanged.
The production table-exit regression now matches current friend-room seat retention and public-table seat release semantics.
Expiry release checks continue to share one terminal interaction predicate, preventing gate drift.
QA source receipts now bind the reviewed current versions and reliably exercise failure paths inside the restricted sandbox.
Released
H5Backend
More reliable synchronized releases and source traceability
This update strengthens the synchronized release guardrails for the website, H5, and backend. Production deployment now validates host cutover prerequisites before consuming a release attempt, manual hotfixes are deduplicated from automatic CI delivery by exact commit, and release tooling follows only the matching CI and production runs. The public corresponding-source notice for the solver also verifies the published tag and its exact metadata. Poker rules, chip settlement, table UI, accounts, and payment behavior are unchanged.
Production validates host cutover prerequisites before consuming a daily release attempt.
Manual hotfixes and automatic CI delivery are deduplicated by exact commit to prevent duplicate releases.
Release tooling waits only for CI and production runs that belong to the target commit.
The public solver corresponding-source notice verifies the published tag and exact metadata.
Released
H5
Safer table exits and consistent frosted navigation
Table 2 now clearly separates ordinary back navigation from an explicit leave. Between hands, returning home from friend rooms or bot practice preserves the seat and stack; only the menu's deliberate leave action gives up the seat. Mid-hand confirmation remains in place, and public matchmaking tables continue to release seats under their existing policy. When a session has ended, hardware back or an edge swipe exits the expired table instead of hiding the terminal notice and stranding the player on an unusable felt. The marketing site's navigation and glass panels also retain their frosted effect consistently in production builds across Chrome, Firefox, and Safari. Poker rules, pot settlement, accounts, and payment behavior are unchanged.
Returning home between hands preserves the seat and stack in friend rooms and bot practice, while explicit leave still releases the seat.
Mid-hand back navigation still requires confirmation, and public-table seat-release policy is unchanged.
Hardware back and edge swipes now exit an ended session instead of revealing an unusable expired table.
Frosted navigation and glass panels remain consistent in production CSS across Chrome, Firefox, and Safari.
Released
Backend
Clearer daily service signals and anomaly alerts
The daily operations report now distinguishes active usage across H5, embedded Flutter, Telegram, and browser surfaces, with coarse iOS, Android, and other-system totals. Zero-only metrics no longer crowd the report, while missing registrations, sessions that never start, and established users with no daily activity are called out explicitly. Retention now keeps both cohort size and retained-user count, so very low but non-zero results are not displayed as zero. This improves privacy-safe aggregate monitoring and incident detection only; poker rules, chips, accounts, and payment behavior are unchanged.
Breaks down real active users by client surface and coarse operating system, with cross-surface duplication stated explicitly.
Suppresses all-zero sections while highlighting missing registration, seating, gameplay-start, and real-activity signals.
Pairs retention cohorts with retained-user counts, distinguishing true zero from a non-zero result below 0.1%.
Keeps the report aggregate-only, without adding IP, country, or user-identity collection.
Released
H5Backend
Friend spectating, the new default table, steadier bot decisions, and release guardrails
Authenticated users with a friend-room code can now join as seatless spectators: they take no seat, hold no chips, cannot act on the game, never receive any player's unrevealed hole cards, and never receive the post-hand fairness seed reveal. Hosts can disable spectating, while two-sided blocks, public tables, and advanced encrypted-dealing tables all deny it. At the time of this release, the default H5 and mobile-WebView entry converged on Table 2 while a temporary rollback surface remained; that temporary surface was removed in the later Table2-only release. Top-bar actions, report and block controls, fairness access, winner presentation, voluntary card reveals, time bank, squid prompts, and nine-seat layout parity are included, with the top bar and nine-seat name readability also polished. Practice bots also handle locked shared-board outcomes, forced chops, and higher two-pair upgrades more reliably while preserving their distinct styles. The marketing site adds first-party anonymous page-view metrics (no third-party analytics, no tracking cookies, no IP stored), disclosed in Privacy Policy v2.8 and Cookie Policy v1.5. On delivery, the website, H5, and backend now share one traceable guardrail for each synchronized Production release: at most three release attempts per Singapore calendar day, with duplicate or indeterminate cutovers never retried automatically; pre-release checks are focused on inputs that actually affect live delivery, avoiding duplicate builds; and the five-minute database watchdog and alerting move to a VPS-native timer, with GitHub retaining a daily independent liveness sample. This release also removes orphaned code and obsolete build inputs that no longer participate in the product; poker rules, chip settlement, and account data are unchanged.
Friend rooms now support read-only spectating: unrevealed hole cards and the post-hand fairness seed stay hidden from spectators, and the rail roster remains visible to the table.
Hosts can disable spectating; two-sided blocks, public tables, and advanced encrypted-dealing tables cannot be railed.
At this release, the default table route used Table 2 while a temporary rollback surface remained; that surface was removed in the later Table2-only release.
Table 2 closes parity gaps in table actions, report and block controls, fairness, winners and voluntary reveals, time bank, squid prompts, and nine-seat layout, with the top bar and seat-name readability also polished.
Bots make more reliable decisions on locked shared-board outcomes, forced chops, and higher two-pair upgrades.
The marketing site adds first-party anonymous page-view metrics, disclosed in Privacy Policy v2.8 and Cookie Policy v1.5.
The site also publishes the bilingual engineering article “Prose doesn't execute,” tracing how written rules become executable guardrails.
The website, H5, and backend are counted as one synchronized release rather than separate releases.
Duplicate triggers, cancellations, and indeterminate cutovers are handled conservatively to prevent accidental repeat releases.
Release checks avoid duplicate builds, while a proven VPS-native five-minute database watchdog keeps a daily independent GitHub liveness sample.
Removes orphaned source and stale build cache inputs that are no longer compiled or loaded; poker rules, chip settlement, and account data are unchanged.
Released
Android
Android 1.1.3: memberships and the latest table features
Android 1.1.3 is now live on Google Play with Pro/Max memberships, the latest table features, reliability improvements, and expanded availability across markets that permit simulated-poker apps. Google policy restricts Algeria, Iran, Libya, Qatar, Syria, and Yemen; South Korea remains unavailable pending GRAC classification.
Adds native Google Play Pro and Max monthly and yearly memberships.
Brings practice-vs-bots, friend-room, and table-rule capabilities up to date.
Improves mobile reliability and platform compatibility.
Released
H5Backend
Safer TestFlight Sandbox acceptance, test-payment retries, and registration metrics
Native Apple purchase verification can now process TestFlight Sandbox transactions on the production backend only for exact allowlisted accounts that are also marked as internal tests. Every payment, subscription, and entitlement fact keeps its Sandbox tag and stays out of revenue and paid metrics. An authorized refunded-balance run on Telegram Test Server may now replace only an expired invoice with no payment fact, while the whole authorization remains capped at one successful test payment. First-time Google, Apple, and Telegram account creation now also enters the trusted server-side registration funnel, while routine sign-ins, auto-linking, and lost concurrency races do not double-count. Ordinary accounts, Production-store transactions, and real revenue reporting are unchanged.
TestFlight Sandbox purchases are limited to exact authorized internal QA accounts and isolated from Production revenue and paid metrics.
Telegram Test Server may safely retry only expired invoices with no payment fact and remains capped at one successful test payment.
First-time Google, Apple, and Telegram account creation now enters the trusted server-side registration funnel.
Re-logins, account auto-linking, and concurrency races do not create duplicate registration counts.
Released
H5Backend
A cleaner homepage, sharper bot practice, and an Android catalog update
The homepage no longer repeats the operating-company card, keeping the page focused on poker practice, review, and strategy training; BLUFF KING PTE. LTD.'s legal name, UEN, Singapore registration, and DPO contact remain fully available in the footer, About, Contact, and legal pages. Bot practice also gets better preflop re-raise ranges: TAG, LAG, and Maniac now have more distinct 3-bet/4-bet styles, while a zero-stack bot is replenished in the same seat at the table's starting stack so the practice roster stays intact. The in-app mobile version catalog now also recognizes public Android 1.1.3 build 312 on Google Play, giving older clients accurate update prompts and the official store destination. Practice chips, the no-real-money boundary, game rules, accounts, membership, payments, and user data are unchanged.
Removed the repeated operating-company card so the homepage stays focused on product value.
The legal name, UEN, and jurisdiction remain in the footer, company page, contact page, and legal documents.
The public DPO contact in Privacy remains unchanged.
TAG, LAG, and Maniac preflop re-raise ranges are now calibrated over real starting-hand combinations for clearer differentiation.
A busted bot is replenished in the same practice seat so the configured roster does not gradually shrink.
The mobile version catalog now recognizes Android 1.1.3 build 312 while keeping iOS and Android metadata and store links independent.
The practice-chip and no-real-money boundary remains clear on the homepage and footer.
Released
H5Backend
Live straddle and finite squid are now available in practice-vs-bots
Until now these two table rules could only be enabled in friend rooms. For table-rule purposes a bot occupying a seat is a player too: straddle is a purely seat-position forced bet, so a bot in that seat posts it exactly like it already posts a small or big blind, and the finite-squid roster no longer recognises humans only — a bot seat becomes a participant as soon as it is dealt in (it is never sent a join prompt, since consent means nothing for a bot). The same change lets a friend room that fills empty seats with bots enable squid. Squid penalties remain a separate table-side ledger that never rewrites poker pots or hand history; practice chips only.
The practice-vs-bots setup now offers the straddle and finite-squid toggles (3+ seats required).
A bot seat joins the current squid round automatically as soon as it is dealt in — it is never sent a join prompt.
A friend room that fills empty seats with bots can now enable squid as well.
Squid penalties never rewrite poker pots or hand history; practice chips only.
Released
H5Backend
Advanced encrypted dealing (highest-encryption mode) now available on all-human, no-AI tables
All-human, no-AI rooms can now have the host enable Advanced encrypted dealing: on a hand where the mode is on, the server does not hold your unshown hole-card plaintext. Required disclosure: this secrecy holds only for that hand; if any player drops, the whole table visibly downgrades to standard (server-visible) dealing; practice chips only. Default tables stay server-visible verifiable dealing, unchanged; settlement logic is unchanged.
Advanced encrypted dealing is now available — the host enables it in all-human, no-AI rooms.
On that hand, the server does not hold your unshown hole-card plaintext.
If any player drops, the whole table visibly downgrades to standard (server-visible) dealing.
Practice chips only; default tables and settlement logic are unchanged.
Released
H5Backend
Engineering post reworked: what a subscription AI really costs on the meter, itemized per model
The Build Notes post on subscription-AI billing was rewritten to lead with its real point: for one flat monthly subscription, what the same usage would cost at the metered API list price — one 30-day window paid $400 and lists at $53,403 (~133×). It adds a per-model usage table (each model's input, cache read/write, and output tokens with list-price subtotals) and explains why a fully-autonomous AI team runs on the flat fee, not the metered API. Content-only release — game rules, room links, accounts, and user data are unchanged.
The post now centers on the real metered cost behind the subscription: $400 paid vs $53,403 at list price (~133×).
Adds a per-model breakdown: each model's input, cache read/write, and output token counts with list-price subtotals and totals.
Adds a worked derivation (tokens × unit price = amount) so every dollar figure is traceable, not conjured.
States the takeaway: a fully-autonomous AI team on the metered API can cost more than a human — the flat subscription is what makes it viable.
Content-only release — no change to gameplay, backend, or user data.
Released
H5Backend
New engineering post: itemize the AI subscription that has no bill
A new bilingual engineering post is live in the site's Build Notes: how to reconstruct a per-model, per-token bill for a subscription AI from the local Claude Code / Codex CLI logs, and the three streaming/aggregation traps that decide whether the total is right. This is a content-only release — it updates the marketing site article and this public changelog; game rules, room links, accounts, and user data are unchanged.
New post “Itemize the AI subscription that has no bill” is live in both languages.
Shows where subscription-AI usage lives in the local CLI logs, and which fields to read.
Breaks down three aggregation traps: streaming dedupe, forked-session double-count, cached-input-is-a-subset.
Content-only release — no change to gameplay, backend, or user data.
Released
H5Backend
Land back in the table you opened after sign-up; safer, more reliable block & report
After you open a table as a guest and then register, we now take you straight back into that table instead of the lobby. Block and report are also more reliable: a report always targets the player you selected (even if seats shuffle while you hold), the report description limit is measured in real bytes (so longer non-English text is no longer misjudged), the report control is keyboard- and screen-reader-accessible, and a blocked player stays hidden on both table layouts even after they change seats or rename. Game rules, room links, and user data are unchanged.
Tap a table as a guest, then after sign-up you land in that table instead of the lobby.
A report always targets the selected player, even if seats change during the press.
The report description limit now counts UTF-8 bytes, so longer non-English text is no longer wrongly rejected or accepted.
The report control is keyboard/screen-reader accessible; blocked players stay hidden across both table layouts even after they reseat or rename.
Released
H5Backend
Telegram release checks aligned with the latest authentication policy
Release verification in the real Telegram App container now uses an isolated test-domain account and a test credential that meets the current strength policy, preventing stale fixtures from being mistaken for product failures. User login rules, game rules, room links, and user data are unchanged.
The Telegram device-verification account now stays inside the test domain and metrics exclusions.
The QA credential follows the current password-strength policy without weakening server-side gates.
QA credentials no longer enter launch URLs or run logs.
Released
H5Backend
More reliable release verification and device screenshots
The release flow now confirms its isolated QA environment before device screenshots and multiplayer verification, so an environment reset cannot be mistaken for a product failure. Game rules, user accounts, room links, and user data are unchanged.
After an environment reset, fixed QA fixtures are restored only when needed and re-verified before device checks begin.
Authentication, network, or unexpected-state errors still fail closed and never bypass the release gate.
The closed-table screenshot oracle now matches the centered new-table layout used in the real product.
Released
H5Backend
Clearer blog navigation and new-table maintenance
The website's article section is accurately labeled “Blog” again, with a new bilingual engineering article about brand-language migrations. The H5 new table also completes a behavior-preserving internal naming cleanup; game rules, room links, and user data are unchanged.
Navigation, page titles, and return links consistently use “Blog,” leaving a clear boundary for a future standalone Insights feature.
Published “Borrow the layout, not the vocabulary,” a reusable guide to naming migrations and information architecture.
Added automated brand-language checks to keep retired codenames out of future releases.