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
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
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
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.
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/