ABOUT DIGG🔥TINDER

The “what is this thing?” page. Built to be honest, readable, and mildly neon.

TL;DR Behind the scenes Data source Cloudflare Worker How random is random? Eligible pool size Data freshness FAQ
TL;DR

Digg Tinder is a simple “random community” explorer. It pulls a public JSON snapshot of Digg communities from LiveSearch (credit: @justinpruett), runs it through a tiny Cloudflare Worker, and serves randomized picks with optional filtering.

No rankings. No recommendations. No “you might like.” Just: Next → random community.

Behind the scenes (plain English)

When someone visits Digg Tinder, the page loads normally (HTML/CSS/JS). Then when you click Next, your browser asks my Cloudflare Worker for a random community.

Browser → Worker request
/?random=1&min_posts=…&exclude=…&count=…
Worker → LiveSearch snapshot
api_1.php?option=communitystats&suboption=platform&platform_id=1
Worker → Browser response
Returns JSON for one community (or a batch)

The Worker caches the full dataset for speed (15 minutes). Your “random” results are never cached (always no-store).

↑ Back to top

Where the data comes from

Digg Tinder uses a public JSON dataset provided by LiveSearch, which collects community stats for Digg (platform_id=1). Credit for this dataset: @justinpruett.

Exact endpoint used:

https://www.livesearch.app/api_1.php?option=communitystats&suboption=platform&platform_id=1

Important: this is snapshot-style data. It’s not guaranteed to match Digg’s live counts at this exact second. i

↑ Back to top

What the Cloudflare Worker does

The Worker is a tiny API sitting between your browser and the LiveSearch JSON feed. Its job is to make requests fast and consistent: normalize fields, cache the dataset briefly, apply filters, and return random picks.

Key behaviors
• Master list cached for 15 minutes at Cloudflare’s edge
• Random picks are no-store (always fresh randomization)
• Preview images (OG images) are cached for 1 day (optional enhancement)
↑ Back to top

How random is random?

“Random” here means: pick from the eligible pool without popularity weighting. Not trending. Not recommended. Not personalized.

If you set Min posts, the Worker filters the dataset first, then samples randomly from that filtered pool.

Digg Tinder does not rank communities. It does not recommend based on your account. It’s closer to pulling a card from a shuffled deck than browsing a “Top” list.
↑ Back to top

Eligible pool size (live)

This indicator shows how many communities are currently eligible under a given Min posts filter, based on the Worker’s current cached snapshot.

Min posts

Pool size: - i

This is fetched by making a single random request and reading the returned _meta.pool_size. No extra Worker endpoints required.

↑ Back to top

Data freshness Transparency mode

Last refreshed: Loading…

Source: Loading…

This is fetched from the Worker’s /?meta=1 endpoint (always no-store). If the cache is cold, it may show “warming up” until the first dataset fetch completes.

↑ Back to top

FAQ

What Digg🔥Tinder is not.

This tool is intentionally simple:

Every click is a fresh draw from the same snapshot.

Why do counts sometimes look “off”?

Because this is snapshot data from LiveSearch - not real-time Digg numbers. Different tools may also use different collection times, definitions, or cleanup rules. i

Does Digg Tinder track me?

No tracking logic is required for the app to work. It requests JSON from the Worker and renders it.

↑ Back to top