QSCS - A State Synchronization platform for distributed systems
Posted by dan_c350@reddit | programming | View on Reddit | 7 comments
A platform of protocols that synchronize state accross registers for distributed apps. A small static C core that interperets packets and payloads, compresses them into state objects using schema agnostic data processing, then sends minimal delta packets, over an encrypted socket, that get rehydrated by interpereters both client and server side reducing bandwith usage by up to 100% depending on the request and collapses the attack surface to a single encrypted socket.
programming-ModTeam@reddit
r/programming is not a place to post your project, get feedback, ask for help, or promote your startup.
Technical write-ups on what makes a project technically challenging, interesting, or educational are allowed and encouraged, but just a link to a GitHub page or a list of features is not allowed.
The technical write-up must be the focus of the post, not just a tickbox-checking exercise to get us to allow it. This is a technical subreddit.
We don't care what you built, we care how you build it.
flower-power-123@reddit
I think you posted this yesterday. What does QSCS stand for? What is this thing and why do you keep posting it? Please explain it like I'm five. I don't get it at all. You seem to be recreating some aspects of HTTPS. How is this different or better?
Right_One_1770@reddit
I think he’s trying to reinvent SDR, (Shared/Sparse Data Replication) by eliminating redundant data across nodes. Like Spread did way back. Chunking, segment hashing, indexing, reassembly (Selective Data Redundancy Elimination (SDRE) and Multi-Resolution Chunking (MRC)). Or maybe it’s malware.
dan_c350@reddit (OP)
QSCS does reduce redundant data across nodes, but not by chunking or hashing content, there is no content‑based segmentation no rolling hash and no dedupe tables,
QSCS interperets packets, updates a state object, emits a compressed delta with enough information for the client to regenerate the message/payload taking into account all previous transactions when generating said delta
dan_c350@reddit (OP)
Hi yes i did post yesterday, this is not http specific and it is not https. It was designed initially as an orchestration tool for hybrid classical quantum compute. But then realised that classical protocols.The http interpereter is just the first one i am using it for development of the stack as its easy to work with. It secures any protocol its run against as once identity is established keypairs are generated for each endpoint. Its encryption without the need for ssl certificates or any knowledge of how to configure them. Its all handled over the socket layer before any requests are sent. Then the requests themselves are compressed for example all requests have :// / in them so theyre not necessary to be sent saving a few bytes. Usually the domain name doesnt change either so that doesnt need to be sent. On the return payload qscs rehydrates the html/css/js state object as it knows how to reform the syntax each tag/item/value are indexed in the local cache and if the next request only updates a few items only that is sent from the server.
This is a far more efficient & secure way of communication than message based protocols.
Does that help?
Right_One_1770@reddit
Can I build from source?
dan_c350@reddit (OP)
It's closed source for now, although patents are pending. With a view to open the source under MIT after the first production ready version. Ill drop you a DM when its available