GoFurry Updates

GoFurry v3.0.0-alpha.6 is officially released. This is one of the major updates in the GoFurry V3 stage. This release further improves data insight capabilities and completes a significant upgrade of the administration system. The new Insights system begins connecting website, game, and community resource data, providing the foundation for future exploration, trend analysis, and resource comparison. This update introduces: Game and site entity insights Data dimension analysis Change exploration Player intelligence Regional pricing information Language support analysis Platform support analysis Certificate and security insights Entity comparison These capabilities allow GoFurry to move beyond simply listing resources and begin helping users understand the structure, context, and evolution behind them. On the administration side, the management system has completed the React Admin migration and adds multi-account permissions, content workspaces, and data operation capabilities, preparing the foundation for more advanced content management. The previous Workshop direction has also been redesigned into Public Insights, providing a clearer product direction for future public data exploration features. This release continues building on the V3 data contracts and historical fact system, allowing future insights to combine current information with historical context. v3.0.0-alpha.6 marks GoFurry’s transition from internal data foundation building toward user-facing data insights. Future releases will continue improving public analytics, change intelligence, and resource exploration experiences.

09/03/2026, 01:26

GoFurry v3.0.0-alpha.5 is officially released. This update introduces the foundation of Change Intelligence, allowing GoFurry to not only display the current state of resources, but also begin tracking how they change over time. Previously, users could view the current information of a website or game. With this update, GoFurry begins exploring new questions: “When did this resource change?” “What was its previous state?” “What information has been updated?” This release adds the foundation for detecting changes across Game and Nav resources, including game status, platform support, release state, price changes, as well as website IPv6, TLS, security configuration, and primary target changes. The system now records change events, versioned detection rules, and historical change information, creating a more reliable foundation for future update tracking, trend analysis, and resource intelligence features. A read-only Change Center has also been added to the admin area, allowing inspection of change rules, detection status, and historical events. While these capabilities are currently focused on internal data construction, they will support future public features around resource history and intelligence. v3.0.0-alpha.5 is still an early V3 release. Instead of simply adding more pages, this update moves GoFurry further from a resource directory toward a resource intelligence platform.

08/30/2026, 01:25

GoFurry v3.0.0-alpha.4 is officially released. This is the fourth alpha release of the GoFurry V3 stage. This update completes the V3-P0.3 Analytics Metric Foundation. Built on top of the Historical Fact Foundation introduced in alpha.3, it establishes an explainable, backfillable, rebuildable, and verifiable foundation for analytics metrics. For metric storage, this release adds versioned Game and Nav metric registries, along with explainable per-entity daily metric states. Each metric state now carries reason codes, evidence timestamps, dimensions, and source projection versions. This means future metric results can explain not only what the result is, but also why it was produced, which fact day it came from, and which projection version generated it. For core metrics, this release introduces the first set of basic indicators. Game metrics now include free game share, Windows support, and Linux support. Nav metrics now include IPv6 adoption, TLS 1.3 adoption, and security.txt adoption. All metrics use a fixed seven-state vocabulary: positive, negative, stale, not_probed, probe_failed, unknown, and not_applicable, reducing inconsistency across different metric types. For metric processing, this release adds in-process Game and Nav Metric Engines. Collector reconciliation now follows the Acquisition → Facts → Metrics order, and Metric Days are gated on finalized Historical Fact watermarks. Each metric version is serialized through a PostgreSQL checkpoint row lock, reducing duplicate computation and concurrency conflicts. For command workflows, this release adds metrics status, metrics backfill, and metrics rebuild, with dry-run support. Runtime, backfill, and rebuild paths share the same evaluator / projector implementation, preventing inconsistent results across different execution paths. Retired metric versions can also remain explicitly rebuildable, making historical results easier to trace. For dimensions, Game metrics now support global, primary-tag, and tag slices. Nav metrics now support global, country, group, NSFW, and welfare slices. Multi-membership tag and group slices are deduplicated per entity to avoid double counting. Empty populations also materialize an all-zero global row, keeping query results structurally stable. For admin workflows, this update adds an authenticated read-only Metric Center. The admin panel now includes Overview, Registry, Checkpoints, Daily Results, and Entity Explorer views. Adoption and coverage ratios are calculated at query time, and entity names are resolved from same-day Historical Facts instead of current catalogs, keeping historical metric results aligned with their original context. For contract hardening, this release validates every active or retired Registry version against the compiled evaluator catalog. Startup will reject retained metric versions that have no compiled evaluator or whose contracts have drifted. Evidence rules are also clarified for free-game and price-related outcomes, and future evidence is rejected atomically without advancing the checkpoint. For database changes, this release includes new Game and Nav migrations. Fresh migrations, alpha.3 to alpha.4 upgrade migrations, PostgreSQL schema adoption, drift checks, sqlc checks, metric engine integration tests, evidence provenance tests, future-evidence rollback tests, checkpoint locking tests, retired rebuild tests, and catalog drift tests have been completed. v3.0.0-alpha.4 is still an early V3 preview release. It does not include P0.4 Change Intelligence or P1 Public Analytics. Its goal is to establish the internal metric computation, storage, backfill, rebuild, explanation, and admin inspection foundation first, preparing GoFurry for future public analytics, change intelligence, and more complete data product capabilities.

