File
SMF·GATHER-TOWN
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·GATHER-TOWN

Can a prompt replace Gather?

Community platforms — online communities and team communication

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$7/moSource: gather.town · Checked on July 31, 2026
Per year
$84
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: network, moderation, and communication infrastructure
Exhibit Q Questions

Verdict

A 2D virtual space where avatars walk around a pixel-art map and video chat automatically connects when two avatars are near each other is a genuinely ambitious, more-than-a-weekend build — the proximity-based WebRTC connection management alone is real distributed-systems work. What doesn't survive: Gather's polished map editor, its reliability at scale with many simultaneous users, and years of interaction-design refinement.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a 2D virtual space with proximity-based video chat — be upfront that this is more ambitious than most entries in this catalogue, since managing WebRTC connections dynamically as avatars move is real distributed-systems work, not a simple CRUD app. Use a canvas-based 2D renderer, such as PixiJS, for a tile-based map where each connected user controls a moving avatar via arrow keys, with positions synced over WebSockets. When two avatars' positions come within a configured proximity distance, establish a WebRTC peer connection between those two users specifically, using a signaling server you run and a public STUN server for NAT traversal, so they see and hear each other; tear the connection down cleanly when they move apart. Use one fixed, pre-built pixel-art map to start rather than a visual map editor — that's a substantial separate feature. Handle the specific hard case carefully: a user moving between multiple nearby avatars in quick succession shouldn't leave stale or duplicate video connections. Do not build a map editor, screen sharing, interactive objects, or optimization for more than a handful of simultaneous users — those are out of scope and each represents real additional engineering; this is a working prototype for a small group, not production infrastructure at Gather's scale. Requires hosting, a domain, and a signaling/STUN setup for WebRTC — free STUN servers exist, but a TURN server for reliable NAT traversal at scale is a real cost this build's honest small-scale scope tries to avoid needing.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 a polished visual map editor
  • B.2 reliability at scale with many simultaneous users
  • B.3 years of proximity-video interaction-design refinement
  • B.4 screen sharing and interactive objects within the space

Prior art

Exhibit C — Why people still pay: network, moderation, and communication infrastructure

A basic proximity-video prototype is a real but bounded project; making it feel smooth and reliable with dozens of people moving around simultaneously, without connection glitches, is genuinely hard real-time systems work.

Questions

Is this actually a weekend project?

Realistically no — it's flagged here as more ambitious than most of this catalogue. Dynamically managing WebRTC connections as people move around is real distributed-systems work, closer to a multi-week project for someone comfortable with real-time systems.

Can I design my own map?

Not with a visual editor in this build — it uses one fixed pre-built map. A map editor is a substantial separate feature Gather has actually built.

How many people can use it at once?

This build is honestly scoped to a handful of simultaneous users — proximity video at Gather's actual scale, with many people moving around reliably, needs production-grade infrastructure this prompt doesn't attempt.

What does it cost to run?

Hosting, a domain, and WebRTC infrastructure — free STUN servers cover basic NAT traversal, but reliable connections for everyone may eventually need a paid TURN server, a real cost worth planning for.

Receipt

Already built this yourself?