A tiny distributed substrate experiment: single binary, single port, remote page retrieval with no HTTP
Posted by dan_c350@reddit | programming | View on Reddit | 12 comments
I’ve been experimenting with a small distributed substrate concept and shipped a fun milestone this week.
QSCSCore v1.1 is a fully static 2.3 MB binary that:
- boots instantly
- opens a single entangled link on TCP:4443
- and pulls back a remote HTML page
- without using HTTP, DNS, a resolver, or a web server
It’s basically a deterministic delta engine that synchronises state between two endpoints and reconstructs the page on the client side.
There’s a small public demo running here if you want to poke it:
spook.systems/public/demo
This isn’t a product or a protocol announcement — just a networking experiment that I thought some of you might find interesting.
Happy to answer technical questions.
programming-ModTeam@reddit
No content written mostly by an LLM. If you don't want to write it, we don't want to read it.
ckdx_@reddit
Can you give us a real use-case and tell us what problem it solves? I've looked at your "use cases" page and I remain uncertain what value this brings.
dan_c350@reddit (OP)
Ok, for http based services (websites & rest based applications) there are no snoopable metadata headers in the packets just a deterministic binary stream. The packets are also reduced, rather than sending a full request/ response payload the decoded packets only reference actual changes so rather than http://domain/uri/?username=new you have stateID {index4: new} , also packets can only be sent authenticated end points determined by identity based trust before the transmission meaning no further tcp handshakes are required. this will work with plugin wrappers for all message based protocols and scale to network domains. Think sql clusters that synchrinize instantaneously through minimal state derived objects not full message relay or binary log replication (which can be notoriously flaky) eventually youd have an open network with endpoints that can only communicate with trusted domain members revealing no information publicly about what services are running. And no way of interupting/poisoning established sessions. It also provides a potential to move routing away from node to node, and towards client -> application
nekokattt@reddit
all of the stuff in this that you actually would need is achievable via https already, just with standardised interfaces.
reveil@reddit
So you just discovered TCP and decided to vibe vomit a crappier version of HTTP1.0 and call it a bunch of buzzwords? What does substrate even mean? Distributed? Where? Between what?
flower-power-123@reddit
I have no clue what you are doing. What is QSCS? Why would I want this?
dan_c350@reddit (OP)
QSCS isn’t trying to replace HTTP — the demo just shows the model in a visible way.
The underlying substrate is about reducing complexity in distributed systems:
• Reduced attack surface (single TLS port, no resolver, no server stack) • Reduced bandwidth through deterministic delta updates • Lower handshake overhead and less network chatter and metadata on packet transfer • Lower CPU load due to minimal protocol work • Identity‑anchored trust instead of endpoint‑based trust • Simplified hybrid compute workflows where state sync matters more than request/response
The demo is just a small example — the benefits are in the substrate model itself.
flower-power-123@reddit
What does QSCS stand for? What does this thing do? Explain it like I'm five. Google gives nothing.
mfitzp@reddit
This is so obviously LLM generated, just the general tone/style, weird bullet list, etc.
But the X not Y of "Reduced attack surface (single TLS port, no resolver, no server stack)" and "QSCS isn’t trying to replace HTTP — the demo just shows the model in a visible way." is the big giveaway.
You can prompt your model to stop doing this, or alternatively, just stop.
SpaceMonkeyAttack@reddit
I can't tell if I just lack the vocabulary and domain knowledge to comprehend, or if that website is AI-generated word salad.
frankster@reddit
It's not a you problem
frankster@reddit
Sounds like AI word salad bollocks to me