08/29/2026, 20:41

GoFurry v3.0.0-alpha.3 is officially released. This is the third alpha release of the GoFurry V3 stage. This update focuses on completing the V3-P0.2 Historical Fact Foundation, laying the groundwork for future analytics, trend tracking, change intelligence, and long-term content evolution records. For the game module, this release adds effective-dated Game / AppID tracking periods, allowing the system to record the historical relationship between games and Steam AppIDs more accurately. Game data now includes UTC hourly and daily player facts, historical game facts, daily price facts, and PostgreSQL-backed Fact checkpoints for managing fact processing progress. This release also introduces a four-state game price contract, making price status clearer across missing, free, paid, and unknown cases. The system now prevents duplicate Player Raw rows for the same run and game, preserves release history after current game deletion, and supports current-day Game Fact and Price Fact write-through so same-day data can reach the fact layer earlier. For the navigation module, this update adds effective-dated target tracking periods, historical Primary Target periods, and minimal admin management with audit records. Site-side facts now include protocol, target, and site daily facts, while scheduled acquisition quality, latest observation results, and last-known normalized state are separated more clearly. Unknown technical states are now preserved as nullable values instead of being forced into misleading conclusions. Empty or malformed historical TLS certificate timestamps are also treated as unknown during fact projection, improving the reliability of historical facts. For fact processing, this release adds in-process Game and Nav Fact Engines, along with facts status, facts backfill, and facts rebuild commands. Fact processing supports dry-run and shares runtime and backfill projection paths. The system only finalizes closed UTC days after the configured grace period and serializes pipelines through PostgreSQL checkpoint row locks to reduce duplicate processing and concurrency conflicts. For retention, Player Raw and Observation retention now support checkpoint-gated mechanisms, but remain disabled by default during the alpha stage to avoid premature data cleanup. Fact Rollup is also kept outside the acquisition Job / Run / Task ledger, reducing coupling between fact aggregation and collection execution records. On the frontend, game homepage cards now show canonical release dates and planned release dates, making released and upcoming information easier to understand. The game review button icon has also been stabilized during card hover transitions. For database changes, this release includes new Game and Nav migrations, with fresh migration checks, alpha.2 to alpha.3 upgrade migration checks, PostgreSQL schema adoption, drift checks, sqlc checks, generated-code checks, and related integration tests completed. v3.0.0-alpha.3 is still an early V3 preview release. It does not include P0.3 or P0.4, but it establishes the initial historical fact model, processing commands, backfill path, and retention boundaries for Game and Nav, providing a key foundation for future analytics, daily facts, change intelligence, and long-term trend capabilities.

08/29/2026, 00:51

GoFurry v3.0.0-alpha.2 is officially released. This is the second alpha release of the GoFurry V3 stage. It continues the game domain foundation introduced in v3.0.0-alpha.1 and focuses on V3-P0.1.1: the collector control plane and the Admin Collection Center. For collection architecture, this update introduces a PostgreSQL-backed durable collector control plane. Collection schedules, jobs, runs, task results, leases, recovery state, and collector heartbeats are now managed through the database. Compared with the previous more temporary and distributed collection triggers, the new structure records tasks, execution results, leases, recovery flow, and collector health more clearly, laying the foundation for an observable, traceable, and recoverable collection system. For execution, Game and Nav acquisition are moving into a unified durable execution path. This reduces differences between collection entry points and makes scheduled collection, manual collection, failure recovery, and run history easier to manage consistently. For admin workflows, this release adds the Admin Collection Center as a centralized place for collection operations. The admin panel now begins to support scheduling, queue and history views, manual collection, audit information, and ECharts-based visualizations, making it easier for maintainers to inspect collection state, troubleshoot issues, and trigger necessary re-collection. For data structure, active Game V2 physical storage objects have been renamed to canonical unversioned names. This makes the underlying storage naming better aligned with the long-term V3 domain model and reduces version-name debt for future evolution. For cleanup, this release removes go-timewheel, old Redis collection commands, and backend collection proxy endpoints, reducing interference from historical implementations. At the same time, existing P0.1 behavior is preserved to avoid unnecessary impact on the current public experience. This update also clarifies schedule editing and clock display in the admin panel, keeps collection task results retained, and adds a CI fallback for Go proxy failures, improving development and release stability. v3.0.0-alpha.2 is still an alpha release. It does not include V3-P0.2 and does not mean the final collection system is fully settled. Its main purpose is to complete the first round of collector control plane foundations, so future daily facts, change intelligence, analytics, and more advanced automated collection features can be built on a more reliable runtime model.

08/28/2026, 00:49