https://github.com/csingendonk/clientsidenetworkcontrol
A single file containing a JavaScript iife that returns and initiates a completely client-side vanilla in-page ui where you can log and additionally block network traffic before it completes (basically a border guard per se) and prompts you to disintegrate or allow each request using thread blocking logic.
https://github.com/csingendonk/clientsidenetworkcontrol
Last synced: over 1 year ago
JSON representation
A single file containing a JavaScript iife that returns and initiates a completely client-side vanilla in-page ui where you can log and additionally block network traffic before it completes (basically a border guard per se) and prompts you to disintegrate or allow each request using thread blocking logic.
- Host: GitHub
- URL: https://github.com/csingendonk/clientsidenetworkcontrol
- Owner: CSingendonk
- Created: 2025-03-16T08:19:34.000Z (over 1 year ago)
- Default Branch: CSingendonk
- Last Pushed: 2025-03-17T06:10:09.000Z (over 1 year ago)
- Last Synced: 2025-03-17T07:26:48.637Z (over 1 year ago)
- Language: JavaScript
- Size: 69.3 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# All rights reserved.
- as per github:
"...However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work."
Proof of concept drafts can be found in my whoops and htmlpanels repositories as well
# © 2024, 2025, 2026 - Chris Singendonk
Copyright (c) 2024 - Chris Singendonk. All Rights Reserved.
This work is **NOT LICENSED** for public or private use, modification, distribution, reproduction,
or the creation of derivative works **without explicit written approval from the author**.
The default copyright laws apply, meaning **you may not use, modify, or distribute any part of this work
in any form** unless you have received direct permission from the copyright holder.
# ClientsideNetworkControll
A single file containing a JavaScript IIFE that returns and initiates a completely client-side,
vanilla in-page UI. This tool logs and, if desired, blocks network traffic before it completes—acting
as a border guard of sorts. With extensive options, you can control what, how, where, when, and even
if logging occurs. Visualize and step through DOM events and mutations, performance metrics, console output, and more
-all dynamically within your active browser tab with or without a network connection.
- This is an obsolete draft copy of the complete code from a previous point in time and state.
- It does work when ran in the document browser scope.. however you get it there ;)
- The three big browsers' DevTools console works great, just paste the "core.js" script into the console to test it.
- Please contact for collaboration.
# ZERO DATA COLLECTION
### NO COOKIES TRACKERS OR DATA COLLECTION
## STATIC LOCAL OFFLINE
- though it can be served from anywhere.
- - see release 1 for demo.
## BASE BLOCKING FUNCTIONALITY WORKS WITH LESS THAN 5000 chars.
- includes XHR, BGSW, WS, HTTP.
[https://github.com/CSingendonk/ClientsideNetworkControl/blob/CSingendonk/core.js
](https://github.com/CSingendonk/ClientsideNetworkControl/blob/CSingendonk/core.js)
## UI CSS AND HTML AND JS MODULES IN ONE FILE UNDER 3000 lines.
- [(https://github.com/CSingendonk/ClientsideNetworkControl/blob/CSingendonk/initLogs.js)
](https://github.com/CSingendonk/ClientsideNetworkControl/blob/CSingendonk/initLogs.js)
## COPYRIGHT & RESTRICTIONS
Unauthorized usage, reproduction, modification, or distribution of this work, in whole or in part,
is a violation of copyright law.
===========================================================
## Imagine
a gardener who has an apple tree, and dreams of making apple pie. But there’s one catch: pies have never been invented.
The gardener, brimming with visionary ideas, bakes apple cakes but shares the concept of pie with anyone who will listen.
Then, someone hears the idea, takes the gardener's apples, bakes pies, and claims ownership of them.
Not only that, but with more trees and resources eventually patent the pies — completely altering the landscape and profiting off the gardener's vision.
They engineer the perfect system to mass-produce the apples, all while claiming full credit for the pies.
Sure, the pies multiply, but the gardener is left with their tree and an idea.
Unable to support the developments needed to bake pies themselves, they are stripped of the opportunity to build upon their creation.
Their vision, their potential to evolve and contribute further, is lost forever.
This scenario is not just about lost fruit; it's about the consequences of creative espionage, plagiarism, and failure to properly attribute sources.
In the world of code and intellectual property, failure to honor the original creator leads to more than just stolen work—it stifles innovation.
The creator’s future contributions are cut off, and the adopting party is limited by their own inability to concieve the original idea.
When someone uses code without permission, claiming it as their own, or fails to properly attribute the original author, they’re not just stealing a product,
they’re hindering the very source of future growth. The original creator loses the chance to evolve, improve, and contribute further.
Meanwhile, the adoptee now lacks the imagination and insights of the original creator that could help them break through roadblocks.
In the same way that the gardener’s vision for pies was lost without attribution, so too is the progress of an idea, concept, or innovation when the source is not credited.
The proper attribution and recognition of intellectual work are not mere formalities,
they are vital to ensuring that creativity continues to flourish, not just for the original creator but for everyone who benefits from it.
# Think of it this way:
You’ve poured countless hours into designing and building a car.
You share your creation selectively, knowing that collaboration is the key to progress.
Sure, you didnt invent cars, but let's say you solve an issue in a way that is unique to your car, but not quite "up to snuff".
Others recognize its potential, but instead of working with you, they take the blueprint and run with it,
making improvements behind closed doors while you remain unaware.
They release their own version, solve problems you never encountered, and refine the design—but you,
the original creator, are left out of the loop, unable to learn from or contribute to what has become
of your own work. Your progress is artificially limited, while others reap the rewards of your effort.
This is why permission and attribution matter:
Innovation isn’t just about the end product—it’s about **inclusion, shared learning, and the mutual respect**
that comes from working together. Acknowledgment ensures that those who plant the seeds of progress
are not cast aside while others harvest the results.
===========================================================
## CONTACT FOR APPROVAL
If you are interested in using, modifying, or building upon this work,
**you must first obtain explicit written permission from the author.**
I welcome collaboration, but only when mutual understanding and respect are upheld.
Contact: [https://www.github.com/csingendonk]
===========================================================
## LEGAL NOTICE
Any unauthorized use, reproduction, modification, or distribution of this work, in whole or in part,
is strictly prohibited and may result in legal action. By accessing or handling this work in any way,
you acknowledge and agree to abide by these terms.
**If in doubt—ask first.**
**Any API or logic used, but not defined, within is most likely documented in W3, mdn, or google dev docs as the script uses base JS web APIs and those are subject to the owners copyright.**
**Any breech of contract, law, or other official restrictions occuring due to use of this work is entirely upon the user**