Reduce potential ISP/Gateway privacy concerns related to user tracking etc.
[!NOTE]
There aren't any inherent privacy issues related to TurboBoost Commands (TBC). TBC does NOT track user/visitor data for any purpose. The original cookie and header management simply served to facilitate a better user experience (UX).
This PR updates the "state" mechanics to use the URL and hidden form fields rather than cookies and headers for this purpose.
TurboBoost state management provides a facility for remembering and restoring the state used to render the last representation of a page or component. It also provides the facility to support client side optimistic updates that we can resolve server side. All of this tooling enables developers to provide a great reactive user experience to visitors with minimal code.
After more discovery and some conversations with AI, I've teased out the following areas that are potential spots that may can appear suspect to naive privacy tools.
Storing larger values in cookies
Using too many cookies
Attaching larger values to HTML request headers
Using too many custom request headers
Updating or mutating an HTML meta tag too frequently
This PR addresses each of the above items to de-risk privacy hawks from attaching a false positive flag due to any library activity or operations.
Reduce potential ISP/Gateway privacy concerns related to user tracking etc.
This PR updates the "state" mechanics to use the URL and hidden form fields rather than cookies and headers for this purpose.
TurboBoost state management provides a facility for remembering and restoring the state used to render the last representation of a page or component. It also provides the facility to support client side optimistic updates that we can resolve server side. All of this tooling enables developers to provide a great reactive user experience to visitors with minimal code.
After more discovery and some conversations with AI, I've teased out the following areas that are potential spots that may can appear suspect to naive privacy tools.
This PR addresses each of the above items to de-risk privacy hawks from attaching a false positive flag due to any library activity or operations.