: Games are played directly in the browser, typically using HTML5 or older Flash emulators.
| Concept | What It Means | How It’s Implemented | |---------|---------------|----------------------| | | Any object that implements to_quack() (returns a serializable dict) and from_quack(dict) (recreates the object). | A tiny abstract base class in Python; in JS it’s simply a contract you follow. | | Replicator | The engine that watches a source, serializes quacks, and pushes them to one or more sinks. | Built on top of asyncio (Python) or Node streams (JS). | | Sink | Destination for replicated data – a DB, a message queue, a file, or even a WebSocket. | Pluggable adapters; out‑of‑the‑box support for PostgreSQL, MongoDB, Kafka, S3, and HTTP endpoints. | | Quack‑Policy | Rules that decide when and how to replicate (e.g., debounce, batch size, conflict resolution). | Declarative JSON/YAML files, plus a tiny DSL for custom logic. | | Quack‑Versioning | Optional “semantic quack” tags that let you evolve the shape of to_quack() without breaking existing sinks. | Similar to schema evolution but fully optional – sinks can ignore unknown fields. | quackrep
: Allows you to chain multiple learning games into a 30- to 60-minute circuit for deep work. : Games are played directly in the browser,
The consumer can evolve independently. If you later add a new field last_login to to_quack() , older services will simply ignore it, while newer ones can start using it right away. | | Replicator | The engine that watches
@classmethod def from_quack(cls, payload: dict) -> "User": # Recreate the object from a dict (ignore unknown keys!) return cls( user_id=payload["id"], email=payload["email"], tags=payload.get("tags", []) )
class UserConsumer: def __init__(self): self.consumer = SinkKafkaConsumer( topic="users", group_id="user-service", bootstrap_servers="localhost:9092" )