Cookie Engineer
Cookie Engineer
The `Download` implementation is the outsourced Download stream that abstracts away all the necessary overhead that's necessary for 206 Partial Content, whereas the `Request` API should be the high-level abstraction...
The `Compeer` implementation is now almost ready. What's missing is a dedicated `Review` for its featureset and the integration of peers to the Settings in the Browser Profile and the...
The Tabs sidebar should show the Browser request statistics at the bottom. The current idea is that the statistics should reflect whether or not bandwidth could be saved and whether...
The Peering Settings should be available for advanced users, in order to reflect whether or not the local Stealth instance should announce itself to other Peers via Multicast DNS-SD. Possible...
The Search Page needs to be improved to reflect a more efficient bandwidth usage. - [ ] Implement Peer-to-Peer support to download from local Peers and their cached URLs, if...
All tasks should be able to be run in a scheduled manner, and additionally it should be possible to run them immediately and in a reoccuring manner. As task should...
Stealth is now pretty failsafe to come around NAT environments that block IPs and/or ports via delegating traffic to networked Peers. In future (after the MDNS implementation) this will also...
The Peer Service needs to be reimplemented after the Peerer Middleware has been implemented with all its features. - [ ] Implement a way to download a `beacon` entry from...
The `stealth:fix-request` error page needs integration to download cached URLs from connected Peers - and in case no Peer is available - the Web Archive. - [ ] Integrate download...
DNS64 and NAT64 are concepts that want to provide IPv4 access to IPv6 only clients that cannot understand legacy IPv4 networking. As far as I can tell the [RFC6052](https://datatracker.ietf.org/doc/html/rfc6052) isn't...