r/perchance

Hey everyone!

I’m pretty new to making and sharing things like this, so I’m a little nervous about posting it 😅

I made an AI Dungeon Master called Fallen & Forged on Perchance.

I deliberately didn’t promote it at first. I wanted to see if people would actually use it without me pushing it everywhere. It recently reached 500+ vieuws so I finally decided to share it and see what people think.

I’d genuinely love some honest feedback good and bad.

What do you like?

What do you think could be better?

Does it feel different enough from other AI Dungeon Masters?

I’m not really looking to just advertise it. I’d honestly like to learn from people who actually play this kind of thing.

If anyone wants to try it, here it is:

https://perchance.org/fallen-forged-ai-dungeon-master

Thanks for taking the time to read this!

I made a chat simulator where Percy and Wingman argue and interact with whatever you type. Or let them go at each other for some real entertainment 🤣

https://perchance.org/ai-chat-simulator

https://perchance.org/kiln-browser-host

Hey everyone! Here is the second batch of concept art images for my Spaghetti-Western project.

I really took your suggestions and critiques from the first post to heart and used them to refine the overall concept. Here is what I tweaked for this run:

1. 1960s Film Aesthetic: I pushed the prompts to strongly mimic the classic '60s celluloid look, leaning heavily into the Sergio Leone style.
2. Widescreen Aspect Ratio: I switched to a horizontal, wider format to better replicate the original "Techniscope" aspect ratio used in those movies.
3. Period-Accurate Clothing: I forced strict period-appropriate clothing in the prompts to stop the AI from generating those borderline "fantasy" outfits.

Take a look and let me know what you think. If you have any suggestions, ideas, or feedback, they are more than welcome!

I turned an active browser tab into a fully functional Image Generator API using ntfy as a relay

Generator / Endpoint: https://perchance.org/papi

I built a working Image Generator API where an open browser tab acts as the dedicated compute worker, communicating with external clients entirely through public relays. No cloud API subscription or backend server setup required—it is up, running, and ready to use.

How the System Works

The browser tab is the actual engine powering the generator:

* Start Worker: Open the generator tab, click Start Worker, and leave the tab open.

* Dispatch Job: Any client sends a POST request with a JSON payload to an ntfy topic:

[https://ntfy.sh/\](https://ntfy.sh/){endpointId}-req

* Generate: The open browser picks up the job via the relay, runs the image generation pipeline, and sends the result back to:

[https://ntfy.sh/\](https://ntfy.sh/){endpointId}-res

* Fetch Result: The client listens via SSE or polls the -res topic for the corresponding jobId to receive the output (image URL or base64).

[ Client / App ] ─── POST /req ───▶ [ ntfy.sh Relay ] ─── SSE ───▶ [ Browser Generator ]

│ (generates image)

[ Client / App ] ◀── SSE/Poll ───── [ ntfy.sh Relay ] ◀── POST /res ───────┘

API Contract

Request (-req topic):

{

"jobId": "unique-uuid",

"prompt": "detailed subject description, high detail...",

"negative": "blurry, low quality",

"resolution": "512x512",

"upscale": "off",

"format": "jpeg"

}

Optional parameters: quality, negative. Large, structured prompts work without issue.

Response (-res topic):

{

"ok": true,

"jobId": "unique-uuid",

"width": 512,

"height": 512,

"imageBase64": "...",

"imageUrl": "..."

}

If an error occurs, it returns {"ok": false, "error": "..."}. For large payloads, ntfy converts the data into an attachment.url.

Performance & Benchmarks

Generation speed depends entirely on the host machine running the generator tab, not the requesting client:

| Host Device | Typical Generation Speed |

|---|---|

| Mid-tier PC / Laptop | ~5 – 50 seconds |

| Mobile Device | ~20 – 250 seconds |

* Host Latency Rule: A phone requesting from a PC worker tab receives images at PC speeds.

* Foreground Requirement: Browsers heavily throttle background tabs. The tab must stay open and active in the foreground; background drops throughput by roughly 10×.

Current Status & Roadblocks

* Generation: Stable and fully functional. Though love to hear how we can optemise the speed and add background processing. I tried few things and tell you it help from nothing to something in background tabe problem. But we need to optemise it more.

* AI Upscaling: In-browser ESRGAN tiling currently leaves subtle vertical/horizontal seam lines across tiles. If anyone has clean implementations for border feathering or overlap blending in WebGL/WASM upscaling, advice is welcome.

* In Development: Adding structured JSON conversations for LLM integration and improved parallel job scheduling.

Feel free to plug into the endpoint and test it out. Feedback on the relay flow or tips on in-browser tile seam blending are appreciated!