bongsmoke.cloud
Headquarters · About us

We are a cloud that forgets, a standards body, a panda scheduler, a cemetery, a relay station off Neptune, and the national headquarters of the Juggalos, for some reason.

This is the About page. It is complete. We keep no records, so nobody can check.

The seal. Found in the lobby, already framed.

Affiliations

Building directory

One building, all floors public. The elevator is a plain link: every trip is a full page load, and the page you left forgets you were there.

All floors

Juggalo National Headquarters

We are the national headquarters of the Juggalos. There was no vote. There was no letter. One morning it was on the directory, and it looked right there. Whoop whoop.

OfficialVisitor desk

Juggalo National Headquartersbongsmoke.cloud · all floors

Front desk hours
Whenever.
Faygo on tap
No. We are a website.
Membership records
None. We keep no records. You are already a member.
Dues
None. We would have to remember who paid.
Dress code
Face paint recommended. Widely reported (2019) to confuse facial recognition, which is more privacy than most cookie banners provide.
Federal classification
Juggalos: “loosely-organized hybrid gang” (FBI, 2011). This building: unclassified. We keep no records to classify.
How this happened
For some reason.

The giant pandas were already wearing the face paint when they arrived. We did not ask.

Self-declared. Unrecognized. Not affiliated with anyone who has a lawyer.

Whoops this visit: 0Whoops remembered: 0

Unpainted. For now.

Miracles

Miracles, on this very website

Things this site does every time you load it. We talked to a scientist.

  1. Miracle No. 1

    The part of a link after the # never leaves your browser.

    Why it happens: The fragment is dereferenced by the user agent alone. It is not in the request, the Referer, or any log. Your note rides there.

    RFC 3986 §3.5How it works

  2. Miracle No. 2

    A server hands out a key exactly once, and then it can’t.

    Why it happens: One atomic SET with NX: the first caller writes the burn mark and gets the key. Every caller after that finds the mark and gets nothing.

    Redis SET … NXThe Burn Desk

  3. Miracle No. 3

    Your browser runs pandas in a loop, forever, and never drops one.

    Why it happens: One task, then every microtask, then maybe a render step. Repeat until the tab closes. It is written down.

    HTML Living Standard, event loopsPandamonium

  4. Miracle No. 4

    Something eats the garbage, and nobody scheduled it.

    Why it happens: The language says when an object may be collected, never when it will be. Even a FinalizationRegistry callback is not promised to run at all.

    ECMAScript, FinalizationRegistryThe basement

  5. Miracle No. 5

    A 39 MB game engine runs on a web page and stores nothing.

    Why it happens: The engine is WebAssembly, and its save paths are an empty list, so it never opens browser storage at all.

    WebAssemblyNeptune

  6. Miracle No. 6

    Zero cookies, and the status bar at the bottom can prove it.

    Why it happens: It reads document.cookie on this page, counts what it finds, and shows you the number. The number is zero.

    HTML, document.cookieSecurity

  7. Miracle No. 7

    Nothing on this page came from a stranger.

    Why it happens: The Content-Security-Policy allows this origin, plus one script and one request from our own visit counter, and refuses every other origin for scripts, styles, fonts, images and requests.

    CSP Level 3Security

  8. Miracle No. 8

    The whoop is not a file.

    Why it happens: The policy says media-src ’none’, so there is no audio file. The whoop is arithmetic: an oscillator swept upward, twice.

    Web Audio, OscillatorNodeThe visitor desk

Org chart

Everybody reports to the couch

A flat organization, because the couch is. Two departments are not on the chart. Nobody put them there, and nobody can take them off.