Browser Profile Settings - SOcial LInked Data SOLID

[York-Earwaker]

Overview
Every browser would have identical minimal standard behaviour on uploading setting from SOLID data pod.

One ring to rule them all and in the data pod bind them
Browser Profile Settings - SOcial LInked Data SOLID
Browser configuration
Multiple browser profiles for different user pseudonyms
Multiple browser profiles for different personas
Multiple browser profiles for different use cases
The same profile for all browsers
Different profiles for different dowsers
Switch profiles
Multiple profiles can be used simultaneously
Different browser vendors
Different browser instances
In the same browser instance but different tabs? - possibly too much at this point

From a systems level view considering the entire internet ecosystem the browser configuration/profile/properties/settings/flags/… attributes are a subset of the ecosystem capability. Similar profile settings might be created for capability that fulfils all the OSI seven layer model elements. For example, and in close relation to browsers, settings for DNS servers, or FTP servers, or HTTP servers, and so on.

See discussion here re browser blacklist whitelist

Security - DNS Blacklists and Whitelists

For fine grained management of internet domains and subdomains to block or allow access to. Domain names and resource indicators / locators. Use of SOcial Linked Data SOLID for single data source to configure all browsers. This would make the solution OS independent. Might be used in tandem with hosts file 127.0.0.1 loopback. The hosts file localhost loopback is a non optimal solution to the issue of control of domains for inclusion in a blacklist and has no whitelist capability. It is also no…

Separation of concern yes in regard to bounded capability sets within an application like a browser or dns server. But the requirement to integrate at a systems level for the entire internet ecosystem.

It may for example also include app ( that is application configuration information ) . So that there is a record of user configuration of applications. Often when applications update to new releases, sometimes automatically, configuration information is lost and the application reverts to default settings. This might impact safeguarding or security or privacy and so on. Keeping a record of app (application) configuration in the user SOLID pod the application would should be required to reset to any saved user configuration.

See discussion here

Browser Ontology - terminology and term relations

A standard set of terms and relations for browser technology. Does this already exist? Device independent capability terms and concerns. Systems engineering, software engineering, systems of systems SoS, internet of things IoT, digital twin, human digital twin, … There are many standards that provide the underlying technology specifications but is there an existing standard / specification for a standard set of terms for browser capability. To consider. The line between app and browser seems …

Standards Organisations
IETF
W3C

References
SOLID, Wikipedia, https://en.wikipedia.org/wiki/Solid_(web_decentralization_project)
SOLID, MIT, https://www.csail.mit.edu/research/solid-social-linked-data
SOLID, GitHub, https://github.com/solid
SOLID, W3C Community Group, https://www.w3.org/community/solid/
SOLID, Project, https://solidproject.org/
SOLID, Solid Technical Reports, https://solidproject.org/TR/protocol
SOLID, Browser, https://podbrowser.inrupt.com/