by Mad_Man_Moon » Sun Jun 14, 2020 3:10 pm
Cheers, @barbaz, much obliged!
Have been doing a bit more playing around (I found another export, and it's huge, so am building a solid reference import/export, hence my quietness) and found that even though there's no way to comment in JSON (assumed that is the language) we can basically make up sites to use as categorisation and noscript preserves the order in which sites are presented in the import / export process.
So, if I have:
Code: Select all
"sites": {
"trusted": [
"__MOONYCAT1",
"§:site1.com",
"§:site2.com",
"§:site3.com",
"__MOONYCAT1",
"§:site4.com",
"§:site5.com",
"§:site6.com",
"__NOMOONYCAT"
],
"untrusted": [
"0jzxzd21.com",
Then if I add site7, site8, site9, and export, the file will look like this:
Code: Select all
"sites": {
"trusted": [
"__MOONYCAT1",
"§:site1.com",
"§:site2.com",
"§:site3.com",
"__MOONYCAT1",
"§:site4.com",
"§:site5.com",
"§:site6.com",
"__NOMOONYCAT",
"§:site7.com",
"§:site8.com",
"§:site9.com"
],
"untrusted": [
"0jzxzd21.com",
This could also help as a Work Around to some kind of organisation ... as long as one does an export every now and then to manage one's list.
Probably best not to use the underscore in case the main man decides that it's a required character for something, but you get the drift.
Oh, and I just had the inkling of another idea using Microsoft's Power Automate (Flow) JSON Parser ... ... one could easily set up a system using sharepoint lists to manage your categorised trusted sites, or, perhaps more relevant/cheap, a local excel file ...
barbaz wrote: ↑Fri Jun 05, 2020 10:12 pm
Entries starting with "https://" will only match that exact domain, not subdomains. If you want to match only HTTPS while including subdomains, use the "§:" (which is what the green lock does).
Domain entries without prefix match both HTTPS and plain HTTP.
Cheers, @barbaz, much obliged!
Have been doing a bit more playing around (I found another export, and it's huge, so am building a solid reference import/export, hence my quietness) and found that even though there's no way to comment in JSON (assumed that is the language) we can basically make up sites to use as categorisation and noscript preserves the order in which sites are presented in the import / export process.
So, if I have:
[code] "sites": {
"trusted": [
"__MOONYCAT1",
"§:site1.com",
"§:site2.com",
"§:site3.com",
"__MOONYCAT1",
"§:site4.com",
"§:site5.com",
"§:site6.com",
"__NOMOONYCAT"
],
"untrusted": [
"0jzxzd21.com",
[/code]
Then if I add site7, site8, site9, and export, the file will look like this:
[code] "sites": {
"trusted": [
"__MOONYCAT1",
"§:site1.com",
"§:site2.com",
"§:site3.com",
"__MOONYCAT1",
"§:site4.com",
"§:site5.com",
"§:site6.com",
"__NOMOONYCAT",
"§:site7.com",
"§:site8.com",
"§:site9.com"
],
"untrusted": [
"0jzxzd21.com",
[/code]
This could also help as a Work Around to some kind of organisation ... as long as one does an export every now and then to manage one's list.
Probably best not to use the underscore in case the main man decides that it's a required character for something, but you get the drift.
Oh, and I just had the inkling of another idea using Microsoft's Power Automate (Flow) JSON Parser ... ... one could easily set up a system using sharepoint lists to manage your categorised trusted sites, or, perhaps more relevant/cheap, a local excel file ...
[quote=barbaz post_id=102286 time=1591395156 user_id=181509]
Entries starting with "https://" will only match that exact domain, not subdomains. If you want to match only HTTPS while including subdomains, use the "§:" (which is what the green lock does).
Domain entries without prefix match both HTTPS and plain HTTP.
[/quote]