Steve Seguin steveseguin

The main correction: xpu should not be an engineName. It should be a backend/accelerator/runtime field under vllm or another engine.

Essential

Separate engineName from backend.
- engineName: vllm
- backend: xpu, cuda, rocm, metal, sycl, level-zero, openvino
- Optional: backendStack: oneAPI 2026.0, Level Zero, vllm-xpu-kernels
Add structured quant fields, not just a free string:

From: Steve Seguin <steve@hovr.it>
Sender: steve@hovr.it
Date: Mon, 15 Apr 2013 12:52:57 -0400
To: <YYYY.YYYY@gmail.com>
Cc: XXXX XXXX<XXXX@hovr.it>
Subject: whitepapers regarding CUDA/GPGPU and HOVR.IT

Hi YYYY,

Below is a copy‑pasteable Markdown guide you can hand to anyone running a white‑label fork of VDO.Ninja on GitHub Pages (eg. modified main.css, index.html, translation JSON files). It shows the safest, least‑surprising way to get from v22.x to the latest stable release without being a Git pro.

TL;DR

Back up your current fork.

Update your fork to the latest stable release tag (currently v28.0, released Aug 26, 2025). ([GitHub][1])

Re‑apply branding via non‑conflicting overrides (&css, &base64css, &js) and translation files instead of editing core files. ([VDO.Ninja][2])

If you only want “alpha/preview” features, you can sync your fork to the upstream develop branch—but that’s intentionally less stable. ([GitHub][3])

Conventions & Limits (v28)

Encoding

URL parameters that carry freeform text or URLs should be URL‑encoded. Examples: label, password, endpage, avatarimg, bgimage, overlayimage, discordwebhook, WHIP/WHEP URLs.
The app decodes many fields internally via decodeURIComponent(...) (e.g., images, webhooks, endpage) and encodes some (e.g., password) before transport. When in doubt, encode.
Booleans accept: true (presence), or strings true/1/yes/on; falsy strings false/0/no/off disable.
Lists: comma‑separated (e.g., view=SID1,SID2, include=SID3,SID4).

IDs and Names

Stream ID (push/id/permaid):

If you think a new section for STATE NODEs is useful, feel free to do that also

✻ Thinking…

The user is asking about creating a new section for "STATE NODEs" in their event flow system. Looking at the context, this is about legitimate software development for a browser extension that manages event flows for social media streams. The user wants to add state management nodes (like queues, gates, flip-flops) to better control message flow and prevent overlapping events.

This is clearly not related to any malicious cyber activity - it's about improving the architecture of a legitimate application to handle concurrent events better. The user is asking me to propose a plan for implementing these state management features in their existing event flow system.

How to Contribute Code to VDO.Ninja

Step 1: Fork the Repository

Go to https://github.com/steveseguin/vdo.ninja
Click the "Fork" button (top right)
This creates your own copy of VDO.Ninja

Step 2: Clone Your Fork

git clone https://github.com/YOUR-USERNAME/vdo.ninja.git

Social Stream Actions and Properties Reference

Actions (using action property)

Navigation Actions

`nextPinned`

Selects the next pinned message and highlights it

	{
	"lastUpdated": "2026-01-09",
	"disclaimer": "These listings are user-submitted and community-provided. Social Stream Ninja does not validate, endorse, or guarantee these services.",
	"services": [
	{
	"id": "3abb0554-14f6-4149-92da-f9c50a5bfaf0",
	"addedDate": "2025-12-11",
	"name": "Kizovibes",
	"discord": "kizovibes",
	"platforms": [

	async function limitConcurrentViewers(maxCount) {
	if (!session.whepInput \|\| !session.salt) {
	throw new Error("Missing session.whepInput or session.salt");
	}

	const WORKER_URL = "https://hash-counter-worker.vdo.workers.dev";
	const WINDOW_MS = 5 * 60 * 1000;

	const hashValue = `${session.whepInput}${session.salt}`;
	let intervalId;

	(function (global) {
	'use strict';
	/**
	* VDO.Ninja SDK v1.0 - STILL IN DEVELOPMENT AND MAY CONTAIN BUGS
	* @author Steve Seguin
	* @license AGPLv3
	*/
	class VDONinjaSDK extends EventTarget {
	/**
	* Sanitize stream ID