Reminder that Firefox has a pathway to specifying some settings, including ones not exposed to users any other way, with a config file stored on disk.
They call it enterprise policies but anyone can use it by just putting a file in the location indicated on that site.
You can disable entire features, opt out of Telemetry before your first launch of Firefox on a new install, declare you never want to be part of studies, turn off their ML integration and keep it off, force about:config preferences in a way that can't be "accidentally" reverted, etc.
reshared this
Electric Gremlin
in reply to Electric Gremlin • • •Sensitive content
This is mine at the moment. I throw out a lot of stuff; be familiar with what everything does by cross-referencing it with the site in the last post, or a preferences list, before just using this because it turns off auto-updating, half of Firefox's features, and changes the UI in ways.
You can't comment JSON 🙃
Oliver Jensen
in reply to Electric Gremlin • • •you can indeed comment json if the schema isn't restricted and you are willing to be silly enough 😁
```
{
"thing": "foo",
"//": "you can comment json",
"// ": "provided that you have no shame",
}
```
Dave Winer ☕️
in reply to Oliver Jensen • • •I do it with comment1, comment2, etc
{
"comment1": this is a comment about something that's nearby."
}
Taco Dave
in reply to Dave Winer ☕️ • • •I prefer multiline comments using arrays, and using //topic as a naming scheme:
```json
{
“//dependencies”: [
“Make sure if you update Next.JS here that”,
“you update the script that handles installing it in”,
“Docker because of dependency weirdness.”
],
“dependencies”: {
}
}
```
allo
in reply to Dave Winer ☕️ • • •You need to known which keys you already used for that. Maybe rather use a uuid. 😈
@ojensen @trysdyn