1000 × 1000 advertising space. Buy a block. Permanent. Once it fills up, it’s gone.
⚠️ TINKER TOY — NOT LIVE YET — DISCLAIMER
This is a toy prototype. Your ad spaces are local-only — stored only in this browser. They are NOT saved to the server and NOT a real purchase. No payment is taken here. Take it as practice for the real board.
Hover over the board and click to place your block. Green ghost = free.Red ghost = taken or off the edge. Once the board hits 1,000,000 blocks, it locks and it’s gone.
It’s gone.
The board filled up. 1,000,000 / 1,000,000 ad spaces sold. No more space. This is the final board — every block is permanent advertising now.
How it works (when it’s real)
Everyone buys advertising space on the same 1000 × 1000 board. 1 block = 1 ad space. $1 per block. Permanent. No overlaps. First come, first served.
Pick a size — or set your own W × H
Hover to preview your block, click to buy it
Put your brand, link, message, and image on it
When it fills up, it’s gone — no more space, ever. What’s sold stays sold.
When it fills up, it’s gone
The board locks at 1,000,000 blocks. No new ads. No edits. No restock. Permanent.
📸 Final board stays up permanently 🏆 Every ad stays exactly where it was bought — permanence is the product 🕒 Not gone yet — 0.0000% claimed 📜 No expiry. No renewal. No monthly fee. Buy once, stay forever. 📜 Rules: No hate, no NSFW, no ads that lie. Your ad stays unless it breaks the rules.
🏠 Buy advertising space
3 × 4 blocks at (0, 0)$12
📄 Purchase of digital advertising space This is a one-time purchase of permanent digital advertising space. Not a donation, investment, or crowdfunding. Your ad stays — no expiry, no renewal, no monthly fee — for the operational lifetime of the platform. In this toy, no payment is taken.
⚠️ Important: upload an image in the same proportions as your block, or edges will be cropped to fill the block.
◐ Best result: same ratio as your block. For a 3 × 4 block, a 300 × 400px image is ideal.
Reserved for 20 minutes. Close before paying — reservation cancels. Toy: closing just cancels.
Template · Proposed · Not connected
⬇ Backend — what it’ll take
Plausible plan for TinyBoard. We’ll fix the details later — this is the shape of it, not the final wiring.
At a glance
🖥️ 1 — Server you already have
VPS + nginx + PHP + MySQL. No new host. Board is just 3 tables + 4 endpoints.
Step 6 — Snapshot + lock: cron snapshots the PNG every hour, sets is_final when full.
Effort — plausible, will fix later
Piece
Files
Plausible effort
Tables + seed
schema.sql
~30 min
State + claim
state.php, claim.php
~1–2 hrs
Pay + reserve expiry
pay.php, cron
~2–3 hrs
Image crop + serve
image.php
~1 hr
Wire toy → real
TinyBoard.html only
~1 hr
Total
~8 files
~1 weekend
Tables — schema.sql (proposed)
CREATE TABLE board_claims (
id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
x SMALLINT UNSIGNED NOT NULL, y SMALLINT UNSIGNED NOT NULL,
w SMALLINT UNSIGNED NOT NULL, h SMALLINT UNSIGNED NOT NULL,
name VARCHAR(120) NOT NULL, website VARCHAR(255) NULL,
message VARCHAR(280) NULL, color CHAR(7) NOT NULL DEFAULT '#22c55e',
image_url VARCHAR(255) NULL, status ENUM('reserved','paid','removed') NOT NULL DEFAULT 'reserved',
reserved_until DATETIME NULL, paid_at DATETIME NULL,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
CHECK (x + w <= 1000 AND y + h <= 1000),
CHECK (w BETWEEN 1 AND 100 AND h BETWEEN 1 AND 100)
);
CREATE TABLE board_payments (
id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
claim_id BIGINT UNSIGNED NOT NULL, amount_cents INT NOT NULL,
provider VARCHAR(40) NOT NULL, provider_ref VARCHAR(120) NULL,
status ENUM('pending','paid','refunded') NOT NULL DEFAULT 'pending',
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
FOREIGN KEY (claim_id) REFERENCES board_claims(id)
);
CREATE TABLE board_snapshots (
id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
claimed_spaces INT NOT NULL, png_url VARCHAR(255) NULL,
is_final TINYINT(1) NOT NULL DEFAULT 0,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);
API — proposed
GET /api/board/state?since=0 -> claimed, pct, new claims since
POST /api/board/claim {x,y,w,h,name,website,message,color}
-> 201 {claim_id, reserved_until} | 409 OVERLAP | 409 BOARD_GONE | 422 BAD_SIZE
POST /api/board/pay {claim_id, provider} -> 200 {status:'paid'} | 410 RESERVATION_EXPIRED
POST /api/board/image {claim_id, file} -> 200 {image_url} (crop to w:h, max 2000px)
🛠️ Fix later — open questions: Which payment provider? Where do images live (VPS disk vs object storage)? How long do reservations last? Who moderates, and does a removed block go back on sale? None of this is decided — the modal is the placeholder until we pick.
Template only — board above is still local-only until this is wired.
Backend · Template · Proposed · Not connected
⬇ Backend — TinyBoard Backend — Template
This is the proposed backend for TinyBoard. It is not connected — the board above is local-only. When it goes live, claims must be atomic: check free → reserve → pay → mark occupied, or two people can buy the same ad space.
Gone rule:SUM(w*h) <= 1,000,000. When SUM = 1,000,000, the board locks. POST /api/board/claim returns 409 BOARD_GONE. The final board is frozen as a snapshot. No restock.
Tables — schema.sql (proposed)
CREATE TABLE board_claims (
id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
x SMALLINT UNSIGNED NOT NULL, y SMALLINT UNSIGNED NOT NULL,
w SMALLINT UNSIGNED NOT NULL, h SMALLINT UNSIGNED NOT NULL,
name VARCHAR(120) NOT NULL, website VARCHAR(255) NULL,
message VARCHAR(280) NULL, color CHAR(7) NOT NULL DEFAULT '#22c55e',
image_url VARCHAR(255) NULL, status ENUM('reserved','paid','removed') NOT NULL DEFAULT 'reserved',
reserved_until DATETIME NULL, paid_at DATETIME NULL,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
UNIQUE KEY uq_xy (x,y), -- plus overlap check in app code, not just this key
CHECK (x + w <= 1000 AND y + h <= 1000),
CHECK (w BETWEEN 1 AND 100 AND h BETWEEN 1 AND 100)
);
CREATE TABLE board_payments (
id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
claim_id BIGINT UNSIGNED NOT NULL, amount_cents INT NOT NULL,
provider VARCHAR(40) NOT NULL, provider_ref VARCHAR(120) NULL,
status ENUM('pending','paid','refunded') NOT NULL DEFAULT 'pending',
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
FOREIGN KEY (claim_id) REFERENCES board_claims(id)
);
CREATE TABLE board_snapshots (
id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
claimed_spaces INT NOT NULL, png_url VARCHAR(255) NULL,
is_final TINYINT(1) NOT NULL DEFAULT 0,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);
Files — proposed
TinyBoard.html -- this page (board + claim modal)
api/board/state.php -- GET -> {claimed, left, pct, claims[]}
api/board/claim.php -- POST -> reserve w,h,x,y + name/site/message/color
api/board/pay.php -- POST -> confirm payment, mark paid
api/board/image.php -- POST -> validate + crop upload to w:h, store
api/board/snapshot.php -- cron -> PNG snapshot, set is_final when full
assets/board.js -- occupancy, ghost, gone check (inline here for toy)
API — proposed
GET /api/board/state?since=0 -> claimed, pct, new claims since
POST /api/board/claim {x,y,w,h,name,website,message,color}
-> 201 {claim_id, reserved_until} | 409 OVERLAP | 409 BOARD_GONE | 422 BAD_SIZE
POST /api/board/pay {claim_id, provider} -> 200 {status:'paid'} | 410 RESERVATION_EXPIRED
POST /api/board/image {claim_id, file} -> 200 {image_url} (crop to w:h, max 2000px)
Frontend wiring — how this toy maps to real
// Toy now: occupied = Uint8Array(1_000_000), claims[] in localStorage
// Real: occupied comes from GET /api/board/state, ghost checks local copy,
// confirmClaim() -> POST /api/board/claim, then pay, then re-fetch.
// Gone: if (claimed >= 1_000_000) show #goneOverlay, disable clicks.
// Overlap: server must re-check with SELECT ... WHERE NOT (x+w <= ? OR ...)
// inside a transaction. Client check alone is not enough.