Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Brave Default Setting Improvements #463

Open
Shrinks99 opened this issue Feb 8, 2024 · 1 comment
Open

Brave Default Setting Improvements #463

Shrinks99 opened this issue Feb 8, 2024 · 1 comment
Assignees
@vnznznz
Labels
enhancement New feature or request

Comments

@Shrinks99
Copy link
Member

Shrinks99 commented Feb 8, 2024 •
edited
Loading

Context

Some of Brave's settings aren't good defaults for crawling.

  • Embedded LinkedIn posts are blocked by default to preserve privacy — probably with good intention, but it also means they won't be captured by the crawler!
  • AMP pages are redirected automatically — unsure if this is good or bad, seems like possible added hassle when figuring out scoping?
  • Tracker and ad blocking is set to Standard, unsure what this does
  • Cross site cookies are blocked — likely fine?
  • Widevine is off by default — likely not an issue, crawling DRM content doesn't work.
  • IPFS is set to "Ask" and requires user input, won't work when crawling
  • Brave's analytics are on, would probably be good to turn these off? We're not real users :P
  • Brave's shields (default adblock and tracking protection) are on by default

User Story

As a user, I'd like my crawler's default settings to offer the best chances of success!
@Shrinks99 Shrinks99 added the enhancement New feature or request label Feb 8, 2024
@Shrinks99 Shrinks99 self-assigned this Feb 8, 2024
@Shrinks99 Shrinks99 changed the title Brave Default Settings Brave Default Setting Improvements Feb 8, 2024
@tw4l
Copy link
Member

tw4l commented Feb 9, 2024

Thank you for doing this investigation! I agree that it'd be wise to tweak the default profile to fit user expectations a bit better.

We could also potentially have a selection of "base profiles" that users could extend from or ignore as they wish, e.g.:

  1. All Shields Disabled
  2. Webrecorder default
  3. Aggressive Ad + Cookie Blocking

@Shrinks99 Shrinks99 removed their assignment Mar 27, 2024
@vnznznz vnznznz mentioned this issue May 21, 2024
Merged
ikreymer pushed a commit that referenced this issue Jun 5, 2024
@vnznznz
Add group policies, limit browser access to container filesystem (#579)
068ee79 
Add some default policy settings to disable unneeded Brave features.
Helps a bit with #463, but Brave unfortunately doesn't provide all
mentioned settings as policy options.

Most important changes are in
`config/policies/lockdown-profilebrowser.json` it limits access to the
container filesystem especially during interactive profile browser
creation.
@ikreymer ikreymer mentioned this issue Jun 15, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vnznznz vnznznz

Labels
enhancement New feature or request
Projects
Webrecorder Projects
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vnznznz @Shrinks99 @tw4l