Most digital memory today is stored as timelines - feeds, profiles, chronological posts. We’re experimenting with a spatial model instead.
Honoramma lets people create isometric “memory parks”: grid-based maps where monuments can be placed in space. Parks can be private (family-only) or public. Monument slots are activated with a one-time purchase rather than a subscription, because we didn’t want memory to depend on recurring payments.
Under the hood:
- Next.js frontend
- Supabase (Postgres + pgvector)
- Custom isometric renderer (Pixi.js)
- Structured export format for long-term preservation
- Internal ledger system for slot activation
The core question we’re exploring:
Are spatial systems more durable for long-term digital memory than feed-based ones?
I’d really appreciate feedback on the architectural approach and long-term durability of platforms like this.
Happy to answer technical or conceptual questions.
Show HN: A Spatial Alternative to Timeline-Based Digital Memory · HackerTrans
I’m Pavel, founder of Honoramma.
Most digital memory today is stored as timelines - feeds, profiles, chronological posts. We’re experimenting with a spatial model instead.
Honoramma lets people create isometric “memory parks”: grid-based maps where monuments can be placed in space. Parks can be private (family-only) or public. Monument slots are activated with a one-time purchase rather than a subscription, because we didn’t want memory to depend on recurring payments.
Under the hood:
- Next.js frontend - Supabase (Postgres + pgvector) - Custom isometric renderer (Pixi.js) - Structured export format for long-term preservation - Internal ledger system for slot activation
The core question we’re exploring:
Are spatial systems more durable for long-term digital memory than feed-based ones?
I’d really appreciate feedback on the architectural approach and long-term durability of platforms like this.
Happy to answer technical or conceptual questions.