2025-03-24infra
Data freeze and wind-down
- Change: Every main page switched from live upstream calls to static JSON under
public/data/in a single day: global data (0b94f10b), world feed (f68921f6),/users(5967959a),/scenes(cea52f5c),/parcel(1aa49fc6),/maps(7bc89f73),/worlds(9bccb79f),/status(15a687db). Front-page world data frozen (dcc23bd8). Search buttons removed (4bcb41bc)./users/:idand/scenes/:idrerouted to their parent list pages (f3c27d09). GitHub Actions workflows disabled (769e7310). Note: GA scripts were already off since 2024-11-01 (3fc4a429). - Why: The upstream DCL API stopped refreshing reliably. Keeping live-fetch paths meant showing stale-and-erroring data to every visitor. A frozen snapshot of the last good cache was a better user experience than broken charts.
- Affected Modules: All page
getStaticPropshandlers,src/lib/data/fetch.ts,public/data/,.github/workflows/, sidebar search - Trade-offs:
- Pro: The site loads fast and never shows errors; the data is consistent and predictable.
- Con: Data frozen at the last cache date (2025-03-24); the project is now a read-only artifact rather than a live dashboard. Any future reactivation would require re-plumbing every page's data source.